Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!hellgate.utah.edu!cc.utah.edu!inel.gov!tws1!dob
Newsgroups: comp.unix.ultrix
Subject: Re: Retrieving per-process info on DS3100
Message-ID: <1990Jul14.175543.6715@inel.gov>
From: dob@tws1.Berkeley.EDU (David L. Brooks)
Date: Sat, 14 Jul 90 17:55:43 GMT
Reply-To: dob@tws1.Berkeley.EDU (David L. Brooks)
Sender: news@inel.gov
References: <2371.269db532@csc.anu.oz>
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Lines: 42

In article <2371.269db532@csc.anu.oz>, pjy100@csc.anu.oz writes:
|>Can anyone help ????
|>
|>I wish to obtain information about every process currently on the system
|>from the two data structures "proc" and "user" (see /usr/include/sys/proc.h
|>& /usr/include/sys/user.h) from within a "c" program, but I cannot find a 
|>system call that will retrieve this information from the system tables.
|>How can this be done? (pstat & ps must use the method I require). SunOS 
|>provides the calls "kvm_nextproc" & "kvm_getu" for doing what I need,
is there
|>an equivalent method for Ultrix 3.1 on a DS3100.
|>
|>Peter Young (systems prog. Mt Stromlo Observatory)

if you get some good info, would you consider posting, or sending me a
copy, please?

sorry fellow netters, i tried email to Mr. Young, but it was bounced.

also please excuse the *long* disclaimer.  it originates with our legal
department; at least they now let us post.
------------------------------------------------------------------------------
David L. Brooks
Idaho National Engineering Lab.  INTERNET: dob@INEL.GOV
POB 1625 M.S. 1206               Phone: (208) 526-0826
Idaho Falls, Id. 83415           FAX:   (208) 526-1419
------------------------------------------------------------------------------

Neither the United States Government nor the Idaho National
Engineering Laboratory nor any of their employees, makes any warranty,
expressed or implied, or assumes any legal liability or responsibility
for the accuracy, completeness, or usefulness of any information,
product, or process disclosed, or represents that its use would not
infringe privately owned rights.  Reference herein to any specific
commercial products, process, or service by trade name, trademark
manufacturer, or otherwise, does not necessarily constitute or imply
its endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions of authors expressed herein do not necessarily state or reflect
those of the United States Government nor the Idaho National Engineering
Laboratory, and shall not be used for advertising or product endorsement
purposes.