Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ sadc(1M) — Motorola System V 88k Release 4 Version 4.3

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

crontab(1)

timex(1)

sar(1M)

sadc(1M)  —  ADMINISTRATOR COMMANDS

NAME

sadc: sa1, sa2, sadc − system activity report package

SYNOPSIS

/usr/lib/sa/sadc [t n] [ofile] /usr/lib/sa/sa1 [t n] /usr/lib/sa/sa2 [−ubdycwaqvmpgrkxDSAC] [−s time] [−e time] [−i sec]
                [−P processor-id]

DESCRIPTION

System activity data can be accessed at the special request of a user (see sar(1M)) and automatically on a routine basis.  The operating system contains several counters that are incremented as various system actions occur.  These include counters for processor utilization, buffer usage, disk and tape I/O activity, TTY device activity, switching and system-call activity, file-access, queue activity, inter-process communications, paging and Remote File Sharing. 

Some of these counters (those in the si member of the binary activity record produced by sadc) are maintained separately for each processor that is or has been online in the system.  For each separately maintained counter, the system also maintains a corresponding aggregate counter.  The per-processor counters are a measure of the actions performed by each processor in the system.  The corresponding aggregate counters represent a measure of the same actions performed by the system as a whole.  For uni-processing, there is only one per-processor set of data. 

sadc and shell procedures, sa1 and sa2, are used to sample, save, and process data. 

sadc, the data collector, samples system data n times, with an interval of t seconds between samples.  The sampling interval t should be greater than 5 seconds; otherwise, the activity of sadc itself may affect the sample.  If t and n are omitted, a special record is written.  This facility is used at system boot time, when booting to a multiuser state, to mark the time at which the counters restart from zero.  For example, the /sbin/init.d/perf file writes the restart mark to the daily data by the command entry:

su sys −c "/usr/lib/sa/sadc /var/adm/sa/sa‘date +%d‘"

sadc writes system activity records in binary format.  This format includes information describing per processor system activity and counters describing aggregate system activity.  If ofile is not specified, sadc writes this data to standard output.  If ofile is specified, sadc writes the data to ofile. 

If the -P option is used, sa2 reports system activity information that applies to the processor specified by processor-id to standard output.  The -P option applies to multi-processing only. 

The shell script sa1, a variant of sadc, is used to collect and store data in binary file /var/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 following entries in /var/spool/cron/crontabs/sys will produce records every 20 minutes during working hours and hourly otherwise:

0 ∗ ∗ ∗ 0-6 /usr/lib/sa/sa1
20,40 8−17 ∗ ∗ 1−5 /usr/lib/sa/sa1

See crontab(1) for details. 

EXAMPLE

The shell script sa2, a variant of sar, writes a daily report in the file /var/adm/sa/sardd.  The options are explained in sar(1).  The following entry in /var/spool/cron/crontabs/sys will report important activities hourly during the working day:

5 18 ∗ ∗ 1−5 /usr/lib/sa/sa2 −s 8:00 −e 18:01 −i 1200 −A

FILES

/var/adm/sa/sadd daily data file for system as a whole

/var/adm/sa/sardd
daily report file

/tmp/sa.adrfl address file

SEE ALSO

crontab(1), timex(1), sar(1M)
 

  —  System Performance Analysis Utilities

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026