From 6d5a10c62f464381912287368c2b93f4014245f2 Mon Sep 17 00:00:00 2001
From: root <root>
Date: Wed, 26 Aug 2009 17:11:42 +0000
Subject: *** empty log message ***

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

diff --git a/Changes b/Changes
index d272af3..96dce7b 100644
--- a/Changes
+++ b/Changes
@@ -2,9 +2,10 @@ Revision history for libev, a high-performance and full-featured event loop.
 
 	- backport inotify code to C89.
         - implement EV_WIN32_HANDLE_TO_FD and EV_WIN32_CLOSE_FD configuration
-          symbols to make ti easier for apps to do their own fd management.
+          symbols to make it easier for apps to do their own fd management.
         - support EV_IDLE_ENABLE being disabled in ev++.h
           (patch by Didier Spezia).
+        - point out the unspecified signal mask in the documentation.
 
 3.8  Sun Aug  9 14:30:45 CEST 2009
 	- incompatible change: do not necessarily reset signal handler
diff --git a/ev.pod b/ev.pod
index 6e07a7e..79fc81c 100644
--- a/ev.pod
+++ b/ev.pod
@@ -2126,12 +2126,17 @@ and might or might not set or restore the installed signal handler.
 While this does not matter for the signal disposition (libev never
 sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on
 C<execve>), this matters for the signal mask: many programs do not expect
-many signals to be blocked.
+certain signals to be blocked.
 
 This means that before calling C<exec> (from the child) you should reset
 the signal mask to whatever "default" you expect (all clear is a good
 choice usually).
 
+In current versions of libev, you can ensure that the signal mask is not
+blocking any signals (except temporarily, so thread users watch out) by
+specifying the C<EVFLAG_NOSIGNALFD> when creating the event loop. This is
+not guaranteed for future versions, however.
+
 =head3 Watcher-Specific Functions and Data Members
 
 =over 4
-- 
cgit v1.2.3