sar

sar

Post by reed wa » Wed, 21 Nov 1990 06:42:03



I get no idle using sar on a 550, on our 320 and 530 I get
reasonable values. It isn't under heavy use or anything.
Is this just, 'one of those things'?

austin> sar 1 10

AIX austin 1 3 000000011C00    11/19/90

16:28:58    %usr    %sys    %wio   %idle
16:29:00      47      53       0       0
16:29:01      51      49       0       0
16:29:02      49      51       0       0
16:29:04      52      48       0       0
16:29:05      51      49       0       0
16:29:07      43      57       0       0
16:29:09      32      68       0       0
16:29:10      50      50       0       0

.
.
.

-reed

 
 
 

sar

Post by Patrick Tor » Fri, 23 Nov 1990 01:02:38



>I get no idle using sar on a 550, on our 320 and 530 I get
>reasonable values. It isn't under heavy use or anything.
>Is this just, 'one of those things'?

I get about the same thing on my 520.
Under very little load.
what gives?
--

{emory,gatech}!nanovx!msa3b!torre

 
 
 

sar

Post by Geoff Colem » Sat, 24 Nov 1990 03:03:36



Quote:

> I get no idle using sar on a 550, on our 320 and 530 I get
> reasonable values. It isn't under heavy use or anything.
> Is this just, 'one of those things'?

        Do you have a tty  port enabled with no device on it? If
so turn that port off and you might see your system go down. Their "getty"
can chew up a lot of system time if it can't open a port.

Geoff Coleman
Unexsys Systems

 
 
 

sar

Post by reed wa » Wed, 28 Nov 1990 06:08:29



Quote:Coleman) writes:



|> >
|> > I get no idle using sar on a 550, on our 320 and 530 I get
|> > reasonable values. It isn't under heavy use or anything.
|> > Is this just, 'one of those things'?
|>
|>   Do you have a tty  port enabled with no device on it? If
|> so turn that port off and you might see your system go down. Their "getty"
|> can chew up a lot of system time if it can't open a port.
|>
|>
|> Geoff Coleman
|> Unexsys Systems

yow! that seemed to fix it..

-reed

 
 
 

1. sar problem: updates timestamp, but no sar data

Greetings folks,

I'm trying to figure out a problem that happened to me twice
yesterday.  I've done extensive searching and haven't found any
explanation for this behaviour.  So, here's the scenario:

I renamed and readdressed two servers, say Box1 and Box2.  They have
no real link to one another, save for the fact that they perform
similar functions.  Prior to the rename/readdress each of the machines
sar was running fine, reporting data at the expected intervals (sa1
was being run from cron at 5 min intervals).  Once the
rename/readdress took place, and the host was booted (just for my own
sanity), I found that while sar would run, and the timestamp on
/var/adm/sa/sa0x would be updated, when running sar -f
/var/adm/sa/sa0x by hand showed that the actual sar data from sa1
wasn't there.

The only solution I could come up with was to move the old datafile
aside and touch (and chmod/chown) an new one.  That solved the problem
in that the file was once again actually being written to, however,
that doesn't explain the strange behaviour when trying to write to the
original file.  Oh, another note, even when running sa1 by hand, the
file still didn't get written to (either running it as root or as
sys).

Any ideas?  The hosts are both SunFire V440's running Sol9, with
/usr/lib/sa/sa1 running at 5 min intervals from the sys crontab.

TIA,

Patrick

2. smbd (samba) and libwrap

3. "sar -f <file>" fails with "sar: malloc failed"

4. Posix Threads

5. Sar weird output question

6. Linux v1.0?

7. Strange Behaviour of sar and cpuhog

8. UPS

9. sar -d and how to determine which filesystem using the disk devices?

10. sar Question (probably a newbie question)

11. SAR reports-graphical representation?

12. corrupt sar files

13. sar -q vs. uptime