Bug 461451
| Summary: | Inappropriate logrotate configuration for salinfo | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Tim Potter <tpot> |
| Component: | salinfo | Assignee: | Prarit Bhargava <prarit> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.2 | CC: | bzeranski, dchapman, peterm, syeghiay |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-09 14:33:21 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: | |||
Closing. No customer has complained about this issue and it is unlikely we'll issue a fix. P. |
Description of problem: The salinfo package comes with some configuration for logrotate which is inappropriate and unnecessary. The salinfo daemon creates files (basically timestamped firmware error records) with unique filenames so rotation is not required. Treating the files in /var/log/salinfo/{decoded,raw} as logs results in zero length files being created where data is expected, with the originals being moved to a subdirectory with .1 appended to the filename. Management applications expect the SAL error records to remain in the /var/log/salinfo directory until deleted by an administrator. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: