| … | |
… | |
| 2962 | |
2962 | |
| 2963 | Using an C<ev_check> watcher is almost enough: it will be called on the |
2963 | Using an C<ev_check> watcher is almost enough: it will be called on the |
| 2964 | next event loop iteration. However, that isn't as soon as possible - |
2964 | next event loop iteration. However, that isn't as soon as possible - |
| 2965 | without external events, your C<ev_check> watcher will not be invoked. |
2965 | without external events, your C<ev_check> watcher will not be invoked. |
| 2966 | |
2966 | |
| 2967 | |
|
|
| 2968 | This is where C<ev_idle> watchers come in handy - all you need is a |
2967 | This is where C<ev_idle> watchers come in handy - all you need is a |
| 2969 | single global idle watcher that is active as long as you have one active |
2968 | single global idle watcher that is active as long as you have one active |
| 2970 | C<ev_check> watcher. The C<ev_idle> watcher makes sure the event loop |
2969 | C<ev_check> watcher. The C<ev_idle> watcher makes sure the event loop |
| 2971 | will not sleep, and the C<ev_check> watcher makes sure a callback gets |
2970 | will not sleep, and the C<ev_check> watcher makes sure a callback gets |
| 2972 | invoked. Neither watcher alone can do that. |
2971 | invoked. Neither watcher alone can do that. |
| … | |
… | |
| 3251 | |
3250 | |
| 3252 | =head2 C<ev_fork> - the audacity to resume the event loop after a fork |
3251 | =head2 C<ev_fork> - the audacity to resume the event loop after a fork |
| 3253 | |
3252 | |
| 3254 | Fork watchers are called when a C<fork ()> was detected (usually because |
3253 | Fork watchers are called when a C<fork ()> was detected (usually because |
| 3255 | whoever is a good citizen cared to tell libev about it by calling |
3254 | whoever is a good citizen cared to tell libev about it by calling |
| 3256 | C<ev_default_fork> or C<ev_loop_fork>). The invocation is done before the |
3255 | C<ev_loop_fork>). The invocation is done before the event loop blocks next |
| 3257 | event loop blocks next and before C<ev_check> watchers are being called, |
3256 | and before C<ev_check> watchers are being called, and only in the child |
| 3258 | and only in the child after the fork. If whoever good citizen calling |
3257 | after the fork. If whoever good citizen calling C<ev_default_fork> cheats |
| 3259 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
3258 | and calls it in the wrong process, the fork handlers will be invoked, too, |
| 3260 | handlers will be invoked, too, of course. |
3259 | of course. |
| 3261 | |
3260 | |
| 3262 | =head3 The special problem of life after fork - how is it possible? |
3261 | =head3 The special problem of life after fork - how is it possible? |
| 3263 | |
3262 | |
| 3264 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3263 | Most uses of C<fork()> consist of forking, then some simple calls to set |
| 3265 | up/change the process environment, followed by a call to C<exec()>. This |
3264 | up/change the process environment, followed by a call to C<exec()>. This |
| … | |
… | |
| 5311 | thread" or will block signals process-wide, both behaviours would |
5310 | thread" or will block signals process-wide, both behaviours would |
| 5312 | be compatible with libev. Interaction between C<sigprocmask> and |
5311 | be compatible with libev. Interaction between C<sigprocmask> and |
| 5313 | C<pthread_sigmask> could complicate things, however. |
5312 | C<pthread_sigmask> could complicate things, however. |
| 5314 | |
5313 | |
| 5315 | The most portable way to handle signals is to block signals in all threads |
5314 | The most portable way to handle signals is to block signals in all threads |
| 5316 | except the initial one, and run the default loop in the initial thread as |
5315 | except the initial one, and run the signal handling loop in the initial |
| 5317 | well. |
5316 | thread as well. |
| 5318 | |
5317 | |
| 5319 | =item C<long> must be large enough for common memory allocation sizes |
5318 | =item C<long> must be large enough for common memory allocation sizes |
| 5320 | |
5319 | |
| 5321 | To improve portability and simplify its API, libev uses C<long> internally |
5320 | To improve portability and simplify its API, libev uses C<long> internally |
| 5322 | instead of C<size_t> when allocating its data structures. On non-POSIX |
5321 | instead of C<size_t> when allocating its data structures. On non-POSIX |
