Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re:  Getting a process listing...
Message-ID: <4e65b29e.1bc5b@pisa.ifs.umich.edu>
Date: 4 Dec 90 16:27:58 GMT
References: <9012041351.AA02186@richter.mit.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 17

In article <9012041351.AA02186@richter.mit.edu>, krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
  You can try using the Apollo-specific call proc2_$list. Documentation
  is available in the Aegis environment under "help calls proc2", or in
  the BSD environment under "man proc2".

It's nice that this interface has finally been released, but I noticed that
they haven't released any of the good stuff.  In particular, the info struct
given in the include file doesn't even have the Unix process IDs in it!  Rest
assured that there is all kinds of interesting stuff in there if you pass in
a big enough info struct.  A little detective work will reveal it to you.

Among other things:

vmstat stuff (number of page faults, disk io, etc)
Unix process IDs for self, parent, pgroup
process name
cpu usage