Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!virtech!jje
From: jje@virtech.uucp (Jeremy J. Epstein)
Newsgroups: comp.unix.i386
Subject: Re: disk logging and sar
Summary: must run sadc(1M) to collect the data before sar(1) can analyze
Keywords: logging
Message-ID: <1990Jan8.145201.4251@virtech.uucp>
Date: 8 Jan 90 14:52:01 GMT
References: <9@cimcor.MN.ORG>
Organization: Virtual Technologies Inc.
Lines: 24

In article <9@cimcor.MN.ORG>, mike@cimcor.MN.ORG (Michael Grenier) writes:
> I'd like to enable the 'sar -d' command for some block disk
> drivers I'm writing. How do I do this?
> Right now, sar -d doesn't give me anything.

Before you can use sar to show data, you must have collected the
data using sadc(1M).  The sadc(1M) man page gives some suggested
cron entries to generate the data at 20 minute intervals (too long
when debugging, but OK for normal monitoring).  Make sure that you
put the commands in the crontab file for 'sys', and set the permissions
for /usr/adm/sa appropriately.  Also, you probably want to initialize
sadc at boot time so you get a zero-point.

The other key thing once you're gathering data is updating the right
data structures (in your disk driver)...does anyone recall what
structures sadc reads to accumulate the statistics?

Another tool worth looking at is sadp, which can generate some nify
histograms and graphs of cylinder usage....
-- 
Jeremy Epstein
TRW Systems Division
2750 Prosperity Avenue
FV10/5010