On Thu, Jun 10, 2010 at 21:55, Kevin Keane <subscript...@kkeane.com> wrote:
> Config file maintenance can be improved to some extent with careful design
> of the config files, as well as tools. It is an issue that I am running into
> with a relatively small installation with 80+ hosts and 400+ services. My
> installation is highly heterogeneous and very dynamic, which makes config
> file maintenance a nightmare. Having to restart Nagios after a configuration
> change doesn’t help either. On the other hand, a network with 2000 identical
> machines is probably going to be much easier to manage than my type of
> network.
>
Nitpicking or helpful tip, you decide: Nagios reloads config changes on
SIGHUP, you don't have to do a restart. A full restart can take a while on a
sufficiently sized installation so having to do one for every change would
indeed be a PITA, but I've never seen a reload take more than a few seconds.
Cheers
Martin
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Nagios-users mailing list
Nagios-users@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
