Bug 81294
Summary: | keeping old sar data should be configurable. | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Need Real Name <jackal> |
Component: | sysstat | Assignee: | Nils Philippsen <nphilipp> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | paul |
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-01-27 12:26:07 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
Need Real Name
2003-01-07 18:30:38 UTC
I concur with you that logrotate should handle this. I'm inclined to remove the "rm" line from sa2 and have sysstat logrotate scripts in a future product/version, but it would be even better if upstream had such changes. Wouldn't tmpwatch be the better tool to handle cleaning up old sar data? Well, "further inverstigation into the matter" revealed that sysstat won't be easily converted to work with logrotate, so for the time being the sa2 script will remain in charge to clean up old sar data. I'm not quite sure about whether the find command with suitable changes to be able to configure the period of time for sar data to be kept or a replacement tmpwatch construct is better -- but so far the find construct has worked, so unless someone gives me a compelling reason why using tmpwatch would be better, I'll leave it that way. fixed in 5.0.0-0.6 Will this make it through to Fedora Core? |