diff options
author | root <root> | 2009-08-26 17:11:42 +0000 |
---|---|---|
committer | root <root> | 2009-08-26 17:11:42 +0000 |
commit | 6d5a10c62f464381912287368c2b93f4014245f2 (patch) | |
tree | 90da0eef64a425be86df7f54f040614c1245c720 /ev.pod | |
parent | c1ef87aee531fa008156ecec2dc1fc76f16c2c16 (diff) |
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r-- | ev.pod | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -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 |