| … | |
… | |
| 686 | reinitialise the kernel state for backends that have one. Despite the |
686 | reinitialise the kernel state for backends that have one. Despite the |
| 687 | name, you can call it anytime, but it makes most sense after forking, in |
687 | name, you can call it anytime, but it makes most sense after forking, in |
| 688 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
688 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
| 689 | child before resuming or calling C<ev_run>. |
689 | child before resuming or calling C<ev_run>. |
| 690 | |
690 | |
| 691 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
691 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
| 692 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
692 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
| 693 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
693 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
| 694 | during fork. |
694 | during fork. |
| 695 | |
695 | |
| 696 | On the other hand, you only need to call this function in the child |
696 | On the other hand, you only need to call this function in the child |
