|
|
1 | =encoding utf-8 |
|
|
2 | |
1 | =head1 NAME |
3 | =head1 NAME |
2 | |
4 | |
3 | libev - a high performance full-featured event loop written in C |
5 | libev - a high performance full-featured event loop written in C |
4 | |
6 | |
5 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
… | |
… | |
686 | reinitialise the kernel state for backends that have one. Despite the |
688 | 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 |
689 | 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 |
690 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
689 | child before resuming or calling C<ev_run>. |
691 | child before resuming or calling C<ev_run>. |
690 | |
692 | |
691 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
693 | 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 |
694 | 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 |
695 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
694 | during fork. |
696 | during fork. |
695 | |
697 | |
696 | On the other hand, you only need to call this function in the child |
698 | On the other hand, you only need to call this function in the child |
… | |
… | |
2411 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2413 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2412 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2414 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2413 | C<SIGINT> in both the default loop and another loop at the same time. At |
2415 | C<SIGINT> in both the default loop and another loop at the same time. At |
2414 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2416 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2415 | |
2417 | |
2416 | When the first watcher gets started will libev actually register something |
2418 | Only after the first watcher for a signal is started will libev actually |
2417 | with the kernel (thus it coexists with your own signal handlers as long as |
2419 | register something with the kernel. It thus coexists with your own signal |
2418 | you don't register any with libev for the same signal). |
2420 | handlers as long as you don't register any with libev for the same signal. |
2419 | |
2421 | |
2420 | If possible and supported, libev will install its handlers with |
2422 | If possible and supported, libev will install its handlers with |
2421 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2423 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2422 | not be unduly interrupted. If you have a problem with system calls getting |
2424 | not be unduly interrupted. If you have a problem with system calls getting |
2423 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2425 | interrupted by signals you can block all signals in an C<ev_check> watcher |