Re: Config reread issues...

[Rory Toma]

Um, yeah, that's exactly what we meant. Wasn't it clear? 8-)

On Thu, 2003-01-30 at 16:32, Jan-Henrik Haukeland wrote:
> Rory Toma <address@hidden> writes:
> 
> > I would not be opposed to having monit only reload if sent a signal.
> > 
> > On Thu, 2003-01-30 at 14:55, Christian Hopp wrote:
> > >
> > > If you edit you config... you have no other chance!  Monit uses it right
> > > away!  And it doesnT wait you any command.  I would prefer to give monit a
> > > sign to reload... like SIGHUP (as already mentioned on the list).
> 
> Ehm, guys I implemented a config reload on SIGHUP and it's in the
> lates official 3.1 release. Maybe you didn't notice since I put it in
> the evening before the release ;)
> 
> Ps. If you change your monitrc file it's not loaded right away but on
> the next poll cycle, I know you know this, but just to clarify. Since
> the code is already in place and working for reloading in SIGHUP I'm
> not opposed to removing the "check for monitrc changes in each poll
> cycle" and just use reload on SIGHUP (it only requires an extra flag
> test).
-- 
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