Eric Chapweske e...@zendesk.com wrote:
We ran into the same issue. For us, it was because we were executing the
process using bundle exec. Bundler doesn't preserve the 1.9 behavior around
FD inheritance. https://github.com/bundler/bundler/issues/2628
Thanks Eric! I just pushed out the following and updated the website.
Subject: [PATCH] Sandbox: document SIGUSR2 + bundler issue with 2.0.0
Thanks to Eric Chapweske for the heads up.
ref: http://mid.gmane.org/loom.20130904t205308-...@post.gmane.org
---
Sandbox | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Sandbox b/Sandbox
index 1df149b..3c7f226 100644
--- a/Sandbox
+++ b/Sandbox
@@ -60,6 +60,13 @@ If you're using an older Bundler version (0.9.x), you may
need to set or
reset GEM_HOME, GEM_PATH and PATH environment variables in the
before_exec hook as illustrated by http://gist.github.com/534668
+=== Ruby 2.0.0 close-on-exec and SIGUSR2 incompatibility
+
+Ruby 2.0.0 enforces FD_CLOEXEC on file descriptors by default. unicorn
+has been prepared for this behavior since unicorn 4.1.0, but we forgot
+to remind the Bundler developers. This issue is being tracked here:
+https://github.com/bundler/bundler/issues/2628
+
== Isolate
=== Running
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying