umurmurd exits (no error/warning) during wrong file permissions

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Specify a log-file
2. _umurmur is not the owner of the file
3. just the owner has write permissions

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

umumur simply exists where it should check if

1. The file exists
2. It can access it with write permissions.

umurmur currently lacks such a check and simply exists without any 
warning/error so it is hard to debug. I strumbled over it after I removed the 
"logfile" and umurmurd worked as exspected. I added the option back and it 
simply exists right after the start so I checked the file permissions in 
/var/log and the logfile was owned by root. I changed the permissions to 
_umurmur and since then the server works.

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

Lates Version and OpenBSD 5.5 on AMD64.

Please provide any additional information below.

Please do see above.


Kind regards,
Sebastian Rother

Original issue reported on code.google.com by [email protected] on 21 May 2014 at 5:00

[GoogleCodeExporter]

man, I'm sure glad you figured that out. Was driving me nuts. LOL. This can 
also be hacked around by the maintainer to either chown the logfile in the 
service script, or during pkg_add using PLIST.  I will email the maintainer of 
the OpenBSD package with this info and see if he is willing to patch around 
this little glitch since there hasn't been any activity on this thing for a bit.

Original comment by [email protected] on 2 Sep 2014 at 1:13

[GoogleCodeExporter]

There is a check and uMurmur tries to log an error, but it is lost since the 
chosen logging is to the file that couldn't be opened... This happens after 
daemonizing so stderr is unavailable. The way to solve this is probably to do a 
check for file access before daemonizing and write an error to stderr. Any 
thoughts?

Original comment by [email protected] on 2 Sep 2014 at 7:12

• Changed state: Accepted