The EvChild class
(PECL ev >= 0.2.0)
Introduction
EvChild
watchers trigger when the process receives a
SIGCHLD
in response to some child status changes (most typically when a child dies
or exits). It is permissible to install an
EvChild
watcher after the child has been forked(which implies it might have
already exited), as long as the event loop isn't entered(or is continued
from a watcher), i.e. forking and then immediately registering a watcher
for the child is fine, but forking and registering a watcher a few event
loop iterations later or in the next callback invocation is not.
It is allowed to register EvChild watchers in the default loop only.
Class synopsis
$pid
,
bool
$trace
,
callable
$callback
[,
mixed
$data
= NULL
[,
int
$priority
= 0
]] )$pid
,
bool
$trace
,
callable
$callback
[,
mixed
$data
[,
int
$priority
]] ) : objectTable of Contents
- EvChild::__construct — Constructs the EvChild watcher object
- EvChild::createStopped — Create instance of a stopped EvCheck watcher
- EvChild::set — Configures the watcher
English translation
You have asked to visit this site in English. For now, only the interface is translated, but not all the content yet.If you want to help me in translations, your contribution is welcome. All you need to do is register on the site, and send me a message asking me to add you to the group of translators, which will give you the opportunity to translate the pages you want. A link at the bottom of each translated page indicates that you are the translator, and has a link to your profile.
Thank you in advance.
Document created the 30/01/2003, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/php-rf-class.evchild.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.