10 More Discussions You Might Find Interesting
1. AIX
How to monitor the IBM AIX server for I/O usage, memory usage, CPU usage, network usage, storage usage? (3 Replies)
Discussion started by: laknar
3 Replies
2. Solaris
Hello Friends,
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
=========================================================================
$ prstat -a
... (4 Replies)
Discussion started by: mahive
4 Replies
3. Solaris
Hi,
I want to monitor the current cpu usage, monitor usage , disk I/o and network utlization for solaris using SNMP.
I want the oids for above tasks.
can you please tell me that
Thank you (2 Replies)
Discussion started by: S_venkatesh
2 Replies
4. Linux
We are working in the office where about 5-6 machines have Internet access. We pay for each GB of traffic we consume and that's quite expensive. Almost no worker download files. Just surfing websites (including our corporate one that is located outside of local network thus we pay for accessing it... (5 Replies)
Discussion started by: FractalizeR
5 Replies
5. HP-UX
how can I find cpu usage memory usage swap usage and
I want to know CPU usage above X% and contiue Y times and memory usage above X % and contiue Y times
my final destination is monitor process
logical volume usage above X % and number of Logical voluage above
can I not to... (3 Replies)
Discussion started by: alert0919
3 Replies
6. Programming
Hi all,
When I have a below while loop in my code (This observation is same for C and Perl)
i= 0;
while(1)
{
i++;
}
for above the CPU uses goes beyond 49% on hp-ux machine, why cpu usage increase at this level for just a simple while loop?
and if I have a single print statement... (2 Replies)
Discussion started by: zing_foru
2 Replies
7. UNIX for Dummies Questions & Answers
can anyone tell me How to check memory and CPU usage of a certain process (1 Reply)
Discussion started by: ccp
1 Replies
8. Programming
Please tell me solaris functions/api for getting following information
1- Function that tells how much memory used by current process
2- Function that tells how much memory used by all running processes
3- Function that tells how much CPU is used by current process
4- Function that tells how... (1 Reply)
Discussion started by: mansoorulhaq
1 Replies
9. UNIX for Advanced & Expert Users
I am using the ZLIB_VERSION "1.2.3" . The memory requirement for Zlib/GZIP compression is stated as
/* The memory requirements for deflate are (in bytes):
(1 << (windowBits+2)) + (1 << (memLevel+9))
that is: 128K for windowBits=15 + 128K for memLevel = 8 (default values)
... (0 Replies)
Discussion started by: Parmod Garg
0 Replies
10. Programming
how can i monitor usages of CPU, Memory, Hard disk etc. under SUN Solaries
through a c program or java program
i want to store that data into database so i can show it graphically
thanks in advance (2 Replies)
Discussion started by: Gajanad Bihani
2 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