diff options
author | Eric Wong <normalperson@yhbt.net> | 2013-11-26 18:58:03 +0000 |
---|---|---|
committer | Eric Wong <normalperson@yhbt.net> | 2013-11-26 19:04:53 +0000 |
commit | fa17da92aa4e76d5fd63cb9b74d6884d611ec899 (patch) | |
tree | d8e564e336cb692ff76e3fd6a0af5f5305f224e7 | |
parent | 795c3527337ff4f03ae6db08c5df01141565ed96 (diff) | |
download | unicorn-fa17da92aa4e76d5fd63cb9b74d6884d611ec899.tar.gz |
"interactive terminal" needed clarification. While we're at it, link to the init.sh example since it may be shared with nginx. Reported-by: Rodrigo Rosenfeld Rosas ref: <5294E9D4.5030608@gmail.com>
-rw-r--r-- | SIGNALS | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -7,6 +7,9 @@ signal handling matches the behavior of {nginx}[http://nginx.net/] so it should be possible to easily share process management scripts between Unicorn and nginx. +One example init script is distributed with unicorn: +http://unicorn.bogomips.org/examples/init.sh + === Master Process * HUP - reloads config file and gracefully restart all workers. @@ -101,8 +104,8 @@ The procedure is exactly like that of nginx: 3. You can now send WINCH to the old master process so only the new workers serve requests. If your unicorn process is bound to an interactive - terminal, you can skip this step. Step 5 will be more difficult but - you can also skip it if your process is not daemonized. + terminal (not daemonized), you can skip this step. Step 5 will be more + difficult but you can also skip it if your process is not daemonized. 4. You should now ensure that everything is running correctly with the new workers as the old workers die off. |