rpms
/
uwsgi
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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)
This commit is contained in:
Jorge Gallegos 2013-10-05 12:18:13 -07:00
parent 11e3d17854
commit c04fd62ef2
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
uwsgi.service
View File

@ -6,6 +6,8 @@ After=syslog.target
ExecStartPre=/bin/mkdir -p /run/uwsgi
ExecStartPre=/bin/chown uwsgi:uwsgi /run/uwsgi
ExecStart=/usr/sbin/uwsgi --ini /etc/uwsgi.ini
ExecReload=/bin/kill -HUP $MAINPID
KillSignal=SIGINT
Restart=always
Type=notify
StandardError=syslog