Description:

the murmurd (murmur daemon) logs per default vie sed'ed config to /var/log/murmur/murmur.log

since we have systemd and its journal, it would be nicer to have it log to the journal instead (this is the feature request)


I tried this myself by setting "logfile=" in /etc/murmur.ini and restarting the service (systemctl restart murmur). this should work out of the box since empty murmur logfile means log to stdout and systemd default handling of stdout is append to journal, but:

systemctl hangs with a spawned process (systemd-tty-ask-password-agent --watch) for a while, finally exits with:

Jan 20 16:03:34 mobserv systemd[1]: Failed to start Mumble Daemon. [16/198]
Jan 20 16:03:34 mobserv systemd[1]: Unit murmur.service entered failed state
Jan 20 16:03:34 mobserv systemd[1]: murmur.service holdoff time over, scheduling restart.
Jan 20 16:03:34 mobserv systemd[1]: Stopping Mumble Daemon...
Jan 20 16:03:34 mobserv systemd[1]: Starting Mumble Daemon...

... and continuously restarts murmur.service


It would be really nice if murmur - per arch linux default - would use systemd's journal. Any additional log files as well as the logrotate handling are administrative overhead - systemd can do so much for us.


Additional info:
* murmur version: 1.2.3-9