… | |
… | |
2002 | some child status changes (most typically when a child of yours dies or |
2002 | some child status changes (most typically when a child of yours dies or |
2003 | exits). It is permissible to install a child watcher I<after> the child |
2003 | exits). It is permissible to install a child watcher I<after> the child |
2004 | has been forked (which implies it might have already exited), as long |
2004 | has been forked (which implies it might have already exited), as long |
2005 | as the event loop isn't entered (or is continued from a watcher), i.e., |
2005 | as the event loop isn't entered (or is continued from a watcher), i.e., |
2006 | forking and then immediately registering a watcher for the child is fine, |
2006 | forking and then immediately registering a watcher for the child is fine, |
2007 | but forking and registering a watcher a few event loop iterations later is |
2007 | but forking and registering a watcher a few event loop iterations later or |
2008 | not. |
2008 | in the next callback invocation is not. |
2009 | |
2009 | |
2010 | Only the default event loop is capable of handling signals, and therefore |
2010 | Only the default event loop is capable of handling signals, and therefore |
2011 | you can only register child watchers in the default event loop. |
2011 | you can only register child watchers in the default event loop. |
2012 | |
2012 | |
2013 | =head3 Process Interaction |
2013 | =head3 Process Interaction |