Red Hat Bugzilla – Bug 241176
logrotate file does not trigger daemon reload
Last modified: 2013-04-12 15:09:27 EDT
Description of problem:
the logrotate file does not specifiy any post action to ensure the daemon starts
a new log file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start freeradius
2. run logrotate
rotated file continues to be used.
daemon starts new log file
/etc/logrotate.d/radiusd probably needs something like
/etc/init.d/radiusd reload 2> /dev/null || true
Which log files are affected by this for you?
Adding this to each section could end in several reloads at the same time.
It applies to every file that would be held open by the application during a
transferred from Thomas Woerner to John Dennis, requested by Steve Grubb.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. This request will
be reviewed for a future Red Hat Enterprise Linux release.
OK, I've gone through the current RHEL5 sources examining how the daemon handles
log files specifically when the daemon is requested to reload.
The conclusion is a little surprising, it would appear that the radius daemon
does not behave like a typical daemon in that it _never_ holds log files open.
They are opened and closed for each entry written. As a consequence there is no
need to trigger a reload on logrotate as the files are not in continuous use.
This makes this BZ redundant as the requested functionality is not needed. I am
closing as NOTABUG.