Kris Kelley <[EMAIL PROTECTED]> wrote:
>
> Finally, yesterday as I was debugging the code for other issues, I started
> it up directly, without using svscan and supervise. No CPU overload! So,
> something about svscan/supervise is causing this program to go hog wild.
Perhaps supervise is continually restarting this program? What does
svstat say about your daemon when it's loading the CPU? What if you run
it several times over half a minute or so?
If it's not that, we need solid data, not speculation -- strace/truss
supervise and all it's children when running it. That will tell you
exactly what's going on.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
