|
|
|
@ -1,4 +1,4 @@ |
|
|
|
|
.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28) |
|
|
|
|
.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.30) |
|
|
|
|
.\" |
|
|
|
|
.\" Standard preamble: |
|
|
|
|
.\" ======================================================================== |
|
|
|
@ -133,7 +133,7 @@ |
|
|
|
|
.\" ======================================================================== |
|
|
|
|
.\" |
|
|
|
|
.IX Title "LIBEV 3" |
|
|
|
|
.TH LIBEV 3 "2015-05-01" "libev-4.19" "libev - high performance full featured event loop" |
|
|
|
|
.TH LIBEV 3 "2015-12-20" "libev-4.20" "libev - high performance full featured event loop" |
|
|
|
|
.\" For nroff, turn off justification. Always turn off hyphenation; it makes |
|
|
|
|
.\" way too many mistakes in technical documents. |
|
|
|
|
.if n .ad l |
|
|
|
@ -543,8 +543,8 @@ without a system call and thus \fIvery\fR fast, but my GNU/Linux system also has |
|
|
|
|
\&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
|
|
|
|
.Sp |
|
|
|
|
The big advantage of this flag is that you can forget about fork (and |
|
|
|
|
forget about forgetting to tell libev about forking) when you use this |
|
|
|
|
flag. |
|
|
|
|
forget about forgetting to tell libev about forking, although you still |
|
|
|
|
have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR) when you use this flag. |
|
|
|
|
.Sp |
|
|
|
|
This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
|
|
|
|
environment variable. |
|
|
|
@ -819,6 +819,9 @@ watchers (except inside an \f(CW\*(C`ev_prepare\*(C'\fR callback), but it makes |
|
|
|
|
sense after forking, in the child process. You \fImust\fR call it (or use |
|
|
|
|
\&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. |
|
|
|
|
.Sp |
|
|
|
|
In addition, if you want to reuse a loop (via this function or |
|
|
|
|
\&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR), you \fIalso\fR have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR. |
|
|
|
|
.Sp |
|
|
|
|
Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after |
|
|
|
|
a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is |
|
|
|
|
because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things |
|
|
|
|