Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!bacchus!mellon From: mellon@zayante.pa.dec.com (Ted Lemon) Newsgroups: comp.unix.wizards Subject: Re: GNU os suggestions -- system data interfaces Message-ID: Date: 7 Jun 89 00:07:22 GMT References: <1344@marvin.Solbourne.COM> <3307@uokmax.UUCP> Sender: news@decwrl.dec.com Organization: Digital Equipment Corporation Lines: 18 In-reply-to: rmtodd@uokmax.UUCP's message of 5 Jun 89 22:09:37 GMT rmtodd@uokmax.UUCP (Richard Michael Todd) sez: >Getting kernel data values isn't too much of a problem (once you master >nlist and friends), though as UNIX is currently implemented it's extremely >ugly. The main problem I seem to run into is figuring out just what kernel >variable you need, what format it is in, and what it means once you've got >it. Well, that's part of it. The other part is that thrashing through the kernel's name list takes a lot of time on small machines. It is highly undesirable to have to do this on a regular basis. On a typical small machine, doing a ps is an unbelievably slow operation. It really shouldn't be. Usually, when you do a ps, it's because the system is misbehaving, often because it's overloaded. The last thing you need is some mondo bizarro program that thrashes through the kernel's name list and brings the CPU to its knees in the process. _MelloN_