Kris Kelley <[EMAIL PROTECTED]> wrote:
> >Perhaps supervise is continually restarting this program?
>
> No, the program is behaving itself, aside from taking up all CPU resources.
> It's the program itself that is getting 90+% CPU according to top, not the
> supervise process that started it.
Okay.
> > What if you run it several times over half a minute or so?
>
> Beg pardon? You mean doing "svc -u" and "svc -d" over and over?
No, I meant svstat, but you've covered that possibility by saying it
actually does stay up.
> Since I was using the init scripts to start and stop everything every time
> (except for when creating a single supervise process), I don't believe they
> are the problem. I'm open to suggestions on how to pursue debugging this.
> Is it possible to strace the entire start-up process?
It should be, but it will be some work. You could change however you're
starting svscan to use strace/truss to start it instead, with the option
to trace all children (strace allows you to trace each process to a
separate file, which might help here).
However, my next step would be to attach strace/truss to the querydaemon
when it is already running and sucking CPU. That should at least tell
you exactly what it's doing when it's spinning so hard. You might even
want to force it to coredump so you can run a debugger on it.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
