09-30-2015
Need help on sar command.
Hi,
how to find out actual utilization of memory using sar -r in Linux, I understand Linux keep entire memory in cache/buffers.
I would like to know how to find out actual usage of memory
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HI Experts,
Can anyone pls help me to understand this..
>sar
20:05:00 1 2 1 96
20:10:00 2 2 10 87
20:15:00 1 2 19 78
20:20:00 1 2 14 83
20:25:00 1 2 16 81
20:30:00 1 ... (1 Reply)
Discussion started by: shaan_dmp
1 Replies
2. UNIX for Dummies Questions & Answers
Hello all
i found out about the sar command but when looking in the man pages
there is no way to make sar working for ever .. only
with some kind of interval . like sar 2 30 .
my question is can i just run sar for ever ? (5 Replies)
Discussion started by: umen
5 Replies
3. Solaris
I am running Solaris 10 in a sparc environment.
I have the sys crontab setup to use sar to gather data and report it.
My sys crontab entry looks like this:
0,5,10,15,20,25,30,35,40,45,50,55 * * * 0-6 /usr/lib/sa/sa1
20,40 8-17 * * 1-5 /usr/lib/sa/sa1
5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e... (2 Replies)
Discussion started by: RobSand
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
# SAR -u 5 5 shows this
10:01:32 AM CPU %user %nice %system %iowait %idle
10:01:37 AM all 1.90 0.00 1.20 96.90 0.00
10:01:42 AM all 1.30 0.00 1.70 97.00 0.00
10:01:47 AM all 4.30 0.00 ... (1 Reply)
Discussion started by: egorig
1 Replies
5. Solaris
hi all:-
when i try to use sar command i get this error how can i fix it
bash-3.00# sar -A
sar: can't open /var/adm/sa/sa16
No such file or directory (5 Replies)
Discussion started by: sharkux
5 Replies
6. Shell Programming and Scripting
Hi all,
I am using linux box ...i dont find the manual entry of sar command through
man sar ...it is in unix not in linux although i have to check the cpu utilization and paging...any alternative of sar command..
Thanks
Vijay Sahu (1 Reply)
Discussion started by: vijays3
1 Replies
7. Shell Programming and Scripting
HI,
I have a problem with 'sar' command.
I am using the sar comman in script.when i execute the script manually using ./filenae, i am getting the desired output.
But when i put the script in cron job i am not getting the desired value.
Below is the script..
sar > $_LOCATION/sar.txt... (2 Replies)
Discussion started by: ahamed
2 Replies
8. Shell Programming and Scripting
I receive on a daily basis CPU measures on a UNIX Server (AIX 5.3 version, korn shell). These CPU measures are provided by Omnivision tool.
We could see that Omnivision daily stats are not always equal to NMON stats regarding CPU level.
On my side (I work in an IT Production Support Team, not... (0 Replies)
Discussion started by: Scofield38
0 Replies
9. Solaris
Hi Folks,
I am again here with a peculier problem.
Please see the code
root@celdws01: # sar -u -f /var/adm/sa/sa21
SunOS celdws01 5.9 Generic_118558-34 sun4u 12/21/2011
10:10:09 %usr %sys %wio %idle
10:10:09 unix restarts
Can anyone help me in... (9 Replies)
Discussion started by: vivek.goel.piet
9 Replies
10. UNIX for Dummies Questions & Answers
Hello,
Can you please explain me how to parameter and use "sar" command on Solaris (AIX) ?
When I use it on Solaris I got the following error :
bash-3.00# sar
sar: data file not in sar format
Thanks, (2 Replies)
Discussion started by: adilyos
2 Replies
RAW(8) System Manager's Manual RAW(8)
NAME
raw - bind a Linux raw character device
SYNOPSIS
raw /dev/raw/raw<N> <major> <minor>
raw /dev/raw/raw<N> /dev/<blockdev>
raw -q /dev/raw/raw<N>
raw -qa
DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device
driver does not even have to be accessible (it may be loaded on demand as a kernel module later).
raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N>
is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either
in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file.
The bindings already in existence can be queried with the -q option, with is used either with a raw device filename to query that one
device, or with the -a option to query all bound raw devices.
Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw
device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache
entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver
can support DMA, then no data copying at all is required to complete the I/O.
Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor-
rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the
data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices.
Use the /etc/sysconfig/rawdevices file to define the set of raw device mappings automatically created during the system startup sequence.
The format of the file is the same used in the command line with the exception that the "raw" command itself is omitted.
OPTIONS
-q Set query mode. raw will query an existing binding instead of setting a new one.
-a With -q , specifies that all bound raw devices should be queried.
-h provides a usage summary.
BUGS
The Linux dd (1) command does not currently align its buffers correctly, and so cannot be used on raw devices.
Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate,
but is regarded either a bug or a feature depending on who you ask!
AUTHOR
Stephen Tweedie (sct@redhat.com)
Version 0.1 Aug 1999 RAW(8)