Hey Tom,
I don't have a RHEL init script handy, but you may want to take a look inside it to see if /etc/init.d/syslog-ng for 3.0.4 creates a link /var/run/syslogd.pid file to syslog-ng's pid upon starting. This way, the default logrotate does a HUP on syslog(-ng)'s PID with no change necessary to your logrotate configuration. This is of course assuming your /etc/logrotate.d/syslog configuration does a HUP on /var/run/syslogd.pid (which looks to be the default for CentOS 5.4). If it's calling an init script or service reload, you may want to symlink /etc/init.d/syslog to /etc/init.d/syslog-ng, or you could just do as you originally planned and generate an /etc/logrotate.d/syslog-ng file.
To anyone else reading this thread who is using ubuntu 8.04 (and probably other debian releases), logrotate still exists, but log rotation for files such as /var/log/syslog is executed via Cron. Have a look at /etc/cron.daily/sysklogd and you will see a shell script that runs the syslogd-listfiles binary in order to get a list of files that it rotates in that daily cron job. As such, if you're running ubuntu you may have to generate your own logrotate.d/files after your upgrade to syslog-ng (I could be wrong on this though, as I am using my own packaging). Something like this should work:
#cat /etc/logrotate.d/syslog-ng
/var/log/syslog
{
weekly
missingok
compress
create 600 root root
rotate 8
sharedscripts
postrotate
if [ -f /var/run/syslog-ng.pid ]; then \
kill -HUP `cat /var/run/syslog-ng.pid`; \
fi;
endscript
}
--
Lance Laursen
Demonware Systems Engineer