sa1 and sa2


 
Thread Tools Search this Thread
Operating Systems AIX sa1 and sa2
# 1  
Old 11-20-2006
sa1 and sa2

Hi all, does anyone know what is the relationship between sa1 and sa2? Apparently both have to be included to make reporting work. If you include only 1, let's say sa2, the file is created but there's no content inside. Can someone shed some light and also provide examples of sa1 and sa2? Thanks a whole bunch.
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

sysout from crontab process /usr/lib/sa/sa1

Hi I've found this crontab entry to run sa1 on sunOs box but I don't know where the result of this command is being stored. Is there a standard location for this? I assume the command is supposed to be storing the details somewhere.. Thanks (2 Replies)
Discussion started by: Grueben
2 Replies

2. Red Hat

How do sa1/sar time intervals work?

Hi, I have set up sar on my RedHat and Fedora Linux systems. I am running sa1 from cron: 0 8-17 * * 1-5 /usr/lib/sa/sa1 1200 3 & The 1200 and 3 parameters tell sa1 to save data every 1200 seconds (== 20 minutes) and to write 3 times. When I run sar to observe my data, I'll see... (1 Reply)
Discussion started by: mschwage
1 Replies

3. Solaris

Sun Solaris 10 - SA1,2,and 3 PDF's

Dear All, Where can i get the Sun Solaris 10 ( SA 1,2, and 3) in pdf ? (4 Replies)
Discussion started by: viswanadhan
4 Replies
Login or Register to Ask a Question
sadc(8) 						    BSD System Manager's Manual 						   sadc(8)

NAME
sadc -- system activity data collector SYNOPSIS
/usr/lib/sa/sadc [-m mode] [t n] [ofile] DESCRIPTION
The sadc tool is used to collect cumulative system activity data. The sample system data is collected at intervals t seconds apart, in a loop n times. The binary sample data is written to ofile if specified. Otherwise, the binary data is written to stdout. If the ofile file does not exist, it is created, otherwise it is truncated. sadc is intended to be used as the engine behind the sar(1) command, and is not typically invoked on the command line. Two shell scripts, sa1 and sa2, are provided to drive the typical sampling, saving, and reporting process. OPTIONS
The following options modify the way data is collected by sadc. -m mode Modify the collection of system statistics as specified by mode. Currently only one mode is supported. PPP By default, the collection of ppp network interface statistics is turned off. This is because the number of ppp connec- tions can be very high, causing the raw data file to grow unexpectedly large, especially when samples are collected at short intervals. Use the PPP mode to turn the collection back on. EXAMPLES
/usr/lib/sa/sadc 15 20 /tmp/sample.out This call collects 20 samples at 15 second intervals. The binary data is written to the /tmp/sample.out file FILES
/var/log/sa/sadd Default daily activity file that holds the binary sampling data. dd are digits that represent the day of the month. /usr/lib/sa/sa1 Shell script used to drive the sar data collection. /usr/lib/sa/sa2 Shell script used to drive the sar data reporting. SEE ALSO
fs_usage(1), netstat(1), sar(1), sc_usage(1), top(1), vm_stat(1), iostat(8), sa1(8), sa2(8) Mac OS X Jul 25 2003 Mac OS X