… | |
… | |
416 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
416 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
417 | without a system call and thus I<very> fast, but my GNU/Linux system also has |
417 | without a system call and thus I<very> fast, but my GNU/Linux system also has |
418 | C<pthread_atfork> which is even faster). |
418 | C<pthread_atfork> which is even faster). |
419 | |
419 | |
420 | The big advantage of this flag is that you can forget about fork (and |
420 | The big advantage of this flag is that you can forget about fork (and |
421 | forget about forgetting to tell libev about forking) when you use this |
421 | forget about forgetting to tell libev about forking, although you still |
422 | flag. |
422 | have to ignore C<SIGPIPE>) when you use this flag. |
423 | |
423 | |
424 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
424 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
425 | environment variable. |
425 | environment variable. |
426 | |
426 | |
427 | =item C<EVFLAG_NOINOTIFY> |
427 | =item C<EVFLAG_NOINOTIFY> |
… | |
… | |
688 | to reinitialise the kernel state for backends that have one. Despite |
688 | to reinitialise the kernel state for backends that have one. Despite |
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 | |
|
|
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>. |
693 | |
696 | |
694 | 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 |
695 | 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 |
696 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
699 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
697 | during fork. |
700 | during fork. |