Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!uhccux!virtue!comp.vuw.ac.nz!munnari.oz.au!lawley From: lawley@cs.mu.OZ.AU (michael lawley) Newsgroups: comp.sys.encore Subject: Re: process arguments Message-ID: Date: 3 Aug 90 02:30:50 GMT References: <9632@xenna.Xylogics.COM> Sender: news@cs.mu.oz.au Reply-To: lawley@murtoa.cs.mu.OZ.AU Distribution: comp Organization: Computer Science Dept., University of Melbourne, Australia. Lines: 26 In-reply-to: john@loverso.leom.ma.us's message of 2 Aug 90 21:07:10 GMT On 2 Aug 90 21:07:10 GMT, john@loverso.leom.ma.us (John Robert LoVerso) said: > I said: >> Under Umax 4.3 is there any way to get hold of a processes arguments for the >> purposes of a ps/sps like program? > From what I remember of UMAX (and the guts of it are unchanged, even in > UMAX4.3), it only keeps the first 12 bytes of the program name. The args > only exist out in process space, and I don't believe there is any way to > access them (at all). Umm, this doesn't make sense to me. If the args are in user space (which, of course, they must be) then you must be able to get at them from kernel mode as long as you know how. (See source for ps or sps [not Encore versions]). You are right, however, that the kernel only keeps track of 12 bytes of the command name - this is what the inq_stats() call gives you. > ../John mike - still looking for an answer -- _--_|\ michael lawley (lawley@cs.mu.OZ.AU). / \ The Unicycling Systems Programmer, \_.--.*/ Melbourne University, Computer Science v "You can't, really, dust for vomit."