17 Commits

Author SHA1 Message Date
Berker Peksag
55a01887a3 Tweak signal handling documentation 2017-02-01 01:03:42 +03:00
Berker Peksag
b712c682f1 Document pidfile naming format change in 19.6.0
Fixes #1382
2017-01-23 07:46:20 +03:00
vishesh92
c54426c1e4 Minor fixes in docs and doc's code style (#1361) 2016-12-28 19:02:32 +03:00
Alex.F
0d5e9bfe5e Update signals.rst 2016-06-23 21:35:04 +08:00
Takuya Noguchi
46b70016d2 Update Debian/Ubuntu installation instructions. 2015-09-09 01:51:22 +09:00
Christopher Troup
73aac61945 Remove no-longer-true statement about matching Nginx signal handling 2014-11-12 15:01:50 -05:00
Collin Anderson
03fbe9429d clean whitespace 2014-09-10 09:52:12 -04:00
Marc Abramowitz
9065bc9bd9 signals.rst: Improve English slightly 2014-08-07 22:39:14 -07:00
Rhys Powell
c8b4f00266 Fixed spelling mistake
fixed spelling in TTOU description
2014-06-16 07:57:07 +01:00
Andrew Burdo
ed2d2a8ab3 Change the rest of QUIT and TERM signals.
This will restore graceful shutdown of workers by master.
Also worker_int callback is moved from handle_exit (INT and TERM before switching) to handle_quit(INT and QUIT).
2014-06-13 14:32:11 +03:00
Randall Leeds
63967597a0 Fix mixed up worker signal handling
Commit 81241907ffcf94517ffa14b8427205906b61b540 changed the signal
handling by switching the roles of `TERM` and `QUIT` for the arbiter
so that `TERM` is graceful and `QUIT` is not.

At the time, workers performed graceful shutdown on `QUIT` and quick
shutdown on `TERM` and `INT`. This behavior was also changed so that
`QUIT` (and `INT`) cause a quick shutdown and `TERM` is graceful.

However, the documentation incorrectly reversed the roles of the worker
signals and the arbiter was not updated to use the correct signals.

This commit fixes the documentation and the arbiter signals.
2014-05-13 11:12:01 -07:00
benoitc
81241907ff switch QUIT and TERM signal
With this change, when gunicorn receives a QUIT all the workers are
killed immediately and exit and TERM is used for the graceful shutdown.

Note: the old behaviour was based on the NGINX but the new one is more
correct according the following doc:

https://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html

also it is complying with the way the signals are sent by heroku:

https://devcenter.heroku.com/articles/python-faq#what-constraints-exist-when-developing-applications-on-heroku
2014-03-08 17:14:06 -08:00
Randall Leeds
6ed6b1399e docs typo -- fix #678 2014-01-14 13:53:15 -08:00
benoitc
bb79cdcc36 quick note about preloaded applications 2013-06-29 06:49:32 +02:00
benoitc
d49f9046c5 document a little more the signals handling 2013-06-29 06:39:37 +02:00
benoitc
ba945bd635 fix link syntax 2013-06-29 06:16:17 +02:00
benoitc
a55bfd5b0c fix signals doc file extension 2013-06-29 06:12:34 +02:00