Quoting Sergei Golovan <sgolo...@gmail.com>:
So I'd suggest to break the current setup little bit by replacing
daemonize = true
by daemonize = false and using --background and --make-pidfile (and
possibly --remove-pidfile)
facilities of start-stop-daemon. I haven't tested these options yet
though. If they work
well, then we can include both ways of starting prosody for buster,
and probably
remove the init.d script for bullseye.
Any thoughts?
I suggest to change all our defaults to use systemd (because it is the
default init system of Debian) and move the sys-v-init script to the
examples. Maybe add a README with hints, what admins need to change
to run prosody with sysvinit. Or helpful comments in the default
config. I don't think that the default setup needs to be sysvinit
compatible out of the box for buster, as long as admins can change
this easily.
Btw. Many thanks for your work on prosody bug sanitizing!
Very much appreciated!
