Re: gconfd process eating CPU

[Joerg Barfurth <jub sun com>]

Ghee Seng Teo wrote:
> > > Aside from running strace or truss for every single user on the 
> > > system and waiting for one to hang, is there an easier way?  Is
> > > there any way to tell what file descriptor is causing the problem
> > > once the process has hung?

> > Yes, run strace on the sick process and it will at least let us 
> > know if the problem is what I suggested.

>    The equivalent of strace on Solaris is called truss. In fact, you can
> get pfiles to see the list of file descriptors for the run away process.
> However, getting a strace output after it hung would give you very
> little history.

If it not just hanging but looping and "eating CPU" (see subject), then 
a strace/truss may yield usable data.

Ciao, Jörg

--
Joerg Barfurth              Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer                         joerg barfurth sun com
OpenOffice.org Configuration          http://util.openoffice.org