Sponsored Content
Full Discussion: sar
Special Forums Hardware Filesystems, Disks and Memory sar Post 31477 by kevinb on Friday 8th of November 2002 08:58:54 AM
Old 11-08-2002
Question sar

We have a script that uses

sar -u 1 10 | awk '/Average/ { print ( $2 + $3 ) }'

to get the CPU usage of a mutli engine machine. We think we are getting wrong information from the above string. We think it is adding up the total of the 12 engines and reporting back the total not the overall average. Can anyone add their two cents as to what might be wrong?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sar and inedt

I am the newest of newbies. Please excuse my ignorance. I have come across these two executables, sar and inedt, and am unfamiliar with their function. I have searched my limited resource library and would appreciate any insight available. Rgds, Ren (7 Replies)
Discussion started by: Ren
7 Replies

2. AIX

sar problem

when i used sar -u -f xxxx i've got the result like the following ... 18Aug200614:45:00 0 1 0 99 18Aug200614:50:00 1 1 0 98 18Aug200622:42:46 1 0 0 98 18Aug200607:00:00 0 0 100 0 18Aug200608:20:48 ... (0 Replies)
Discussion started by: pohnpohnpohn
0 Replies

3. HP-UX

Sar

Hey guys in sar -v 5 5 command what is the proc means. (1 Reply)
Discussion started by: sbn
1 Replies

4. Solaris

sar tool

Hi All, I have come through this very nice tool which stores the week performance stats in solaris, but its only stores the stats for 8 in the morning to 5 in the evening. i want to extend the facility to work 24 hrs . Does anyone know how to do that? Thanks in advance (1 Reply)
Discussion started by: azs0309
1 Replies

5. AIX

sar

I am trying to set up sar on my AIX server. We have been running sar and getting reports on out Linux boxes in the past but would like to try to do the same in AIX. On my Linux i have a sar.sh that looks like this: #!/bin/bash LC_ALL=C sar -A -f /var/log/sa/sa27 > /server023.txt LC_ALL=C sar -A... (1 Reply)
Discussion started by: seacros
1 Replies

6. Solaris

Sar Issue

Dear All, I had added these lines in crontab. 0 * * * 0-6 /usr/lib/sa/sa1 00,15,30,45 * * * 0-6 /usr/lib/sa/sa1 5 18 * * 0-6 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A After adding these lines I have to get sar file. But here I am not getting any files in /var/adm/sa directory in one... (2 Replies)
Discussion started by: lbreddy
2 Replies

7. AIX

SAR

I am running below script to display last 48 hour data but the output is not displaying heading - AIX eqrdb26u1 1 6 00CFD5E34C00 01/21/10 System configuration: lcpu=8 ent=2.00 mode=Uncapped 22:31:40 %usr %sys %wio %idle physc %entc and footer - Average 25 9 ... (1 Reply)
Discussion started by: noorm
1 Replies

8. Solaris

sar output

One of my servers giving all zero sar output. Could anyone explain this behaviour. Thanks CHaandana Sample: 10:43:37 %usr %sys %wio %idle 16:15:01 2 1 0 97 16:20:02 2 1 0 97 16:25:02 2 1 0 97 16:30:01 ... (3 Replies)
Discussion started by: chaandana
3 Replies

9. Shell Programming and Scripting

Mpstat and sar

HI I ma using mpstat and sar commands to check the cpu utilisation but the results are not matching .I dont understand why thisis happening? $ sar -u 12 5 Linux 2.6.9-89.35.1.ELhugemem (abcd.efgh.com) 03/07/2013 02:43:16 AM CPU %user %nice %system %iowait %idle... (1 Reply)
Discussion started by: ptappeta
1 Replies

10. UNIX for Advanced & Expert Users

Sar during a test

Hi All, I am trying to run sar on a Redhat server during a test I am performing for a couple of hours. I would like to get the sar metrics for every second (instead of the regularly set up 10 minute interval in the cron). What is the most efficient way to do this? Thanks, Shahzad (6 Replies)
Discussion started by: sleo
6 Replies
SA(8)							    BSD System Manager's Manual 						     SA(8)

NAME
sa -- print system accounting statistics SYNOPSIS
sa [-abcdDfijkKlmnqrstu] [-P file] [-U file] [-v cutoff] [file ...] DESCRIPTION
The sa utility reports on, cleans up, and generally maintains system accounting files. The sa utility is able to condense the information in /var/account/acct into the summary files /var/account/savacct and /var/account/usracct, which contain system statistics according to command name and login id, respectively. This condensation is desirable because on a large sys- tem, /var/account/acct can grow by hundreds of blocks per day. The summary files are normally read before the accounting file, so that reports include all available information. If file names are supplied, they are read instead of /var/account/acct. After each file is read, if the summary files are being updated, an updated summary will be saved to disk. Only one report is printed, after the last file is processed. The labels used in the output indicate the following, except where otherwise specified by individual options: avio Average number of I/O operations per execution cp Sum of user and system time, in minutes cpu Same as cp k CPU-time averaged core usage, in 1k units k*sec CPU storage integral, in 1k-core seconds re Real time, in minutes s System time, in minutes tio Total number of I/O operations u User time, in minutes The options to sa are: -a List all command names, including those containing unprintable characters and those used only once. By default, sa places all names containing unprintable characters and those used only once under the name ``***other''. -b If printing command statistics, sort output by the sum of user and system time divided by number of calls. -c In addition to the number of calls and the user, system and real times for each command, print their percentage of the total over all commands. -d If printing command statistics, sort by the average number of disk I/O operations. If printing user statistics, print the average number of disk I/O operations per user. -D If printing command statistics, sort and print by the total number of disk I/O operations. -f Force no interactive threshold comparison with the -v option. -i Do not read in the summary files. -j Instead of the total minutes per category, give seconds per call. -k If printing command statistics, sort by the cpu-time average memory usage. If printing user statistics, print the cpu-time average memory usage. -K If printing command statistics, print and sort by the cpu-storage integral. -l Separate system and user time; normally they are combined. -m Print per-user statistics rather than per-command statistics. -n Sort by number of calls. -P file Use the specified file for accessing the per-command accounting summary database, instead of the default /var/account/savacct. -q Create no output other than error messages. -r Reverse order of sort. -s Truncate the accounting files when done and merge their data into the summary files. -t For each command, report the ratio of real time to the sum of user and system cpu times. If the cpu time is too small to report, ``*ignore*'' appears in this field. -U file Use the specified file for accessing the per-user accounting summary database, instead of the default /var/account/usracct. -u Superseding all other flags, for each entry in the accounting file, print the user ID, total seconds of cpu usage, total memory usage, number of I/O operations performed, and command name. -v cutoff For each command used cutoff times or fewer, print the command name and await a reply from the terminal. If the reply begins with ``y'', add the command to the category ``**junk**''. This flag is used to strip garbage from the report. By default, per-command statistics will be printed. The number of calls, the total elapsed time in minutes, total cpu and user time in min- utes, average number of I/O operations, and CPU-time averaged core usage will be printed. If the -m option is specified, per-user statistics will be printed, including the user name, the number of commands invoked, total cpu time used (in minutes), total number of I/O operations, and CPU storage integral for each user. If the -u option is specified, the uid, user and system time (in seconds), CPU storage integral, I/O usage, and command name will be printed for each entry in the accounting data file. If the -u flag is specified, all flags other than -q are ignored. If the -m flag is specified, only the -b, -d, -i, -k, -q, and -s flags are honored. FILES
/var/account/acct raw accounting data file /var/account/savacct per-command accounting summary database /var/account/usracct per-user accounting summary database EXIT STATUS
The sa utility exits 0 on success, and >0 if an error occurs. SEE ALSO
lastcomm(1), acct(5), ac(8), accton(8) CAVEATS
While the behavior of the options in this version of sa was modeled after the original version, there are some intentional differences and undoubtedly some unintentional ones as well. In particular, the -q option has been added, and the -m option now understands more options than it used to. The formats of the summary files created by this version of sa are very different from the those used by the original version. This is not considered a problem, however, because the accounting record format has changed as well (since user ids are now 32 bits). AUTHORS
Chris G. Demetriou <cgd@postgres.berkeley.edu> BUGS
The number of options to this program is absurd, especially considering that there is not much logic behind their lettering. The field labels should be more consistent. The VM system does not record the CPU storage integral. BSD
May 18, 2007 BSD
All times are GMT -4. The time now is 10:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy