home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!apple!apple!motcsd!xhost92.csd.mot.com!ajv
- From: ajv@xhost92.csd.mot.com
- Newsgroups: comp.sys.hp
- Subject: Re: pstat () system call (and other goodies)
- Message-ID: <6986@motcsd.csd.mot.com>
- Date: 17 Aug 92 20:03:46 GMT
- References: <1992Aug14.083831.9639@Informatik.TU-Muenchen.DE> <n2@byu.edu>
- Sender: usenet@motcsd.csd.mot.com
- Lines: 28
-
- gritton@alaska.et.byu.edu (Jamie Gritton) writes:
-
- > I found this by accident too. After looking in sys/pstat.h, I
- >played around with it and found out how to make it work. It's really
- >quite useful, and much more elegant then poking around in /dev/kmem.
- >Plus non-root users can get the info too.
-
- Why, thank you! :-)
-
- This interface was first conceived by a fellow employee who was
- working on a customer complaint that ps was too slow. He defined
- the interface, and handed it off to my group. We worked on the
- interface to make it more generic and extensible, and then a
- fellow worker took a partial rewrite of ps I had done and filled
- out the rest of the missing functions.
-
- We considered the possibility of proposing it as a standard, but
- our standards "animals" told us that it probably wouldn't fly.
- The interface seems generic, but it is a generic to *UNIX*. Some
- people on these committees take exception to the concept of UNIX,
- and shoot down anything which leans in that direction. Things like
- "working set" or "virtual size" (assumes VM) push their buttons.
- There were some other fields which were problematic also. I'd have
- to take another look at someone's copy of pstat.h to name them.
-
- Andy Valencia
- ajv@csd.mot.com (for now)
- jtk@netcom.com (if it bounces)
-