diff options
author | root <root> | 2013-10-11 07:50:43 +0000 |
---|---|---|
committer | root <root> | 2013-10-11 07:50:43 +0000 |
commit | a587b0899cfafb04ea726a6e9316777aa7d0ebda (patch) | |
tree | f14f3296ce650940014873806e4ead57e2e030ff | |
parent | 109db4dbb930b320980082c5cfd57dff26a70c0c (diff) |
*** empty log message ***
-rw-r--r-- | ev.pod | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -688,7 +688,7 @@ name, you can call it anytime, but it makes most sense after forking, in the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. -Again, you I<have> to call it on I<any> loop that you want to re-use after +Again, you I<have> to call it on I<any> loop that you want to re-use after a fork, I<even if you do not plan to use the loop in the parent>. This is because some kernel interfaces *cough* I<kqueue> *cough* do funny things during fork. |