[pkg-uWSGI-devel] Bug#969372: Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Jonas Smedegaard]

Quoting Rens Houben (2020-12-22 18:35:52)
> Okay, this is quick-and-dirty because I didn't have a great deal of time and I'm not /that/ great with systemd service files to begin with.
> 
> -------
> [Unit]
> Description=uWSGI Emperor
> After=syslog.target
> 
> [Service]
> ExecStart=/usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini
> RuntimeDirectory=uwsgi
> Restart=always
> KillSignal=SIGQUIT
> Type=notify
> StandardError=syslog
> NotifyAccess=all
> 
> [Install]
> WantedBy=multi-user.target
> --------
> There's serious room for improvement there -- the usual way for 
> running the Emperor is in Tyrant mode and setting it to retain 
> setuid/setguid capabilities before switching down to a 
> non-privileged user; I think it would be possible to assign 
> it those capabilities in the service file and start it unprivileged 
> otherwise, but I'm not good enough to bash that out safely.
> 
> Hope this helps, and thanks for the excellent job you guys do,


Thanks!

What I still don't understand is why, when systemd file is missing, it 
does not automatically fallback to use sysv - I thought that would 
happen generally in Debian (and that adding systemd file therefore 
should be only an improvement, not crucial).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-uwsgi-devel/attachments/20201223/d57d3615/attachment.sig>