Lines Matching refs:fork

120 limited support for fork events (C<ev_fork>).
410 Instead of calling C<ev_loop_fork> manually after a fork, you can also
411 make libev check for a fork in each iteration by enabling this flag.
420 The big advantage of this flag is that you can forget about fork (and
509 0.1ms) and so on. The biggest issue is fork races, however - if a program
542 extra overhead. A fork can both result in spurious notifications as well
576 two event changes per incident. Support for C<fork ()> is very bad (you
577 might have to leak fd's on fork, but it's more sane than epoll) and it
698 a fork, I<even if you do not plan to use the loop in the parent>. This is
700 during fork.
704 you just fork+exec or create a new loop in the child, you don't have to
710 it just in case after a fork.
859    - If EVFLAG_FORKCHECK was used, check for a fork.
860    - If a fork was detected (by any means), queue and call all fork watchers.
1206 The event loop has been resumed in the child process after fork (see
1677 =head3 The special problem of fork
1679 Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit
1680 useless behaviour. Libev fully supports fork, but needs to be told about
1683 To support fork in your child processes, you have to call C<ev_loop_fork
1684 ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to
2434 =head3 The special problem of inheritance over fork/execve/pthread_create
2452 to install a fork handler with C<pthread_atfork> that resets it. That will
2453 catch fork calls done by libraries (such as the libc) as well.
2589 Example: C<fork()> a new process and install a child handler to wait for
2601    pid_t pid = fork ();
3179 =head3 C<ev_embed> and fork
3183 fork handling is required in that case. When the watcher is not running,
3262 =head2 C<ev_fork> - the audacity to resume the event loop after a fork
3264 Fork watchers are called when a C<fork ()> was detected (usually because
3268 after the fork. If whoever good citizen calling C<ev_default_fork> cheats
3269 and calls it in the wrong process, the fork handlers will be invoked, too,
3272 =head3 The special problem of life after fork - how is it possible?  argument
3274 Most uses of C<fork ()> consist of forking, then some simple calls to set
3280 fork.
3312 Initialises and configures the fork watcher - it has no parameters of any
5381 =item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
5385 =item Stopping check/prepare/idle/fork/async watchers: O(1)