Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update signals.rst #1297

Merged
merged 1 commit into from
Jun 26, 2016
Merged

Update signals.rst #1297

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions docs/source/signals.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,8 +69,8 @@ do it without any service downtime - no incoming requests will be
lost. Preloaded applications will also be reloaded.

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.
/var/run/gunicorn.pid.oldbin), then executes a new binary,
master process. It executes a new binary whose .pid file is
postfixed with .2 (e.g. /var/run/gunicorn.pid.2),
which in turn starts a new master process and the new worker processes::


Expand All @@ -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

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
.oldbin suffix from its .pid file, and everything is exactly as before
them after the new master process quits, and everything is exactly as before
the upgrade attempt.

If an update is successful and you want to keep the new server, send
Expand Down