Bug 109633
Summary: | Handling of uniquely-named traces. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Nicolas Mailhot <nicolas.mailhot> |
Component: | logrotate | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED WONTFIX | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | srevivo |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-06-02 17:36:14 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: |
Description
Nicolas Mailhot
2003-11-10 14:45:39 UTC
I don't think logrotate is meant to handle these type of situations. The tmpwatch utility might be better suited - it can delete files after they are a certain number of days old. tmpwatch won't do compression like logwatch... . Consider it a rfe then. From a technical POV this might be different, from an admin/user POV handling all sorts of traces/logs in the same files is a must. (for example some apps use combined cross-referenced logs and traces. So right now you have to use one logrotate file, another for tmpwarch and yet another for the compression. And be sure all of them match at all times, since the stuff is cross referenced. This is an admin's nightmare) I don't want to let this report sit here and pretend that anything is going to happen with it. A patch would be harder to argue with, but it's not likely that I'll ever make time to code the feature, given other priorities. That's fair if not exactly welcome |