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

Comparing libev/ev.pod (file contents):
Revision 1.137 by root, Sun Mar 16 16:42:56 2008 UTC vs.
Revision 1.138 by root, Mon Mar 31 01:14:12 2008 UTC

… …
1085To support fork in your programs, you either have to call 1085To support fork in your programs, you either have to call
1086C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child, 1086C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,
1087enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or 1087enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or
1088C<EVBACKEND_POLL>. 1088C<EVBACKEND_POLL>.
1089 1089
1090=head3 The special problem of SIGPIPE
1091
1092While not really specific to libev, it is easy to forget about SIGPIPE:
1093when reading from a pipe whose other end has been closed, your program
1094gets send a SIGPIPE, which, by default, aborts your program. For most
1095programs this is sensible behaviour, for daemons, this is usually
1096undesirable.
1097
1098So when you encounter spurious, unexplained daemon exits, make sure you
1099ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
1100somewhere, as that would have given you a big clue).
1101
1090 1102
1091=head3 Watcher-Specific Functions 1103=head3 Watcher-Specific Functions
1092 1104
1093=over 4 1105=over 4
1094 1106

Diff Legend

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