*BSD News Article 33089


Return to BSD News archive

Xref: sserve comp.os.386bsd.misc:2756 comp.os.linux.misc:19967
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!Starbase.NeoSoft.COM!nobody
From: peter@Starbase.NeoSoft.COM (Peter da Silva)
Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc
Subject: Re: I hope this won't ignite a major flame war, but I've got to know!
Date: 23 Jul 1994 15:03:29 -0500
Organization: NeoSoft Internet Services   +1 713 684 5969
Lines: 16
Message-ID: <30rt2h$oka@Starbase.NeoSoft.COM>
References: <30drlt$7tc@news.u.washington.edu> <30ntmh$642@apollo.west.oic.com> <30pafh$hv4@Starbase.NeoSoft.COM> <30pl71$m1@newstand.syr.edu>
NNTP-Posting-Host: starbase.neosoft.com

In article <30pl71$m1@newstand.syr.edu>,
Shawn M Carey <smcarey@rodan.syr.edu> wrote:
>One thing I find annoying about SysV 'ps' is that you can't tell which
>process is using the most CPU,

ps -ef | sort -rn +0.40

Something I do a lot less often than 'ps -u' or 'ps -t'.

>and the RAM statistics are often misleading.

Same is true of any system that supports VM and shared libraries. The best you
can ever get from RAM statistics is a rough idea of what's been active
recently.

As for running out of procs, it's not at all hard if a daemon goes crazy.