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

Comparing libev/ev.pod (file contents):
Revision 1.269 by root, Mon Aug 31 14:51:48 2009 UTC vs.
Revision 1.270 by root, Fri Sep 18 21:02:12 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,

Diff Legend

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