best solution for configuration changes

[Tom Throckmorton]

On 01/03/2008 12:44 PM, Max wrote:
> On the Nagios server side you could have a cron job that updated the
> configs every N minutes or even a sub-version commit trigger that
> would run a "nagios -v /path/nagios.cfg" check on your configuration
> and either 1) restart Nagios if the configuration is good or 2) alert
> you if someone has broken the configs.

...or, do the pre-flight check using a pre-commit hook, so that the 
broken configs never make it to the nagios server in the first place ;-)

-tt

-- 
Tom Throckmorton
OIT - CSI
Duke University

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null