Bug 248982 - -r option in /etc/sysconfig/syslog breaks rsyslog
Summary: -r option in /etc/sysconfig/syslog breaks rsyslog
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-20 01:46 UTC by Jonathan Kamens
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-07-23 15:12:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2007-07-20 01:46:02 UTC
I have "-r" as one of the flags in SYSLOGD_OPTIONS in /etc/sysconfig/syslog. 
When I upgraded to rsyslog as part of a "yum update" against devel, it copied
/etc/sysconfig/syslog to /etc/sysconfig/rsyslog, preserving the "-r" flag, and
thus causing rsyslog to fail to start up properly.

I think the upgrade from sysklog to rsyslog probably needs to be a bit smarter
about stuff in /etc/sysconfig/syslog.

Comment 1 Jonathan Kamens 2007-07-20 01:47:10 UTC
Also, the /etc/sysconfig/rsyslog that ships with rsyslog still claims that -r
does something that it doesn't and still lists -m 0 even though (according to
the man page) it doesn't do anything with rsyslogd.

Comment 2 Jonathan Kamens 2007-07-20 01:54:04 UTC
As best as I can tell, the equivalent of "-r" in sysklogd is "-r 0" in rsyslogd.


Comment 3 Peter Vrabec 2007-07-20 10:53:11 UTC
It should be fixed in rsyslog-1.17.1-1.fc8


Comment 4 Rainer Gerhards 2007-07-20 10:55:24 UTC
I am the rsyslog maintainer.

I will fix the -r option in 1.17.2. The rule, I think, should be that if -r is
NOT followed by a number, that means -r 0, which is compatible with what
sysklogd did. Will check on -m 0.

Comment 5 Rainer Gerhards 2007-07-20 13:11:52 UTC
I have now changed the -r option, its cvs and will be available in 1.17.2 as
said before. The -m option is fully functional, that was a doc error. Its
corrected now.

Comment 6 Peter Vrabec 2007-07-23 15:11:44 UTC
upstream version 1.17.2 was just built


Note You need to log in before you can comment on or make changes to this bug.