its always advisable to take the
or even with longer interval..as it gives a stable o/p for the last 4 intervals..The 1st interrogation denotes the average value for the m/c since it was rebooted..However the subsequent values show the current status...Hence alwyas try to notice o/p from a longer interval and for a relatively larger number of interrogations
Last edited by DukeNuke2; 07-27-2011 at 12:57 PM..
Hello all,
I have the folowing question: I have an E450 with Solaris 2.6 running in a cluster environment. The primary node runs Oracle 8.1.5. My problem is: every time the Oracle Database is shutdown, the "w"colum in vmstat command jumps to "30". In man page for vmstat command, the "w" colum... (1 Reply)
Hello. I'm a complete newbie to C programming. I have a C program that wasn't written by me where I need to write some wrappers around it to automate and make it easier for a client to use. The problem is that the program accepts standard input to control the program... I'm hoping to find a simple... (6 Replies)
if I have a two CPU
when I run vmstat command to check cpu usage
it only one row
procs memory page faults cpu
r b w avm free re at pi po fr de sr in sy cs us sy id
1 ... (1 Reply)
Hi, guys, I'm a new comer here. I'm studying Unix Shell and I met a problem confusing me a lot. Here it is :
script 1:
#!/bin/sh
# scriptname : do_increment
increment(){
sum=`expr $1 + 1`
return $sum # Return the value of sum to the script.
}
echo -n "The sum is "
increment $1 # Call... (2 Replies)
RHEL 5.4
Our Linux machine seemed to be running slow. So, I ran the top and vmstat commands.
Question1.
I can see the process 11517 consuming 100% CPU . But that just means that this process totally utilizes one of the cores in a mult-core CPU. Right ? This machine apparently has two... (2 Replies)
Cheers!
In /etc/syslog.conf, if an error type is not specified, is it logged anywhere (most preferable is it logged to /var/log/messages) or not?
To be more precise I am interested in error and critical level messages. At default these errors are not specified in syslog.conf, and I need to... (6 Replies)
On our prod system we found sometime runqueue goes back to 0 as below.
Whereas on test server even with very very less work the r-queue never dropped to 0. Under what conditions r-queue drops to 0? Does it mean something unusual?
EG:
kthr memory page faults ... (1 Reply)
Discussion started by: aixusrsys
1 Replies
LEARN ABOUT SUSE
mrtg-logfile
MRTG-LOGFILE(1) mrtg MRTG-LOGFILE(1)NAME
mrtg-logfile - description of the mrtg-2 logfile format
SYNOPSIS
This document provides a description of the contents of the mrtg-2 logfile.
OVERVIEW
The logfile consists of two main sections.
The first Line
It stores the traffic counters from the most recent run of mrtg.
The rest of the File
Stores past traffic rate averates and maxima at increassing intervals.
The first number on each line is a unix time stamp. It represents the number of seconds since 1970.
DETAILS
The first Line
The first line has 3 numbers which are:
A (1st column)
A timestamp of when MRTG last ran for this interface. The timestamp is the number of non-skip seconds passed since the standard UNIX
"epoch" of midnight on 1st of January 1970 GMT.
B (2nd column)
The "incoming bytes counter" value.
C (3rd column)
The "outgoing bytes counter" value.
The rest of the File
The second and remaining lines of the file contains 5 numbers which are:
A (1st column)
The Unix timestamp for the point in time the data on this line is relevant. Note that the interval between timestamps increases as you
prograss through the file. At first it is 5 minutes and at the end it is one day between two lines.
This timestamp may be converted in OpenOffice Calc or MS Excel by using the following formula
=(x+y)/86400+DATE(1970;1;1)
(instead of ";" it may be that you have to use "," this depends on the context and your locale settings)
you can also ask perl to help by typing
perl -e 'print scalar localtime(x),"
"'
x is the unix timestamp and y is the offset in seconds from UTC. (Perl knows y).
B (2nd column)
The average incoming transfer rate in bytes per second. This is valid for the time between the A value of the current line and the A
value of the previous line.
C (3rd column)
The average outgoing transfer rate in bytes per second since the previous measurement.
D (4th column)
The maximum incoming transfer rate in bytes per second for the current interval. This is calculated from all the updates which have
occured in the current interval. If the current interval is 1 hour, and updates have occured every 5 minutes, it will be the biggest 5
minute transfer rate seen during the hour.
E (5th column)
The maximum outgoing transfer rate in bytes per second for the current interval.
AUTHOR
Butch Kemper <kemper@bihs.net> and Tobias Oetiker <tobi@oetiker.ch>
2.16.2 2008-05-16 MRTG-LOGFILE(1)