Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6597 ; Mon, 11 Jan 93 08:07:00 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!sdd.hp.com!elroy.jpl.nasa.gov!ufo!kaleb From: kaleb@jpl-devvax.jpl.nasa.gov (Kaleb Keithley) Subject: no avenrun in 386BSD Message-ID: <1993Jan13.204832.7321@jpl-devvax.jpl.nasa.gov> Organization: Jet Propulsion Laboratory (NASA) Date: Wed, 13 Jan 1993 20:48:32 GMT Lines: 22 I went searching through the 0.1 source to find an explanation of the "avenrun" variable. I was amused to find that that in 0.1 it's not there. Now, before everyone jumps down my throat and says, "yes it is", yes, it is indeed in the source, wrapped in a conditional compilation that will only be true on a vax or a tahoe. I double checked, 'nm /386bsd | grep avenrun' confirms that it didn't get declared. I might add that this is "vanilla" 0.1, with absolutely no patches, not even X11 (yet -- maybe I'll wait for 0.2!). Given that top and xload both use avenrun, I was wondering if one of the "58 patches" addresses this? On a separate but related question, now that I know what avenrun is, it strikes me that it's the wrong variable for xload, maybe cp_time would be better suited for what xload is trying to represent. -- Kaleb Keithley kaleb@jpl-devvax.jpl.nasa.gov