--- AnyEvent/README	2008/10/02 06:42:39	1.31
+++ AnyEvent/README	2008/11/21 01:36:22	1.34
@@ -1133,16 +1133,16 @@
 
    Results
               name watchers bytes create invoke destroy comment
-             EV/EV   400000   244   0.56   0.46    0.31 EV native interface
-            EV/Any   100000   244   2.50   0.46    0.29 EV + AnyEvent watchers
-        CoroEV/Any   100000   244   2.49   0.44    0.29 coroutines + Coro::Signal
-          Perl/Any   100000   513   4.92   0.87    1.12 pure perl implementation
-       Event/Event    16000   516  31.88  31.30    0.85 Event native interface
-         Event/Any    16000   590  35.75  31.42    1.08 Event + AnyEvent watchers
-          Glib/Any    16000  1357  98.22  12.41   54.00 quadratic behaviour
-            Tk/Any     2000  1860  26.97  67.98   14.00 SEGV with >> 2000 watchers
-         POE/Event     2000  6644 108.64 736.02   14.73 via POE::Loop::Event
-        POE/Select     2000  6343  94.13 809.12  565.96 via POE::Loop::Select
+             EV/EV   400000   224   0.47   0.35    0.27 EV native interface
+            EV/Any   100000   224   2.88   0.34    0.27 EV + AnyEvent watchers
+        CoroEV/Any   100000   224   2.85   0.35    0.28 coroutines + Coro::Signal
+          Perl/Any   100000   452   4.13   0.73    0.95 pure perl implementation
+       Event/Event    16000   517  32.20  31.80    0.81 Event native interface
+         Event/Any    16000   590  35.85  31.55    1.06 Event + AnyEvent watchers
+          Glib/Any    16000  1357 102.33  12.31   51.00 quadratic behaviour
+            Tk/Any     2000  1860  27.20  66.31   14.00 SEGV with >> 2000 watchers
+         POE/Event     2000  6328 109.99 751.67   14.02 via POE::Loop::Event
+        POE/Select     2000  6027  94.54 809.13  579.80 via POE::Loop::Select
 
    Discussion
     The benchmark does *not* measure scalability of the event loop very
@@ -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.