Hi,
The following patch allows dumping of live Ruby backtraces of running workers
by sending a TRAP signal (kill -5) to the worker PID.
The master also automatically generates a backtrace when it kills a worker due
to timeout: this helps identifying what was doing the worker and hopefully give
a hint of what was taking so much time.
Kind regards,
Cedric
PS: not subscribed to the ML, so please CC: me when replying. Thanks!
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
