ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.pod
(Generate patch)

Comparing libev/ev.pod (file contents):
Revision 1.266 by root, Wed Aug 26 17:15:05 2009 UTC vs.
Revision 1.271 by root, Fri Sep 18 21:16:10 2009 UTC

… …
370When this flag is specified, then libev will not attempt to use the 370When this flag is specified, then libev will not attempt to use the
371I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and 371I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and
372testing, this flag can be useful to conserve inotify file descriptors, as 372testing, this flag can be useful to conserve inotify file descriptors, as
373otherwise each loop using C<ev_stat> watchers consumes one inotify handle. 373otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
374 374
375=item C<EVFLAG_NOSIGNALFD> 375=item C<EVFLAG_NOSIGFD>
376 376
377When this flag is specified, then libev will not attempt to use the 377When this flag is specified, then libev will not attempt to use the
378I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This is 378I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This is
379probably only useful to work around any bugs in libev. Consequently, this 379probably only useful to work around any bugs in libev. Consequently, this
380flag might go away once the signalfd functionality is considered stable, 380flag might go away once the signalfd functionality is considered stable,
… …
590as signal and child watchers) would need to be stopped manually. 590as signal and child watchers) would need to be stopped manually.
591 591
592In general it is not advisable to call this function except in the 592In general it is not advisable to call this function except in the
593rare occasion where you really need to free e.g. the signal handling 593rare occasion where you really need to free e.g. the signal handling
594pipe fds. If you need dynamically allocated loops it is better to use 594pipe fds. If you need dynamically allocated loops it is better to use
595C<ev_loop_new> and C<ev_loop_destroy>). 595C<ev_loop_new> and C<ev_loop_destroy>.
596 596
597=item ev_loop_destroy (loop) 597=item ev_loop_destroy (loop)
598 598
599Like C<ev_default_destroy>, but destroys an event loop created by an 599Like C<ev_default_destroy>, but destroys an event loop created by an
600earlier call to C<ev_loop_new>. 600earlier call to C<ev_loop_new>.
… …
704event loop time (see C<ev_now_update>). 704event loop time (see C<ev_now_update>).
705 705
706=item ev_loop (loop, int flags) 706=item ev_loop (loop, int flags)
707 707
708Finally, this is it, the event handler. This function usually is called 708Finally, this is it, the event handler. This function usually is called
709after you initialised all your watchers and you want to start handling 709after you have initialised all your watchers and you want to start
710events. 710handling events.
711 711
712If the flags argument is specified as C<0>, it will not return until 712If the flags argument is specified as C<0>, it will not return until
713either no event watchers are active anymore or C<ev_unloop> was called. 713either no event watchers are active anymore or C<ev_unloop> was called.
714 714
715Please note that an explicit C<ev_unloop> is usually better than 715Please note that an explicit C<ev_unloop> is usually better than
… …
2130 2130
2131This means that before calling C<exec> (from the child) you should reset 2131This means that before calling C<exec> (from the child) you should reset
2132the signal mask to whatever "default" you expect (all clear is a good 2132the signal mask to whatever "default" you expect (all clear is a good
2133choice usually). 2133choice usually).
2134 2134
2135The simplest way to ensure that the signal mask is reset in the child is
2136to install a fork handler with C<pthread_atfork> that resets it. That will
2137catch fork calls done by libraries (such as the libc) as well.
2138
2135In current versions of libev, you can ensure that the signal mask is not 2139In current versions of libev, you can also ensure that the signal mask is
2136blocking any signals (except temporarily, so thread users watch out) by 2140not blocking any signals (except temporarily, so thread users watch out)
2137specifying the C<EVFLAG_NOSIGNALFD> when creating the event loop. This is 2141by specifying the C<EVFLAG_NOSIGFD> when creating the event loop. This
2138not guaranteed for future versions, however. 2142is not guaranteed for future versions, however.
2139 2143
2140=head3 Watcher-Specific Functions and Data Members 2144=head3 Watcher-Specific Functions and Data Members
2141 2145
2142=over 4 2146=over 4
2143 2147

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines