Stone <[email protected]> wrote: > In the deployment I did kill -s USR2 `cat unicorn_pid` to gracefully > restart unicorn. But I noticed that unicorn workers were partially > restarted when using USR2.
You need to send a SIGQUIT to the original master process, otherwise both masters and all workers continue running. This allows you to test the new deploy (combined with SIGWINCH). The last section of http://unicorn.bogomips.org/SIGNALS.html describes this process in detail. > The following is how I did test: > > start unicorn in production environment: > > the action has the following code: Ugh, don't you have something like "ps axf" that shows you a process tree? It's much easier just to *see* the process tree. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
