sar(1M) sar(1M)
NAME
sa1, sa2, sadc - system activity report package
SYNOPSIS
/usr/lib/sa/sadc [tn] [ofile]
/usr/lib/sa/sa1 [tn]
/usr/lib/sa/sa2 [-i] [-u] [-b] [-d] [-y] [-c] [-w] [-a] [-q]
[-v] [-m] [-A] [-stime] [-etime] [-isec]
DESCRIPTION
System activity data can be accessed at the special request
of a user (see sar(1)) and automatically on a routine basis
as described here. The operating system contains a number
of counters that are incremented as various system actions
occur. These include CPU utilization counters, buffer usage
counters, disk and tape I/O activity counters, TTY device
activity counters, switching and system-call counters,
file-access counters, queue activity counters, and counters
for inter-process communications.
sadc and shell procedures, sa1 and sa2, are used to sample,
save, and process this data.
sadc, the data collector, samples system data n times every
t seconds and writes in binary format to ofile or to
standard output. If t and n are omitted, a special record
is written. This facility is used at system boot time to
mark the time at which the counters restart from zero. The
/etc/rc entry:
su adm -c "/usr/lib/sa/sadc /usr/adm/sa/sa`date +%d`"
writes the special record to the daily data file to mark the
system restart.
The shell script sa1, a variant of sadc, is used to collect
and store data in binary file /usr/adm/sa/sadd where dd is
the current day. The arguments t and n cause records to be
written n times at an interval of t seconds, or once if
omitted. The entries in crontab (see cron(1M)):
0 * * * 0,6 su adm -c "/usr/lib/sa/sa1"
0 8-17 * * 1-5 su adm -c "/usr/lib/sa/sa1 1200 3"
0 18-7 * * 1-5 su adm -c "/usr/lib/sa/sa1"
will produce records every 20 minutes during working hours
and hourly otherwise.
The shell script sa2, a variant of sar(1), writes a daily
report in file /usr/adm/sa/sardd. The flag options are
Page 1 (last mod. 1/16/87)
sar(1M) sar(1M)
explained in sar(1). The crontab entry:
5 18 * * 1-5 su adm -c "/usr/lib/sa/sa2 -s 8:00 -e 18:01 -i
3600 -A"
will report important activities hourly during the working
day.
The structure of the binary daily data file is:
struct sa {
struct sysinfo si; /* defined in
/usr/include/sys/sysinfo.h */
struct minfo mi; /* defined in
/usr/included/sys/sysinfo.h */
int szinode; /* current size of inode table */
int szfile; /* current size of file table */
int szproc; /* current size of proc table */
int szlckf; /* current size of file record
header table */
int szlckr; /* current size of file record
lock table */
int mszinode; /* maximum size of inode table */
int mszfile; size of file table */
int mszproc; /* maximum size of proc table */
int mszlckf; /* maximum size of file record
header table */
int mszlckr; /* maximum size of file record
lock table */
long inodeovf; /* cumulative overflows of inode
table since boot*/
long fileovf; /* cumulative overflows of file
table since boot */
long procovf; /* cumulative overflows of proc
table since boot */
time_t ts; /* time stamp */
int apstate;
long devio[NDEVS][4];/* device unit information */
#define IO_OPS 0 /* number of I/O requests since
boot */
#define IO_BCNT 1 /* number of blocks transferred
since boot */
#define O_ACT 2 /* cumulative time in ticks when
drive is active */
#define IO_RESP 3 /* cumulative I/O response time in
ticks since boot */
};
FILES
/usr/lib/sa/sa1
Page 2 (last mod. 1/16/87)
sar(1M) sar(1M)
/usr/lib/sa/sa2
/usr/lib/sa/sadc
/usr/adm/sa/sadd daily data file
/usr/adm/sa/sardd daily report file
/tmp/sa.adr address file
SEE ALSO
cron(1M), sag(1G), sar(1), timex(1).
Page 3 (last mod. 1/16/87)