| … | |
… | |
| 689 | the name, you can call it anytime you are allowed to start or stop |
689 | the name, you can call it anytime you are allowed to start or stop |
| 690 | watchers (except inside an C<ev_prepare> callback), but it makes most |
690 | watchers (except inside an C<ev_prepare> callback), but it makes most |
| 691 | sense after forking, in the child process. You I<must> call it (or use |
691 | sense after forking, in the child process. You I<must> call it (or use |
| 692 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
692 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
| 693 | |
693 | |
| 694 | In addition, if you want to reuse a loop (via this function of |
694 | In addition, if you want to reuse a loop (via this function or |
| 695 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
695 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
| 696 | |
696 | |
| 697 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
697 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
| 698 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
698 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
| 699 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
699 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
