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

Comparing libev/ev.pod (file contents):
Revision 1.430 by root, Tue Oct 29 12:13:37 2013 UTC vs.
Revision 1.431 by root, Fri Nov 22 16:42:10 2013 UTC

2413only within the same loop, i.e. you can watch for C<SIGINT> in your 2413only within the same loop, i.e. you can watch for C<SIGINT> in your
2414default loop and for C<SIGIO> in another loop, but you cannot watch for 2414default loop and for C<SIGIO> in another loop, but you cannot watch for
2415C<SIGINT> in both the default loop and another loop at the same time. At 2415C<SIGINT> in both the default loop and another loop at the same time. At
2416the moment, C<SIGCHLD> is permanently tied to the default loop. 2416the moment, C<SIGCHLD> is permanently tied to the default loop.
2417 2417
2418When the first watcher gets started will libev actually register something 2418Only after the first watcher for a signal is started will libev actually
2419with the kernel (thus it coexists with your own signal handlers as long as 2419register something with the kernel. It thus coexists with your own signal
2420you don't register any with libev for the same signal). 2420handlers as long as you don't register any with libev for the same signal.
2421 2421
2422If possible and supported, libev will install its handlers with 2422If possible and supported, libev will install its handlers with
2423C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should 2423C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should
2424not be unduly interrupted. If you have a problem with system calls getting 2424not be unduly interrupted. If you have a problem with system calls getting
2425interrupted by signals you can block all signals in an C<ev_check> watcher 2425interrupted by signals you can block all signals in an C<ev_check> watcher

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines