umurmur doesn't create PID file

[GoogleCodeExporter]

>What steps will reproduce the problem?

Running umurmurd with the -d flag doesn't create a PID file when combined with 
-p 

>What is the expected output? What do you see instead?

Expecting '/usr/bin/umurmurd -d -r -p /run/umurmurd.pid -c 
/etc/umurmur/umurmur.conf' to produce a file in /run/ Instead no file is 
created, unless run without -d.

>What version of the product are you using? On what operating system?

uMurmur version 0.2.15 ('Drool'). Mumble protocol 1.2.4
Arch Linux Arm

Original issue reported on code.google.com by erogl...@gmail.com on 22 Aug 2014 at 5:38

[GoogleCodeExporter]

That's expected behavior. If you run with '-d' you have a controlling terminal 
and thus don't need to find the PID to send signals.

Original comment by fatbob.s...@gmail.com on 22 Aug 2014 at 8:25

• Changed state: WontFix

[GoogleCodeExporter]

It's fine if you don't want to fix it but at least warn the user that he's 
setting a useless flag or at least document it as such.

Original comment by erogl...@gmail.com on 24 Aug 2014 at 1:22

[GoogleCodeExporter]

I just can't imagine a valid use case where one would want to run it with both 
'-d' and '-p' flags, even if I try hard. The 'do not daemonize' mode is 
intended for debugging.

Original comment by fatbob.s...@gmail.com on 24 Aug 2014 at 2:20

[GoogleCodeExporter]

I like -d since it keeps a log of the process in systemd (such as who connects 
and disconnects) and I was going to attempt to use this 
https://github.com/ohaal/murmur-failover-daemon which requires umurmur to write 
it's PID to a file.

I suppose I can try it with no log since it won't get fixed.

Original comment by erogl...@gmail.com on 26 Aug 2014 at 3:01

[GoogleCodeExporter]

uMurmur logs everything (like connects/disconnects) to syslog by default. If 
that for some reason is not suitable there is the option to log to a file 
specified in the conf. 

Original comment by fatbob.s...@gmail.com on 26 Aug 2014 at 6:31