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 |
|