| … | |
… | |
| 1820 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1820 | C<repeat> value), or reset the running timer to the C<repeat> value. |
| 1821 | |
1821 | |
| 1822 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1822 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
| 1823 | usage example. |
1823 | usage example. |
| 1824 | |
1824 | |
|
|
1825 | =item ev_timer_remaining (loop, ev_timer *) |
|
|
1826 | |
|
|
1827 | Returns the remaining time until a timer fires. If the timer is active, |
|
|
1828 | then this time is relative to the current event loop time, otherwise it's |
|
|
1829 | the timeout value currently configured. |
|
|
1830 | |
|
|
1831 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
|
|
1832 | C<5>. When the timer is started and one second passes, C<ev_timer_remain> |
|
|
1833 | will return C<4>. When the timer expires and is restarted, it will return |
|
|
1834 | roughly C<7> (likely slightly less as callback invocation takes some time, |
|
|
1835 | too), and so on. |
|
|
1836 | |
| 1825 | =item ev_tstamp repeat [read-write] |
1837 | =item ev_tstamp repeat [read-write] |
| 1826 | |
1838 | |
| 1827 | The current C<repeat> value. Will be used each time the watcher times out |
1839 | The current C<repeat> value. Will be used each time the watcher times out |
| 1828 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
1840 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
| 1829 | which is also when any modifications are taken into account. |
1841 | which is also when any modifications are taken into account. |
| … | |
… | |
| 2064 | Signal watchers will trigger an event when the process receives a specific |
2076 | Signal watchers will trigger an event when the process receives a specific |
| 2065 | signal one or more times. Even though signals are very asynchronous, libev |
2077 | signal one or more times. Even though signals are very asynchronous, libev |
| 2066 | will try it's best to deliver signals synchronously, i.e. as part of the |
2078 | will try it's best to deliver signals synchronously, i.e. as part of the |
| 2067 | normal event processing, like any other event. |
2079 | normal event processing, like any other event. |
| 2068 | |
2080 | |
|
|
2081 | Note that only the default loop supports registering signal watchers |
|
|
2082 | currently. |
|
|
2083 | |
| 2069 | If you want signals asynchronously, just use C<sigaction> as you would |
2084 | If you want signals asynchronously, just use C<sigaction> as you would |
| 2070 | do without libev and forget about sharing the signal. You can even use |
2085 | do without libev and forget about sharing the signal. You can even use |
| 2071 | C<ev_async> from a signal handler to synchronously wake up an event loop. |
2086 | C<ev_async> from a signal handler to synchronously wake up an event loop. |
| 2072 | |
2087 | |
| 2073 | You can configure as many watchers as you like per signal. Only when the |
2088 | You can configure as many watchers as you like per signal. Only when the |
| 2074 | first watcher gets started will libev actually register a signal handler |
2089 | first watcher gets started will libev actually register something with |
| 2075 | with the kernel (thus it coexists with your own signal handlers as long as |
2090 | the kernel (thus it coexists with your own signal handlers as long as you |
| 2076 | you don't register any with libev for the same signal). Similarly, when |
2091 | don't register any with libev for the same signal). |
| 2077 | the last signal watcher for a signal is stopped, libev will reset the |
2092 | |
| 2078 | signal handler to SIG_DFL (regardless of what it was set to before). |
2093 | Both the signal mask state (C<sigprocmask>) and the signal handler state |
|
|
2094 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
|
|
2095 | sotpping it again), that is, libev might or might not block the signal, |
|
|
2096 | and might or might not set or restore the installed signal handler. |
| 2079 | |
2097 | |
| 2080 | If possible and supported, libev will install its handlers with |
2098 | If possible and supported, libev will install its handlers with |
| 2081 | C<SA_RESTART> behaviour enabled, so system calls should not be unduly |
2099 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
| 2082 | interrupted. If you have a problem with system calls getting interrupted by |
2100 | not be unduly interrupted. If you have a problem with system calls getting |
| 2083 | signals you can block all signals in an C<ev_check> watcher and unblock |
2101 | interrupted by signals you can block all signals in an C<ev_check> watcher |
| 2084 | them in an C<ev_prepare> watcher. |
2102 | and unblock them in an C<ev_prepare> watcher. |
| 2085 | |
2103 | |
| 2086 | =head3 Watcher-Specific Functions and Data Members |
2104 | =head3 Watcher-Specific Functions and Data Members |
| 2087 | |
2105 | |
| 2088 | =over 4 |
2106 | =over 4 |
| 2089 | |
2107 | |
| … | |
… | |
| 2134 | libev) |
2152 | libev) |
| 2135 | |
2153 | |
| 2136 | =head3 Process Interaction |
2154 | =head3 Process Interaction |
| 2137 | |
2155 | |
| 2138 | Libev grabs C<SIGCHLD> as soon as the default event loop is |
2156 | Libev grabs C<SIGCHLD> as soon as the default event loop is |
| 2139 | initialised. This is necessary to guarantee proper behaviour even if |
2157 | initialised. This is necessary to guarantee proper behaviour even if the |
| 2140 | the first child watcher is started after the child exits. The occurrence |
2158 | first child watcher is started after the child exits. The occurrence |
| 2141 | of C<SIGCHLD> is recorded asynchronously, but child reaping is done |
2159 | of C<SIGCHLD> is recorded asynchronously, but child reaping is done |
| 2142 | synchronously as part of the event loop processing. Libev always reaps all |
2160 | synchronously as part of the event loop processing. Libev always reaps all |
| 2143 | children, even ones not watched. |
2161 | children, even ones not watched. |
| 2144 | |
2162 | |
| 2145 | =head3 Overriding the Built-In Processing |
2163 | =head3 Overriding the Built-In Processing |
| … | |
… | |
| 2155 | =head3 Stopping the Child Watcher |
2173 | =head3 Stopping the Child Watcher |
| 2156 | |
2174 | |
| 2157 | Currently, the child watcher never gets stopped, even when the |
2175 | Currently, the child watcher never gets stopped, even when the |
| 2158 | child terminates, so normally one needs to stop the watcher in the |
2176 | child terminates, so normally one needs to stop the watcher in the |
| 2159 | callback. Future versions of libev might stop the watcher automatically |
2177 | callback. Future versions of libev might stop the watcher automatically |
| 2160 | when a child exit is detected. |
2178 | when a child exit is detected (calling C<ev_child_stop> twice is not a |
|
|
2179 | problem). |
| 2161 | |
2180 | |
| 2162 | =head3 Watcher-Specific Functions and Data Members |
2181 | =head3 Watcher-Specific Functions and Data Members |
| 2163 | |
2182 | |
| 2164 | =over 4 |
2183 | =over 4 |
| 2165 | |
2184 | |
