Lines Matching refs:child

334 supports child process events, and dynamically created event loops which
510 forks then I<both> parent and child process have to recreate the epoll
674 as signal and child watchers) would need to be stopped manually.
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>.
702 On the other hand, you only need to call this function in the child
703 process if and only if you want to use the event loop in the child. If
704 you just fork+exec or create a new loop in the child, you don't have to
880      Signals and child watchers are implemented as I/O watchers, and will
1206 The event loop has been resumed in the child process after fork (see
1681 it in the child if you want to continue to use it in the child.
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
2447 This means that before calling C<exec> (from the child) you should reset
2451 The simplest way to ensure that the signal mask is reset in the child is
2513 some child status changes (most typically when a child of yours dies or
2514 exits). It is permissible to install a child watcher I<after> the child
2517 forking and then immediately registering a watcher for the child is fine,
2522 you can only register child watchers in the default event loop.
2524 Due to some design glitches inside libev, child watchers will always be
2532 first child watcher is started after the child exits. The occurrence
2533 of C<SIGCHLD> is recorded asynchronously, but child reaping is done
2539 Libev offers no special support for overriding the built-in child
2540 processing, but if your application collides with libev's default child
2544 event-based approach to child reaping and thus use libev's support for
2549 Currently, the child watcher never gets stopped, even when the
2550 child terminates, so normally one needs to stop the watcher in the
2552 when a child exit is detected (calling C<ev_child_stop> twice is not a
2589 Example: C<fork()> a new process and install a child handler to wait for
2607        // the forked child executes here
3267 and before C<ev_check> watchers are being called, and only in the child
3279 in the child, or both parent in child, in effect "continuing" after the
3283 forks) is to duplicate all the state in the child, as would be expected
3284 when I<either> the parent I<or> the child process continues.
4721 but multiple event loop support, async and child watchers and the poll
4774 embed, async, child...) you can enable them manually by defining
5381 =item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)
5387 =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HA…