RE: toggle feature

[Rory Toma]

Any objections to making this consistent, and having the flag set no
matter what the state of the process?

Also, I'm now in the process of more refactoring, now that I've
integrated the latest cvs into our own code base.

I also have another question. It would be probably useful if monitor.h
had comments to say which functions belonged to which files. However,
does doxygen or some other automated tool do this?

On Fri, 2002-09-27 at 16:21, Jan-Henrik Haukeland wrote:
> 
> You are right. Only if you stop/start the process from the web-interface is 
> the
> do_validate flag set.
> 
> Jan-Henrik
> 
> > I don't believe it will set the flag if the process isn't running (i.e
> > it's in a crash loop)
> >
> > On Fri, 2002-09-27 at 10:13, Jan-Henrik Haukeland wrote:
> > > > > Isn't it easier to, stop monit - upgrade - start monit :-) Anyway I do
> > > > > not think a this is a general useful feature.
> > > >
> > > > Not if it's running from init. Or, alternatively, one could change the
> > > > code so that if I run "monit stop foo" or "monit start foo" it
> > will change
> > > > the do_validate flag, regardless of if the process is running or not.
> > >
> > > It should do so already. E.g. if you do "monit stop foo" the
> > do_validate flag
> > > is set to FALSE in the monit daemon. That is, monit will not validate the
> > > process anymore, until you issue a "monit start foo"
> 
> 
> 
> --
> To unsubscribe:
> http://mail.freesoftware.fsf.org/mailman/listinfo/monit-general
> 
-- 
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