From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.0.0) Gecko/20020606
Description of problem:
By default sar only keeps 7 days of data.
That should be configurable.
"/etc/cron.daily/sysstat" calls "/usr/lib/sa/sa2 -A".
/usr/lib/sa/sa2 has a hardcoded "+7" in the file. That should be in a config
file and not the script.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd /var/log/sa
2. ls -al sar* |wc -l
Actual Results: I only had 9 days of sar data. Curious why 9 when that find
command says 7.
But regardless, what if I wanted 3 weeks of sar data.
Expected Results: I actually expected logrotate to handle this, but since sa2
has it hardcoded, the logs are being removed.
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
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?