Re: Question

[Martin Pala]

Yeah - i though about it too (it is monit's default behavior). It will 
be needed to implement it so, that it will keep state of p->do_validate 
after reload. Current behavior will forget its value after configuration 
reload. It is bad for cluster 'manual' mode too - monit's configuration 
reload is dangerous in such case. We maybe shouldn't release 3.1 before 
this problem will be solved.

Martin

address@hidden wrote:

> Yes, but if I run "monit stop foo" it should stay stopped, and the
> do_validate should not be set back to true when I re-load the
> configuration.
>
> So, the second question is:
>
> I didn't change my config file, so what triggers a config reload?
>
>
>  
>
> > Rory Toma wrote:
> >
> >    
> >
> > > Let me clarify. I thought that the code that set the defaults in p.y
> > > was only called on monit startup. What conditions could cause me to
> > > visit this code again?
> > >
> > > On Wed, 2002-11-20 at 19:13, Rory Toma wrote:
> > >
> > >
> > >      
> > >
> > > > So, I've about got the order dependency nailed. However, I've broken
> > > > validate in doing so. I've tracked my problem down to p.y. For some
> > > > reason, the way I'm doing it is invoking the code in p.y that sets the
> > > > default value of do_validate to TRUE, clobbering the FALSE value I've
> > > > put in.
> > > >
> > > > Hopefully I can figure a way around this tomorrow. If not, I'll post
> > > > the patch and see if one of you can.
> > > >
> > > >
> > > >        
> > Configuration reload
> >
> > Martin
> >
> >
> >
> >
> > _______________________________________________
> > monit-dev mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/monit-dev
> >    
>
>
>
>
>
> _______________________________________________
> monit-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/monit-dev
>