jd1008 writes:
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.
Thanks for your suggestion, but you missed the part where I explicitly
referenced /var/run, and not /var/log. And I wasn't talking about rotating
files, but removing them, since what I suspected was happening is that
something was removing syslog's pid file in /var/run. I explained that in
the very first paragraph that you quoted, above.
But, anyway, I eventually figured out – and as I noted elsewhere in this
thread – that was I was recalling was the configuration in /etc/tmpfiles.d
It's the little details, like that, that matter a great deal…