From 2a7a247b8106b570bd193801b4739d5a755ae1c7 Mon Sep 17 00:00:00 2001
From: root <root>
Date: Thu, 2 Aug 2012 11:55:28 +0000
Subject: *** empty log message ***

---
 Changes |  1 +
 ev.pod  | 15 +++++++--------
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/Changes b/Changes
index 4fcd0c5..54c1640 100644
--- a/Changes
+++ b/Changes
@@ -10,6 +10,7 @@ TODO: ev_feed_child_event
 TODO: document the special problem of signals around fork.
 TODO: store pid for each signal
 TODO: document file descriptor usage per loop
+TODO: store loop pid_t and compare isndie signal handler,store 1 for same, 2 for differign pid, clean up in loop_fork
         - destroying a non-default loop would stop the global waitpid
           watcher (Denis Bilenko).
 	- queueing pending watchers of higher priority from a watcher now invokes
diff --git a/ev.pod b/ev.pod
index 1a63c5d..1e28589 100644
--- a/ev.pod
+++ b/ev.pod
@@ -2964,7 +2964,6 @@ Using an C<ev_check> watcher is almost enough: it will be called on the
 next event loop iteration. However, that isn't as soon as possible -
 without external events, your C<ev_check> watcher will not be invoked.
 
-
 This is where C<ev_idle> watchers come in handy - all you need is a
 single global idle watcher that is active as long as you have one active
 C<ev_check> watcher. The C<ev_idle> watcher makes sure the event loop
@@ -3253,11 +3252,11 @@ C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too).
 
 Fork watchers are called when a C<fork ()> was detected (usually because
 whoever is a good citizen cared to tell libev about it by calling
-C<ev_default_fork> or C<ev_loop_fork>). The invocation is done before the
-event loop blocks next and before C<ev_check> watchers are being called,
-and only in the child after the fork. If whoever good citizen calling
-C<ev_default_fork> cheats and calls it in the wrong process, the fork
-handlers will be invoked, too, of course.
+C<ev_loop_fork>). The invocation is done before the event loop blocks next
+and before C<ev_check> watchers are being called, and only in the child
+after the fork. If whoever good citizen calling C<ev_default_fork> cheats
+and calls it in the wrong process, the fork handlers will be invoked, too,
+of course.
 
 =head3 The special problem of life after fork - how is it possible?
 
@@ -5313,8 +5312,8 @@ be compatible with libev. Interaction between C<sigprocmask> and
 C<pthread_sigmask> could complicate things, however.
 
 The most portable way to handle signals is to block signals in all threads
-except the initial one, and run the default loop in the initial thread as
-well.
+except the initial one, and run the signal handling loop in the initial
+thread as well.
 
 =item C<long> must be large enough for common memory allocation sizes
 
-- 
cgit v1.2.3