|author||Eric Wong <firstname.lastname@example.org>||2014-01-29 08:43:22 +0000|
|committer||Eric Wong <email@example.com>||2014-01-29 08:43:41 +0000|
fix races/error handling in worker SIGQUIT handler This protects us from two problems: 1) we (or our app) somehow called IO#close on one of the sockets we listen on without removing it from the readers array. We'll ignore IOErrors from IO#close and assume we wanted to close it. 2) our SIGQUIT handler is interrupted by itself. This can happen as a fake signal from the master could be handled and a real signal from an outside user is sent to us (e.g. from unicorn-worker-killer) or if a user uses the killall(1) command.
1 files changed, 1 insertions, 1 deletions
diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
index 85be5c9..ad3a12b 100755
@@ -1,5 +1,5 @@
-DEF_VER = "v4.8.0"
+DEF_VER = "v4.8.1"
CONSTANT = "Unicorn::Const::UNICORN_VERSION"
RVF = "lib/unicorn/version.rb"
GVF = "GIT-VERSION-FILE"