Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2787 comp.os.linux.misc:20116 Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.moneng.mei.com!hookup!news.kei.com!travelers.mail.cornell.edu!newstand.syr.edu!rodan.syr.edu!smcarey From: smcarey@rodan.syr.edu (Shawn M Carey) 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: 24 Jul 1994 00:34:55 GMT Organization: Syracuse University, Syracuse, NY Lines: 15 Message-ID: <30scvf$12q@newstand.syr.edu> References: <30pafh$hv4@Starbase.NeoSoft.COM> <30pl71$m1@newstand.syr.edu> <30rt2h$oka@Starbase.NeoSoft.COM> NNTP-Posting-Host: rodan.syr.edu In article <30rt2h$oka@Starbase.NeoSoft.COM> peter@Starbase.NeoSoft.COM (Peter da Silva) writes: >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 Yes, this will show you which processes have used the most CPU over thier lifespans, but it doesn't show you which ones are burning the hottest at the moment you run ps. I understand this isn't that big a deal since top runs on both SysV and BSD, and it shows CPU burners (and RAM burners) better than ps does... -Shawn Carey