Commit Graph

4 Commits

Author SHA1 Message Date
Jorge Gallegos
c04fd62ef2 This was actually right. From the documentation
> By default sending the SIGTERM signal to uWSGI means "brutally
> reload the stack" while the convention is to shut an application
> down on SIGTERM. To shutdown uWSGI use SIGINT or SIGQUIT instead.
> If you absolutely can not live with uWSGI being so disrespectful
> towards SIGTERM, by all means enable the die-on-term option.

(https://uwsgi-docs.readthedocs.org/en/latest/ThingsToKnow.html)

And:

> Sending SIGHUP to the Emperor will reload all vassals.

(https://uwsgi-docs.readthedocs.org/en/latest/Emperor.html)
2013-10-05 12:18:13 -07:00
Jorge Gallegos
6e9a7acef1 This got fixed a while ago, don't need it
This completes fix for BZ 912317
2013-10-04 08:59:59 -07:00
Jorge A Gallegos
7e7c7f9a23 Fixing 873382 2012-12-26 18:27:53 -08:00
Jorge A Gallegos
1b255a44e5 Adding systemd files and changes
Still not entirely working as I want it to, need to figure out why uwsgi
returns 30 and how to make systemd understand that is fine
2012-07-29 15:47:35 -07:00