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
..
2012-10-18 18:12:14 +02:00
2012-10-18 17:58:28 +02:00
2012-10-18 17:58:28 +02:00
2012-12-25 07:00:46 +01:00
2013-08-28 00:40:48 +02:00
2013-12-26 13:42:17 +01:00
2014-02-21 17:14:31 +03:00
2013-12-26 13:42:17 +01:00
2013-12-26 13:42:17 +01:00
2013-08-19 10:38:10 +02:00
2014-02-13 12:40:41 -08:00
2014-03-08 17:14:06 -08:00