*BSD News Article 25838


Return to BSD News archive

Newsgroups: comp.os.386bsd.apps
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!vixen.cso.uiuc.edu!newsrelay.iastate.edu!news.iastate.edu!ponderous.cc.iastate.edu!michaelv
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: Top - what is it and do I need it?
Message-ID: <michaelv.758254073@ponderous.cc.iastate.edu>
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames IA
References: <CJBFJz.3L1@usenet.ucs.indiana.edu> <1994Jan10.184623.16915@news.csuohio.edu>
Date: Tue, 11 Jan 1994 02:07:53 GMT
Lines: 38

In <1994Jan10.184623.16915@news.csuohio.edu> stever@csuohio.edu (Steve Ratliff) writes:

>Jim Pitts (pitts@mimosa.astro.indiana.edu) wrote:
>: In article <tmcCJAqoB.5L@netcom.com>, Tom Crockett <tmc@netcom.com> wrote:
>: >Occasionally I've seen references to what must be a system mgt.
>: >tool named 'top'.  archie -s top returns lots of getopts :) but 
>: >not top.  
>: 
>: 'top' is indeed a handy tool.  It gives you a real time breakdown on the
>: consumption and use of system resources.  It has given most of the *BSD
>: packages nothing but trouble getting it ported to their particular systems.
>: 
>: FreeBSD has 'top' on FreeBSD.cdrom.com in the pub/FreeBSD/packages directory.
>: It works very well for me.  There is both a binary and source package
>: there.
>:[sig deleted]
>	Be warned that the binary and source packages of top on
>FreeBSD.cdrom.com currently have a rather substantial memory leak.
>	Top will grow in size about 30-40k every time that a new process
>is started or exits.  So don't run top for extended periods of time,
>especially on a very busy system.  Top will hang your system after it
>gets to big.  On my not very busy system, it locks the system up after
>it has been running for about 24 hours.
>	I do not know if this applies to the NetBSD available source as well.
>There doesn't seem to be any problem if you only run top for several
>minutes at a time.  You can actually use top itself to watch the memory
>leak in action. :)

I grabbed the NetBSD top sources off alpha.gnu.ai.mit.edu and compiled
them with shared libraries, and had absolutely no problems whatsoever.
It ran all night long and was the same size the next day as when I
started it.  Top is indispensible for process load monitoring...

-- 
------------------------------------------------------------------------------
  Michael L. VanLoon                           Project Vincent Systems Staff
  michaelv@iastate.edu              Iowa State University Computation Center
------------------------------------------------------------------------------