Description of problem:
Installing both syslog-ng and rsyslog causes no messages to make there way to
/var/log/messages, and rsyslog.spec does not explicitly conflict with syslog-ng.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -ivh rsyslog-3.14.1-2.fc9.src.rpm
2. grep "Conflicts:" %_topdir/SPECS/rsyslog.spec |grep -i syslog-ng
These two packages have an implicit conflict, that has no sane way to resolve.
There is a solution for the problem: read the comments >= #16 of bug #400661.
Re: comment #1
OK, so there may be a SANE way to resolve it...
Apparently my bug search was too narrow, I think I only looked in
version:rawhide and or version:8 for the bug.
Assumption: both daemons "using the same the pid file (/var/run/syslogd.pid)",
would cause the second one that is fired up by init (or the new init replacment)
to either kill the first one or itself.
Apparently Peter Vrabec <firstname.lastname@example.org> decided that was not such a great idea.
from the rsyslog-3.14.1-2.fc9.src.rpm rsyslog.spec Change log:
* Wed Jan 16 2008 change pid filename and use logrotata script from sysklogd
* Fri Jan 18 2008 use rsyslog own pid file
looking at the syslog-ng-2.0.8-1.fc9.src.rpm syslog-ng.spec ... Any chance you
(JPO) have a decent working relation ship with Peter, and can convince him it is
a good idea? :}
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Adding to F10Blocker. No file conflicts are allowed in the repo (and I just verified this is still the case as of rawhide 20080913)
fixed, rsyslog and syskog-ng use same pidfile and logrotate file since: