Re: Issue when sending USR2 too soon

2010-01-18 Thread Eric Wong
Iñaki Baz Castillo i...@aliax.net wrote: El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió: What about if Unicorn very quicky prepares the trap for USR2 so in case it receives it soon when starting it ignores it (and logs some warning)? Does it make sense? Adding the

Re: Issue when sending USR2 too soon

2010-01-18 Thread Iñaki Baz Castillo
El Lunes, 18 de Enero de 2010, Eric Wong escribió: Iñaki Baz Castillo i...@aliax.net wrote: El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió: What about if Unicorn very quicky prepares the trap for USR2 so in case it receives it soon when starting it ignores it (and logs some

Re: Issue when sending USR2 too soon

2010-01-18 Thread Iñaki Baz Castillo
El Lunes, 18 de Enero de 2010, Eric Wong escribió: On systems with RubyGems, the executable is always an automatically generated wrapper script that does require 'rubygems' first. True, but I use Ruby 1.9 which doesn't require using rubygems. However it's of course true that the binary does a

Re: Issue when sending USR2 too soon

2010-01-18 Thread Eric Wong
Iñaki Baz Castillo i...@aliax.net wrote: El Lunes, 18 de Enero de 2010, Eric Wong escribió: Iñaki Baz Castillo i...@aliax.net wrote: El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió: What about if Unicorn very quicky prepares the trap for USR2 so in case it receives it

Re: Issue when sending USR2 too soon

2010-01-16 Thread Iñaki Baz Castillo
El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió: What about if Unicorn very quicky prepares the trap for USR2 so in case it receives it soon when starting it ignores it (and logs some warning)? Does it make sense? Adding the following on the top of bin/unicorn solves the problem: