I see this line in /etc/logrotate.d/syslog:
/bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null||true
The PID file for rsyslog is actually /var/run/rsyslogd.pid, therefore once logrotate runs the new log files, e.g., messages, maillog, etc., are empty. Sound like a bug to you all?
I'm running F22 kernel 4.0.4-301.fc22.x86_64 and I just upgraded via dnf.
Thanks,
-- Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com 617-947-4263, Twitter: @allmanpc
On 06/11/15 03:11, Mark C. Allman wrote:
I see this line in /etc/logrotate.d/syslog:
/bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null||true
The PID file for rsyslog is actually /var/run/rsyslogd.pid, therefore once logrotate runs the new log files, e.g., messages, maillog, etc., are empty. Sound like a bug to you all?
I'm running F22 kernel 4.0.4-301.fc22.x86_64 and I just upgraded via dnf.
Yes, it seems the name of the pid file has changed between rsyslog-7.4.10-5.fc21 and rsyslog-8.8.0-2.fc22 but the associated logrotate file wasn't updated to reflect the change.
So, you should file a bugzilla against rsyslog in F22.