Need help making syslog-ng, rsyslog, and sysklogd not conflict

[Chris Adams]

Once upon a time, Douglas E. Warner <silfreed at silfreed.net> said:
> I didn't realize RHEL 5.2 added rsyslog; I'll have to see if they did anything 
> to make them both installable at the same time.

I see it now; the logrotate script from both packages is the same and
attempts to HUP both daemons:

/var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {
    sharedscripts
    postrotate
	/bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true
	/bin/kill -HUP `cat /var/run/rsyslogd.pid 2> /dev/null` 2> /dev/null || true
    endscript
}


Maybe instead any system logger could symlink the PID file to a common
name in the init script?  I.e.:

start() {
	...
	daemon syslogd $SYSLOGD_OPTIONS
	ln -s /var/run/syslogd.pid /var/run/system-logger.pid
}


Then the logrotate config could just use that file (and be included
somewhere other than the various syslog packages).

I don't think it is valid to have more than one syslog type daemon
running at once, is it?

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.