RE: Question

[Rory Toma]

OK, I'll check it in.

check_process() has been changed to pass a flag to tell me whether to
toggle do_validate or not. We don't want validate() changing the values
of do_validate, that should only be done by running monit or from the
web interface.

The problem I'm running into is that I turn do_validate to FALSE from
monit, but it gets set back in p.y to TRUE, so it doesn't stay set.

In any case, I've gotten the code to a point where we don't start
anything w/o stopping it first. Once I get the above problem fixed, I
can probably even eliminate that, as well, so we would only start things
once ever.

I'm going to check in the code with do_validate initialized to 4, as it
makes debugging easier.

On Mon, 2002-11-25 at 15:18, Jan-Henrik Haukeland wrote:
> > After digging some more, here is my quandry...
> >
> > I can't figure out how do_validate is getting reset to TRUE.
> >
> > It is, however, passing through the code in p.y that sets do_validate to
> > TRUE.
> >
> > I can check in what I have, as all the order stuff seems to work ok. I
> > just can't get my changes to the do_validate flag to stick and I'm
> > stuck.
> 
> Not bad, a haiku, sort off :)
> 
> Check it in and I can try to give it a stab. Could you also provide a short
> design description so I'll know where to start. For instance why it is
> important to set the do_validate flag...
> 
> Cheers!
> 
> Jan-Henrik
> 
> 
> 
> _______________________________________________
> monit-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/monit-dev
-- 
Rory Toma               address@hidden
VP of Run Level 5       http://www.trs80.net
Digeo Digital           http://www.digeo.com

signature.asc
Description: This is a digitally signed message part