diff options
| -rw-r--r-- | configure.ac | 2 | ||||
| -rw-r--r-- | ev.h | 2 | ||||
| -rw-r--r-- | ev.pod | 13 |
3 files changed, 9 insertions, 8 deletions
diff --git a/configure.ac b/configure.ac index 061bb39..8bb910d 100644 --- a/configure.ac +++ b/configure.ac @@ -1,7 +1,7 @@ AC_INIT AC_CONFIG_SRCDIR([ev_epoll.c]) -AM_INIT_AUTOMAKE(libev,3.8) dnl also update ev.h! +AM_INIT_AUTOMAKE(libev,3.9) dnl also update ev.h! AC_CONFIG_HEADERS([config.h]) AM_MAINTAINER_MODE @@ -163,7 +163,7 @@ struct ev_loop; #endif #define EV_VERSION_MAJOR 3 -#define EV_VERSION_MINOR 8 +#define EV_VERSION_MINOR 9 #ifndef EV_CB_DECLARE # define EV_CB_DECLARE(type) void (*cb)(EV_P_ struct type *w, int revents); @@ -376,8 +376,10 @@ otherwise each loop using C<ev_stat> watchers consumes one inotify handle. When this flag is specified, then libev will attempt to use the I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API -delivers signals synchronously, which makes is both faster and might make -it possible to get the queued signal data. +delivers signals synchronously, which makes it both faster and might make +it possible to get the queued signal data. It can also simplify signal +handling with threads, as long as you properly block signals in your +threads that are not interested in handling them. Signalfd will not be used by default as this changes your signal mask, and there are a lot of shoddy libraries and programs (glib's threadpool for @@ -2162,10 +2164,9 @@ unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces the window of opportunity for problems, it will not go away, as libev I<has> to modify the signal mask, at least temporarily. -So I can't stress this enough I<if you do not reset your signal mask -when you expect it to be empty, you have a race condition in your -program>. This is not a libev-specific thing, this is true for most event -libraries. +So I can't stress this enough: I<If you do not reset your signal mask when +you expect it to be empty, you have a race condition in your code>. This +is not a libev-specific thing, this is true for most event libraries. =head3 Watcher-Specific Functions and Data Members |