monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Config reread issues...


From: Rory Toma
Subject: Re: Config reread issues...
Date: 30 Jan 2003 15:06:51 -0800

I would not be opposed to having monit only reload if sent a signal.

That being said, one should still make sure all of their services
(including monit) are running after making changes. It's a "best
practices" procedure.

Furthermore, if you are running a production system, you don't make
changes to it w/o testing somewhere else first, and still testing on the
production system.


On Thu, 2003-01-30 at 14:55, Christian Hopp wrote:
> On Thu, 30 Jan 2003 address@hidden wrote:
> 
> > More important is that we save state information when we reload. IMHO, if
> > you edit the config file and walk away without testing, you get what you
> > deserve.
> 
> 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).
> 
> Christian
-- 
Rory Toma               address@hidden
VP of Run Level 5       http://www.trs80.net
Digeo Digital           http://www.digeo.com

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]