Re: Question

[Martin Pala]

There is the only one cause to reload monit's configuration without 
monit restart - changed timestamp of monitrc. If you'll change 
configuration and immediately load it, you can send monit signal to 
wakeup. It then looks on timestamp and parses monitrc again. There isn't 
any other way (to force configuration reload) now. In the past i made 
patch for monit implementing SIGHUP, that caused forced configuration 
reload, but it was rejected (it isn't realy needed).

Martin

Rory Toma wrote:

> What causes (other than a new config file) a re-load of config?
>
>
> On Thu, 2002-11-21 at 03:40, Martin Pala wrote:
>  
>
> > address@hidden wrote:
> >
> >    
> >
> > > I also pulled out the ability for control.c to send stop/start via http.
> > > It stopped making sense to me to do it that way. One way, we called a
> > > function that then called spawn, the other way we sent data to the http
> > > port, which then calls spawn. By removing this in control.c, evrything
> > > runs through check_process() now, including cervlet and validate, and most
> > > of the logic can be put there, instead of replicated in 2 or 3 places.
> > >
> > >      
> > Sounds logical :)
> >
> >
> >
> > _______________________________________________
> > monit-dev mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/monit-dev
> >