[pkg-uWSGI-devel] Bug#833067: Bug#833067: uwsgi: does not use systemd for services

[Chris Warrick]

On 31 July 2016 at 15:57, Jonas Smedegaard <dr at jones.dk> wrote:
> Hi Chris,
>
> Quoting Chris Warrick (2016-07-31 14:34:04)
>> the uwsgi (and uwsgi-emperor) packages do not contain systemd service
>> files, instead opting for old LSB service files. Other distros
>> (Fedora, CentOS with EPEL, Arch Linux) already use systemd units. The
>> uwsgi developers provide a systemd service file in the documentation
>> [0].  Is it possible to update the Debian packages to ship those files
>> instead of /etc/init.d/uwsgi* as well?
>
> I am not comfortable writing/patching/debugging systemd files yet
> myself.
>
> I would very much welcome someone joining the team who would take the
> responsibility of caring for those files, ensuring that the behaviour
> across init systems is consistent (e.g. write Debian-specific systemd
> files behaving same as the Debian-specific sysV files, or help adapt the
> sysV files to match whatever possibly more sensible behaviour of
> upstream shipped systemd files).
>
> Would you perhaps be interested in joining our team to care for that?

Sorry, but I don’t have time to do OS development, I despise SysV init
and I don’t use Debian often anyways. I’m afraid you will have to find
someone else, or accept the fact that there might be some minor
incompatibilities. That said, looking at /etc/init.d/uwsgi-emperor, it
could be replaced by uwsgi’s proposed systemd service file pretty
easily. (I have no idea about /etc/init.d/uwsgi)

-- 
Chris Warrick <https://chriswarrick.com/>
PGP: 5EAAEA16