Date: Tue, 5 Oct 1999 09:17:44 +0930 From: Greg Lehey <grog@lemis.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, thyerm@camtech.net.au, Ruslan Ermilov <ru@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: top with < 1 second delay (was: cvs commit: src/bin/sleep sleep.1 sleep.c) Message-ID: <19991005091744.W40186@freebie.lemis.com> In-Reply-To: <199910041635.JAA67276@apollo.backplane.com>; from Matthew Dillon on Mon, Oct 04, 1999 at 09:35:10AM -0700 References: <Pine.BSF.4.10.9910042220480.308-100000@localhost> <xzp670n88c7.fsf@flood.ping.uio.no> <199910041635.JAA67276@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 4 October 1999 at 9:35:10 -0700, Matthew Dillon wrote: > >>> I think it would be good to be able to run "top -s0.5" >> >> I don't think so. The output of top(1) (especially the CPU usage >> breakdown) becomes essentially useless if it is updated too often. >> >> As to adding funtionality to contributed software, we've already added >> functionality to top(1) (specifically, the -t flag and the 't' >> command). The maintainer never even bothered to reply when asked to >> review (and possibly integrate) the patches. >> >> Dag-Erling Smorgrav - des@flood.ping.uio.no > > top is kinda cpu-heavy. Occassionally I'll use 's0<return>' just to > watch the display go nuts, but beyond the laughs having a less then > one second update time isn't all that useful for top. I think that depends on what you're looking at. I could imagine that people look at other things besides the CPU time breakdown. I personally think that it would be a useful thing to have. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991005091744.W40186>