Bug 352831

Summary: adding the -d option to the execution line in /etc/init.d/sysstat fails to track disk stats after the daily roll of the /var/log/sa files.
Product: Red Hat Enterprise Linux 5 Reporter: brian
Component: sysstatAssignee: Ivana Varekova <varekova>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: low    
Version: 5.0   
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: 2007-11-08 11:05: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:

Description brian 2007-10-25 17:33:15 UTC 
I've read the sadc man page and found that if I want to track disk usage stats I
need to execute sadc with the -d flag.  So I modified the /etc/init.d/sysstat
script to start up sadc with the -d option.  This appears to work as expected to
start with.  However after the daily roll of the stats files in /var/log/sa the
-d value seems to get forgotten as the next day's file does not have disk stats.
 I have been looking for what is restarting the file daily but I'm not seeing an
obvious answer there to see if I just need to add -d somewhere else. 

Tracking disk stats have value to us as we are using a number of SAN attached
storage arrays on a server and we wish to track which of these devices are being
used and how they are being used.
Comment 1 Ivana Varekova 2007-11-08 11:05:21 UTC 
I'm not sure whether you have not edited /etc/cron.d/sysstat file but there is
necessary to edit /usr/lib{64}/sa/sa1 script - which creates an output record to
/var/log/sa/sa{date} file per 10 minutes (see /etc/cron.d/sysstat).
/etc/init.d/sysstat only creates the initial record to /var/log/sa/sa{date}.