about summary refs log tree commit homepage
path: root/SIGNALS
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-11-14 15:53:17 -0800
committerEric Wong <normalperson@yhbt.net>2009-11-14 16:21:33 -0800
commit5663773f053a0cd9764e43b9f34b341f6df5853f (patch)
tree9e25aa4a06e8330fc2494d14c41eea794e93c7a0 /SIGNALS
parent07767ea2733ed5276ec638fa50102dccb0b2991e (diff)
downloadunicorn-5663773f053a0cd9764e43b9f34b341f6df5853f.tar.gz
This is only supported when SIGUSR1 is sent only to the master
process (which then resends SIGUSR1 to the workers).

Since we only added support for user/group switching in the
workers, we now chown any log files upon switching users so the
master can pick up and chown the log files later on.  Thus
we can avoid having to restart workers because they fail to
rotate log files on their own.
Diffstat (limited to 'SIGNALS')
-rw-r--r--SIGNALS7
1 files changed, 7 insertions, 0 deletions
diff --git a/SIGNALS b/SIGNALS
index 30a0ab0..5c7295e 100644
--- a/SIGNALS
+++ b/SIGNALS
@@ -50,6 +50,13 @@ automatically respawned.
   the current request, so multiple log lines for one request
   (as done by Rails) will not be split across multiple logs.
 
+  It is NOT recommended to send the USR1 signal directly to workers via
+  "killall -USR1 unicorn" if you are using user/group-switching support
+  in your workers.  You will encounter incorrect file permissions and
+  workers will need to be respawned.  Sending USR1 to the master process
+  first will ensure logs have the correct permissions before the master
+  forwards the USR1 signal to workers.
+
 === Procedure to replace a running unicorn executable
 
 You may replace a running instance of unicorn with a new one without