summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2008-08-18 23:23:45 +0000
committerroot <root>2008-08-18 23:23:45 +0000
commit604b74e5ce2b43560a130ae0a291cbd1e574770c (patch)
tree6a941face90d4143f4387728a9129870704cfe4d
parent4508469c415bb2f031f1fa9a6bea5bb026593612 (diff)
*** empty log message ***
-rw-r--r--ev.pod7
1 files changed, 3 insertions, 4 deletions
diff --git a/ev.pod b/ev.pod
index bef742d..0044dff 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1136,10 +1136,9 @@ C<EVBACKEND_POLL>.
=head3 The special problem of SIGPIPE
While not really specific to libev, it is easy to forget about SIGPIPE:
-when reading from a pipe whose other end has been closed, your program
-gets send a SIGPIPE, which, by default, aborts your program. For most
-programs this is sensible behaviour, for daemons, this is usually
-undesirable.
+when writing to a pipe whose other end has been closed, your program gets
+send a SIGPIPE, which, by default, aborts your program. For most programs
+this is sensible behaviour, for daemons, this is usually undesirable.
So when you encounter spurious, unexplained daemon exits, make sure you
ignore SIGPIPE (and maybe make sure you log the exit status of your daemon