Re-send: Notificaitons after the commit

[C. Bensend]

> Running nagios -v nagios.cfg haves Nagios verify the configuration, this
> is
> best practice because otherwise you risk a typo stopping your monitoring
> for
> the time it takes for you to correct the configuration :-)

...

> Tip: don't use restart when you just want Nagios to load new
> configuration.Your init script should handle reload instead, which will
> send
> a HUP signal to Nagios. This means that Nagios doesn't stop and start back
> up, it only re-reads the configuration files.
>
> So, for your specific problem, I think you'd be fine by simply using this
> instead:
>
> /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
> /etc/init.d/nagios reload

For exactly this reason, I have had two command aliases for years:

preflight (which does a -v against the configuration file to check the
           sanity of my Nagios configuration)

reload (which sends the Nagios process a SIGHUP)

I *always* do a preflight before the reload, just to be sure my
configuration is sane, no matter how minor a change I made.  It's
a good habit to be in.

Benny


-- 
"Show me on the doll where the marketing touched you."
                               -- "Mally" on Fazed.net



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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