Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!sundc!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: Access to user process info.
Message-ID: <413@hadron.UUCP>
Date: Sat, 3-Jan-87 19:38:52 EST
Article-I.D.: hadron.413
Posted: Sat Jan  3 19:38:52 1987
Date-Received: Sat, 3-Jan-87 23:37:02 EST
References: <1327@brl-adm.ARPA> <165@hqda-ai.UUCP> <263@spectrix.UUCP> <99@osupyr.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 14
Summary: Some of how.
Xref: mnetor comp.unix.wizards:486 comp.unix.questions:512

I can't give you off the top of my head any tricks to make sure
that all the data you get is consistent.  However,

First you read the elements of the proc table.  There are NPROC
of them: this is found in int nproc in /vmunix or /dev/kmem.  The
proc structures tell where in memory or page space one can find
the user memory, including the _u structure; and the _u structure
tells which tty the process is attached to.  You get the addresses
out of /vmunix using nlist(), and then read them from /dev/kmem.
Or from /dev/proc, if you are lucky enough to have it ...
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}
			jsdy@hadron.COM (not yet domainised)