ExecStartPre=
in the unit file
]]># mkdir /var/run/murmur
# chown murmur:murmur /var/run/murmur
# chmod 777 /var/run/murmur
#uname=
in /etc/murmur.ini
]]>Sorry I can't be of more help, but it seems to have something to do with a conflict between the service and the desired pid file.
]]>murmurd -fg -ini /etc/murmur.ini
systemd[1]: PID file /run/murmur/murmur.pid not readable (yet?) after start.
the daemon stayed alive and working.
If the problem comes again I'll report it as a bug but for now I'm not sure what's happening.
Thanks for your help.
]]>You could probably jsut avoid the pidfile all together and run the service in non-forking mode.
[Unit]
Description=Mumble Daemon
After=network.target
[Service]
ExecStart=/usr/sbin/murmurd -fg -ini /etc/murmur.ini
[Install]
WantedBy=multi-user.target
lrwxrwxrwx 1 root root 6 Jul 21 02:46 run -> ../run/
I think it is ok.
]]>I installed murmur form "community" and started it with
systemctl start murmur
The service starts but restarts every two minutes or so with these lines in journalctl:
PID file /run/murmur/murmur.pid not readable (yet?) after start.
murmur.service operation timed out. Terminating.
Unit murmur.service entered failed state.
murmur.service holdoff time over, scheduling restart.
Any clues?
]]>