I have another box running 4.2 and it does not act the
same way, so I know there is something funky going on.
The telnet is not timing out...I have never had this
problem until I upgraded that box from 4.2 to 6.0...
There is a problem, I just don't know where and why.
--- Ward William E PHDN <[EMAIL PROTECTED]>
wrote:
> Um, this is standard Top behavior (no joke, every
> Unix box I've ever used!). It's compiling
> information,
> so what you are seeing is incomplete the first few
> seconds.
> If you lower your top threshold time down to the
> lowest
> number, you'll see it begins updating faster, so
> it's
> not missing that 99% as long...
>
> As for your REAL problem, I have no idea. Perhaps
> you're
> telnet is simply timing out due to lack of activity?
>
> Bill Ward
>
> -----Original Message-----
> From: Adv. Systems Design
> [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 14, 2000 11:55 AM
> To: [EMAIL PROTECTED]
> Cc: recipient.list.not.shown; @nswcphdn.navy.mil
> Subject: RE: weird entries under netstat
>
>
> The problem I am having is that my machine's
> processor
> is being cycled to death to the point where my
> telnet
> sessions become dead (top reveals that there is 0%
> idle, but 0.3% being used by system and 0.9% by user
>
> SO where is the rest of the 99%?! After a few
> seconds,
> top must background the process, because idle shoots
> up to 98%. Funny thing is, if I keep top running, my
> telnet connection never dies!
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
