summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2009-06-29 04:41:34 +0000
committerroot <root>2009-06-29 04:41:34 +0000
commit68aeda203bfd3a3e4a5577dc0ada8155a7a12223 (patch)
tree0b5d613504fc8db75dfedcd922d1a7b8435853e6 /ev.pod
parent6a30e750dc5b7dd735094e3ddbf06efa5cdc930b (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/ev.pod b/ev.pod
index 26be56c..d2de446 100644
--- a/ev.pod
+++ b/ev.pod
@@ -2004,8 +2004,8 @@ exits). It is permissible to install a child watcher I<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 is
-not.
+but forking and registering a watcher a few event loop iterations later or
+in the next callback invocation is not.
Only the default event loop is capable of handling signals, and therefore
you can only register child watchers in the default event loop.