*BSD News Article 21683


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!headwall.Stanford.EDU!nntp.Stanford.EDU!leland.Stanford.EDU!yergeau
From: yergeau@leland.Stanford.EDU (Dan Yergeau)
Subject: Re: 386bsd-0.1 + pk-0.2.4: top-3.2 problems
Message-ID: <1993Sep30.221833.6777@leland.Stanford.EDU>
Sender: news@leland.Stanford.EDU (Mr News)
Organization: DSG, Stanford University, CA 94305, USA
References:  <CE2szt.q5@luva.stgt.sub.org>
Date: Thu, 30 Sep 93 22:18:33 GMT
Lines: 26

In article <CE2szt.q5@luva.stgt.sub.org>, migieger@luva.stgt.sub.org (Michael Giegerich) writes:
|> 
|> Hi,
|> 
|> compiling top-3.2 (w/o any error message) was straight
|> forward, but...
|> 
|> after invoking top all seems ok, for 5 seconds; then after the
|> first screen refreh all but the header "vanishes" (no processes
|> are displayed any more).

Try uncommenting the 

/* #define PATCHED_KVM		/* YOU PROBABLY DON'T NEED THIS DEFINED! */
				/* define this if you have a kvm.c */
				/* that has been patched not to freshly */
				/* alloc an array of procs each time */
				/* kvm_getprocs is called, but to do a */
				/* realloc when the no. of processes inc. */

in m_386bsd.c.

--
Dan Yergeau                         You are in a twisty little passage
yergeau@gloworm.Stanford.EDU        of standards, all conflicting.
#include <std.disclaimer>