Hi, I'm thinking in using a worker (i.e: worker.nr == 0) to accomplish a
diferent task than binding in the Unicorn socket.
It would behave as a different process which binds in a different socket as
daemon, so the other workers would notify it after processing data.
Of course I could have a
On Thu, Jan 7, 2010 at 11:31 AM, Iñaki Baz Castillo i...@aliax.net wrote:
El Jueves, 7 de Enero de 2010, Michael Guterl escribió:
Our Rails app has started raising exceptions (caught by hoptoad
thankfully) and I can only imagine they're related to unicorn. I only
think the errors are
On Thu, Jan 7, 2010 at 3:13 PM, Eric Wong normalper...@yhbt.net wrote:
Michael Guterl mgut...@gmail.com wrote:
Our Rails app has started raising exceptions (caught by hoptoad
thankfully) and I can only imagine they're related to unicorn. I only
*think* the errors are occurring on the request
