Re: gconfd process eating CPU



Mark McLoughlin wrote:

On Mon, 2004-12-20 at 15:43 -0600, Brian Cameron 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.

-Ghee

Cheers,
Mark.

_______________________________________________
gconf-list mailing list
gconf-list gnome org
http://mail.gnome.org/mailman/listinfo/gconf-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]