jingrow/gunicorn
1
0
Fork 0
mirror of https://github.com/frappe/gunicorn.git synced 2026-01-14 11:09:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1297 from gfreezy/patch-1

Browse Source 
Update signals.rst
This commit is contained in:
Randall Leeds 2016-06-26 17:46:26 -04:00 committed by GitHub
commit 28c12b2668
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/source/signals.rst
View File

@ -69,8 +69,8 @@ do it without any service downtime - no incoming requests will be
lost. Preloaded applications will also be reloaded. lost. Preloaded applications will also be reloaded.
First, replace the old binary with a new one, then send the **USR2** signal to the First, replace the old binary with a new one, then send the **USR2** signal to the
master process. It renames its .pid file to .oldbin (e.g. master process. It executes a new binary whose .pid file is
/var/run/gunicorn.pid.oldbin), then executes a new binary, postfixed with .2 (e.g. /var/run/gunicorn.pid.2),
which in turn starts a new master process and the new worker processes:: which in turn starts a new master process and the new worker processes::
@ -96,8 +96,7 @@ At this point you can still revert to the old server because it hasn't closed it
- Send the QUIT signal to the new master process to force it quit - Send the QUIT signal to the new master process to force it quit
If for some reason the new worker processes do not quit, send the KILL signal to If for some reason the new worker processes do not quit, send the KILL signal to
them after the new master process quits, the old master process removes them after the new master process quits, and everything is exactly as before
.oldbin suffix from its .pid file, and everything is exactly as before
the upgrade attempt. the upgrade attempt.
If an update is successful and you want to keep the new server, send If an update is successful and you want to keep the new server, send