FS#37058 - [murmur] logging to syslog ignoring settings in /etc/murmur.ini

Attached to Project: Community Packages
Opened by georg (fordprefect) - Wednesday, 25 September 2013, 16:08 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 23 October 2013, 01:55 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
running murmur on a fresh up-to-date archlinux machine always loggs to syslog facilities daemon and mark ingnoring settings made in /etc/murmur.ini
settings i tried:
1) logfile=/var/log/murmur/murmur.log
2) logfile=/dev/null
there is no data written to 1), all data goes to said syslog facilities.

Additional info:
* community/murmur 1.2.4-1
* community/rsyslog 7.4.2-1
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 23 October 2013, 01:55 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 17 October 2013, 15:43 GMT
There is nothing in the package which would prohibit murmur from logging to file. Are you certain you restarted murmur after making the changes and that murmur has write access to the directory you provided? If so, please report this upstream and post bug report url here.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 17 October 2013, 15:44 GMT
Nevermind, running murmur with -fg does this.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 17 October 2013, 15:46 GMT
Alright so this may or may not be an upstream bug depending on whether it is expected behavior. We're running the murmur daemon with -fg which keeps it in the foreground. Is it expected for it to log to some log still if it is provided in the .ini file? I think so. Looks like upstream bug.

Loading...