Hi, On Mon, Jan 16, 2017 at 12:45 AM, W. Martin Borgert <deba...@debian.org> wrote: > > There is a systemd unit file by upstream: > > https://hg.prosody.im/prosody-modules/file/tip/misc/systemd/prosody.service > (change https://hg.prosody.im/prosody-modules/rev/f8ecb4b248b0) > > I'm using it on Jessie. I had to remove the Umask line and to change > the daemonize mode of prosody. So far, it seems to work.
This might cause a problem, at least while we ship both a /etc/init.d script and a systemd service file. They would require different configs, which in case of prosody isn't easy to achieve. 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? Cheers! -- Sergei Golovan
