From c04fd62ef2ccf45c38a0fed5a36683f1df6ea22c Mon Sep 17 00:00:00 2001 From: Jorge Gallegos Date: Sat, 5 Oct 2013 12:18:13 -0700 Subject: [PATCH] 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) --- uwsgi.service | 2 ++ 1 file changed, 2 insertions(+) diff --git a/uwsgi.service b/uwsgi.service index f9961d2..e2f2446 100644 --- a/uwsgi.service +++ b/uwsgi.service @@ -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