… | |
… | |
402 | environment variable. |
402 | environment variable. |
403 | |
403 | |
404 | =item C<EVFLAG_NOINOTIFY> |
404 | =item C<EVFLAG_NOINOTIFY> |
405 | |
405 | |
406 | When this flag is specified, then libev will not attempt to use the |
406 | When this flag is specified, then libev will not attempt to use the |
407 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
407 | I<inotify> API for its C<ev_stat> watchers. Apart from debugging and |
408 | testing, this flag can be useful to conserve inotify file descriptors, as |
408 | testing, this flag can be useful to conserve inotify file descriptors, as |
409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
410 | |
410 | |
411 | =item C<EVFLAG_SIGNALFD> |
411 | =item C<EVFLAG_SIGNALFD> |
412 | |
412 | |
413 | When this flag is specified, then libev will attempt to use the |
413 | When this flag is specified, then libev will attempt to use the |
414 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
414 | I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API |
415 | delivers signals synchronously, which makes it both faster and might make |
415 | delivers signals synchronously, which makes it both faster and might make |
416 | it possible to get the queued signal data. It can also simplify signal |
416 | it possible to get the queued signal data. It can also simplify signal |
417 | handling with threads, as long as you properly block signals in your |
417 | handling with threads, as long as you properly block signals in your |
418 | threads that are not interested in handling them. |
418 | threads that are not interested in handling them. |
419 | |
419 | |
… | |
… | |
619 | This function is normally used on loop objects allocated by |
619 | This function is normally used on loop objects allocated by |
620 | C<ev_loop_new>, but it can also be used on the default loop returned by |
620 | C<ev_loop_new>, but it can also be used on the default loop returned by |
621 | C<ev_default_loop>, in which case it is not thread-safe. |
621 | C<ev_default_loop>, in which case it is not thread-safe. |
622 | |
622 | |
623 | Note that it is not advisable to call this function on the default loop |
623 | Note that it is not advisable to call this function on the default loop |
624 | except in the rare occasion where you really need to free it's resources. |
624 | except in the rare occasion where you really need to free its resources. |
625 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
625 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
626 | and C<ev_loop_destroy>. |
626 | and C<ev_loop_destroy>. |
627 | |
627 | |
628 | =item ev_loop_fork (loop) |
628 | =item ev_loop_fork (loop) |
629 | |
629 | |
… | |
… | |
2260 | |
2260 | |
2261 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2261 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2262 | |
2262 | |
2263 | Signal watchers will trigger an event when the process receives a specific |
2263 | Signal watchers will trigger an event when the process receives a specific |
2264 | signal one or more times. Even though signals are very asynchronous, libev |
2264 | signal one or more times. Even though signals are very asynchronous, libev |
2265 | will try it's best to deliver signals synchronously, i.e. as part of the |
2265 | will try its best to deliver signals synchronously, i.e. as part of the |
2266 | normal event processing, like any other event. |
2266 | normal event processing, like any other event. |
2267 | |
2267 | |
2268 | If you want signals to be delivered truly asynchronously, just use |
2268 | If you want signals to be delivered truly asynchronously, just use |
2269 | C<sigaction> as you would do without libev and forget about sharing |
2269 | C<sigaction> as you would do without libev and forget about sharing |
2270 | the signal. You can even use C<ev_async> from a signal handler to |
2270 | the signal. You can even use C<ev_async> from a signal handler to |