--- AnyEvent/README	2008/10/02 06:42:39	1.31
+++ AnyEvent/README	2008/10/03 07:19:23	1.32
@@ -1333,6 +1333,30 @@
     *   C-based event loops perform very well with small number of watchers,
         as the management overhead dominates.
 
+SIGNALS
+    AnyEvent currently installs handlers for these signals:
+
+    SIGCHLD
+        A handler for "SIGCHLD" is installed by AnyEvent's child watcher
+        emulation for event loops that do not support them natively. Also,
+        some event loops install a similar handler.
+
+    SIGPIPE
+        A no-op handler is installed for "SIGPIPE" when $SIG{PIPE} is
+        "undef" when AnyEvent gets loaded.
+
+        The rationale for this is that AnyEvent users usually do not really
+        depend on SIGPIPE delivery (which is purely an optimisation for
+        shell use, or badly-written programs), but "SIGPIPE" can cause
+        spurious and rare program exits as a lot of people do not expect
+        "SIGPIPE" when writing to some random socket.
+
+        The rationale for installing a no-op handler as opposed to ignoring
+        it is that this way, the handler will be restored to defaults on
+        exec.
+
+        Feel free to install your own handler, or reset it to defaults.
+
 FORK
     Most event libraries are not fork-safe. The ones who are usually are
     because they rely on inefficient but fork-safe "select" or "poll" calls.