gainer@gainer.engr.sgi.com (Patrick Gainer) writes:
>In article <40aspa$f1l@oscar.cc.gatech.edu>,
>Carlos Ugarte <cau@cc.gatech.edu> wrote:
>>With onstat and onmonitor you can determine some information
>>about each thread, but I haven't figured out yet how to determine
>>what user process is tied to that thread. Can anyone give a
>But I thought processes weren't tied to threads, that threads could
>migrate around onto different engine processes.
Hmm... could be. If I recall correctly, the engine will
allocate threads to do some other tasks (ie recovery, if the
engine was brought down unexpectedly). Anyways, thanks to all
the folks who responded - the answer everyone gave was to use
'onstat -g ses'.
Carlos
--
Carlos A. Ugarte cau@cc.gatech.edu
Author of PageMage, a virtual desktop util for OS/2
http://www.cc.gatech.edu/people/home/cau/