On 06/21/2015 07:46 PM, Sam Varshavchik wrote:
jd1008 writes:
>
>
> On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
>> After updating to F22, after the system is up for some period of
>> time, I have not determine for how long, looks like something
>> removes /var/run/syslogd.pid
>>
>> Consequently, logrotate eventually rotates /var/log/messages to
>> /var/log/messages-yyyymmdd (same for several other /var/log files),
>> but can't find syslogd's PID to SIGHUP it, so that syslog can reopen
>> the log files.
>>
>> I vaguely recall seeing some config files that defines
>> expiration/cleanup retention period for stuff in /var/run. Anyone
>> recall where that lives?
>>
>>
>>
> see /etc/logrotate.d
That's not what I asked.
Why don't you try by adding:
/var/log/messages {
rotate 5
weekly
postrotate
/usr/bin/killall -HUP syslogd
endscript
}
to /etc/logrotate.conf
It says keep a backlog for 5 weeks.
Rotate the log weekly.