I'm sorry but the systemd service file provided didn't change the behavior. The
issue is still the same on my machine.
Here are my tests with 2 configurations:
A/with no "host" specified
# systemctl status mumble-server
● mumble-server.service - Mumble VoIP server
Loaded: loaded (/lib/systemd/system/mumble-server.service; enabled)
Active: active (running) since dim 2015-04-12 23:57:15 CEST; 41s ago
Docs: man:murmurd(1)
file:///usr/share/doc/mumble-server/README
http://wiki.mumble.info/wiki/Running_Murmur
Process: 853 ExecStart=/usr/sbin/murmurd -ini /etc/mumble-server.ini
(code=exited, status=0/SUCCESS)
Process: 788 ExecStartPre=/usr/bin/install -o mumble-server -g adm
-d /var/run/mumble-server (code=exited, status=0/SUCCESS)
Main PID: 1362 (murmurd)
CGroup: /system.slice/mumble-server.service
└─1362 /usr/sbin/murmurd -ini /etc/mumble-server.ini
# cat /var/log/mumble-server/mumble-server.log
<W>2015-04-12 23:57:14.916 Initializing settings
from /etc/mumble-server.ini (basepath /etc)
<C>2015-04-12 23:57:14.919 Adding 1 CA certificates from certificate
file.
<W>2015-04-12 23:57:14.919 OpenSSL: OpenSSL 1.0.1k 8 Jan 2015
<C>2015-04-12 23:57:14.920 Successfully switched to uid 126
<W>2015-04-12 23:57:15.135 ServerDB: Opened SQLite
database /var/lib/mumble-server/mumble-server.sqlite
<W>2015-04-12 23:57:15.137 Resource limits were 0 0
<W>2015-04-12 23:57:15.137 Successfully dropped capabilities
<W>2015-04-12 23:57:15.162 Murmur 1.2.8 (1.2.8-2) running on X11: Debian
GNU/Linux 8.0 (jessie): Booting servers
<W>2015-04-12 23:57:15.184 1 => Announcing server via bonjour
<W>2015-04-12 23:57:15.273 1 => Registration needs nonempty
'registername', 'registerpassword' and 'registerurl', must have an empty
'password' and allowed pings.
<W>2015-04-12 23:57:15.273 Object::connect: No such slot
MurmurDBus::userTextMessage(const User *, const TextMessage &)
B/with "host" specified
# systemctl status mumble-server
● mumble-server.service - Mumble VoIP server
Loaded: loaded (/lib/systemd/system/mumble-server.service; enabled)
Active: active (running) since lun 2015-04-13 00:12:21 CEST; 16s ago
Docs: man:murmurd(1)
file:///usr/share/doc/mumble-server/README
http://wiki.mumble.info/wiki/Running_Murmur
Process: 846 ExecStart=/usr/sbin/murmurd -ini /etc/mumble-server.ini
(code=exited, status=0/SUCCESS)
Process: 780 ExecStartPre=/usr/bin/install -o mumble-server -g adm -d
/var/run/mumble-server (code=exited, status=0/SUCCESS)
Main PID: 1353 (murmurd)
CGroup: /system.slice/mumble-server.service
└─1353 /usr/sbin/murmurd -ini /etc/mumble-server.ini
# cat /var/log/mumble-server/mumble-server.log
<W>2015-04-13 00:12:20.913 Initializing settings
from /etc/mumble-server.ini (basepath /etc)
<W>2015-04-13 00:12:20.914 Binding to address 192.168.1.150
<C>2015-04-13 00:12:20.916 Adding 1 CA certificates from certificate
file.
<W>2015-04-13 00:12:20.916 OpenSSL: OpenSSL 1.0.1k 8 Jan 2015
<C>2015-04-13 00:12:20.917 Successfully switched to uid 126
<W>2015-04-13 00:12:21.121 ServerDB: Opened SQLite
database /var/lib/mumble-server/mumble-server.sqlite
<W>2015-04-13 00:12:21.123 Resource limits were 0 0
<W>2015-04-13 00:12:21.124 Successfully dropped capabilities
<W>2015-04-13 00:12:21.143 Murmur 1.2.8 (1.2.8-2) running on X11: Debian
GNU/Linux 8.0 (jessie): Booting servers
<W>2015-04-13 00:12:21.203 1 => Server: TCP Listen on
192.168.1.150:64738 failed: The address is not available
<W>2015-04-13 00:12:21.301 1 => Stopped
I've seen ssh uses 2 systemd files : "ssh.socket" and "ssh.service",
shouldn't mumble use also a ".socket"? I don't know how the ssh systemd
socket handle the fact the user can choose the SSH port is a separate
config file.
Thanks a lot for the help !
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
