Bug 241176
| Summary: | logrotate file does not trigger daemon reload | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Martin Poole <mpoole> |
| Component: | freeradius | Assignee: | John Dennis <jdennis> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | alan.tyson, tao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-23 11:51:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 logrotate. 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. |
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): freeradius-1.1.3-1.1.el5 How reproducible: always. Steps to Reproduce: 1. start freeradius 2. run logrotate 3. Actual results: rotated file continues to be used. Expected results: daemon starts new log file Additional info: /etc/logrotate.d/radiusd probably needs something like postrotate /etc/init.d/radiusd reload 2> /dev/null || true endscript