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

19 lines
398 B
SYSTEMD
Raw Normal View History

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 22:47:35 +00:00
[Unit]
Description=uWSGI Emperor Service
After=syslog.target
[Service]
SystemD service definition sysconfig support Forgot to add this before, and given that uWSGI *does* offer strong support for environment variables, makes sense.
2014-09-16 16:11:15 +00:00
EnvironmentFile=-/etc/sysconfig/uwsgi
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 22:47:35 +00:00
ExecStartPre=/bin/mkdir -p /run/uwsgi
ExecStartPre=/bin/chown uwsgi:uwsgi /run/uwsgi
Fixing 873382
2012-12-27 02:27:53 +00:00
ExecStart=/usr/sbin/uwsgi --ini /etc/uwsgi.ini
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 19:18:13 +00:00
ExecReload=/bin/kill -HUP $MAINPID
KillSignal=SIGINT
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 22:47:35 +00:00
Restart=always
Type=notify
StandardError=syslog
NotifyAccess=all
[Install]
WantedBy=multi-user.target