| … | |
… | |
| 483 | Like C<ev_default_destroy>, but destroys an event loop created by an |
483 | Like C<ev_default_destroy>, but destroys an event loop created by an |
| 484 | earlier call to C<ev_loop_new>. |
484 | earlier call to C<ev_loop_new>. |
| 485 | |
485 | |
| 486 | =item ev_default_fork () |
486 | =item ev_default_fork () |
| 487 | |
487 | |
|
|
488 | This function sets a flag that causes subsequent C<ev_loop> iterations |
| 488 | This function reinitialises the kernel state for backends that have |
489 | to reinitialise the kernel state for backends that have one. Despite the |
| 489 | one. Despite the name, you can call it anytime, but it makes most sense |
490 | name, you can call it anytime, but it makes most sense after forking, in |
| 490 | after forking, in either the parent or child process (or both, but that |
491 | the child process (or both child and parent, but that again makes little |
| 491 | again makes little sense). |
492 | sense). You I<must> call it in the child before using any of the libev |
|
|
493 | functions, and it will only take effect at the next C<ev_loop> iteration. |
| 492 | |
494 | |
| 493 | You I<must> call this function in the child process after forking if and |
495 | On the other hand, you only need to call this function in the child |
| 494 | only if you want to use the event library in both processes. If you just |
496 | process if and only if you want to use the event library in the child. If |
| 495 | fork+exec, you don't have to call it. |
497 | you just fork+exec, you don't have to call it at all. |
| 496 | |
498 | |
| 497 | The function itself is quite fast and it's usually not a problem to call |
499 | The function itself is quite fast and it's usually not a problem to call |
| 498 | it just in case after a fork. To make this easy, the function will fit in |
500 | it just in case after a fork. To make this easy, the function will fit in |
| 499 | quite nicely into a call to C<pthread_atfork>: |
501 | quite nicely into a call to C<pthread_atfork>: |
| 500 | |
502 | |
| 501 | pthread_atfork (0, 0, ev_default_fork); |
503 | pthread_atfork (0, 0, ev_default_fork); |
| 502 | |
|
|
| 503 | At the moment, C<EVBACKEND_SELECT> and C<EVBACKEND_POLL> are safe to use |
|
|
| 504 | without calling this function, so if you force one of those backends you |
|
|
| 505 | do not need to care. |
|
|
| 506 | |
504 | |
| 507 | =item ev_loop_fork (loop) |
505 | =item ev_loop_fork (loop) |
| 508 | |
506 | |
| 509 | Like C<ev_default_fork>, but acts on an event loop created by |
507 | Like C<ev_default_fork>, but acts on an event loop created by |
| 510 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
508 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
