On Wed, Sep 05, 2001 at 11:10:06AM -0500, Kris Kelley wrote:
> I 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.
>
> Charles Cazabon replied:
> >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, this is getting annoying. I shut down svscan, using its init script.
svscan does not come with an init script!
> Then, I started one supervise process to oversee querydaemon (my program).
> No CPU overload. Next, I killed that supervise process, restarted svscan
> with its init script, and then restarted querydaemon using its init script.
> Again, no CPU overload, and everything was working fine. But then I
> rebooted the machine, allowing svscan and the supervised programs to start
> up as they normally would at system boot. querydaemon is once again maxing
> out the CPU! I repeated this procedure several times to be sure I wasn't
> making it all up.
>
I bet your querydaemon relies on it's process state, see
http://cr.yp.to/daemontools/faq/create.html#why . That is a reason why
daemontools has no init script. I would suggest you stop using the init
script, follow author's installation instruction, check what your daemon
relies on that is not in svscan's process state and fix the daemon or the
startup of the daemon.
Guessing: does your daemon rely on environment variables you set in
.profile or similar and runs wild if they are missing?
Regards, Gerrit.
--
[EMAIL PROTECTED]
innominate AG
tel: +49.30.308806-0 fax: -77 http://www.innominate.com
