-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/22/15 08:13, 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 First of all, I find this odd. The update to F22 should have resulted in an update from rsyslog-7.4.10-5.fc21.x86_64 to rsyslog-8.8.0-2.fc22.x86_64 with the PID now being /var/run/rsyslogd.pid. And, note there is a BZ on this, one should edit /etc/logrotate.d/syslog to reflect the change. > > 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? Not sure about that at the moment. - -- Sorta what I want to say when folks habitually complain about Fedora - https://youtu.be/ZArl8fTfub4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWHXtAACgkQ4JnKjVbCBvpVggCeLe3orb00UZ5OReXqZe2qwfcE 1dUAnjodjIR77zYRrtRbsnAJvpi2LwFA =h6m9 -----END PGP SIGNATURE----- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
