Re: gconfd process eating CPU

<quote who="Brian Cameron">

> Unfortunately the problem does not seem to happen in a predicatable
> fashion so we don't know how to recreate the problem.  We do have
> monitoring software that points us towards processes once they've entered
> an unhealthy state and are sucking up 100% of the CPU.  So I can easily
> find many processes that are sick.
> 
> Aside from running strace or truss for every single user on the system and
> waiting for one to hang, is there an easier way?

Once you've found a spinning process, strace -p it. You don't have to strace
it from the start.

- Jeff

-- 
linux.conf.au 2005: Canberra, Australia                http://linux.conf.au/
 
   "I came for the quality, but I stayed for the freedom." - Sean Neakums