[Pkg-mailman-hackers] Bug#881329: systemd service
Stefan Bühler
stbuehler at lighttpd.net
Fri Nov 10 12:22:39 UTC 2017
Hi again,
I had to add
RestartPreventExitStatus=1
in [Service], because on certain failures (e.g. broken permissions in
the lock directory) mailmanctl forks and exits (which systemd considers
a successful start), and then the fork exits with status code 1.
Because it was started "successfully", systemd will trigger a restart
without limit...
It would be better if mailmanctl supported a flag to not fork mailmanctl
itself, but just run in the foreground (no need to close std{in,out,err}
either). systemd (and other supervising init systems) can handle that
way better.
cheers,
Stefan
More information about the Pkg-mailman-hackers
mailing list