Age | Commit message (Collapse) | Author |
|
|
|
Debian and ubuntu have their resource.cfg file placed in /etc/nagios3/
and when it's absent it can cause issues with the package (because the
package is badly done).
|
|
|
|
That purging resources work correctly, the config files must be at
the location that the nagios providers have internally, which is
at /etc/nagios/<name>.cfg
To ease the config file we used the cfg_dir option so far, which we
can't anymore and hence this change requires adoption of your site
modules. But auto-purging resources will then finally work.
|
|
|
|
|
|
|
|
|
|
notify-(host|service)-by-email commands
|
|
|
|
Debian nagios.cfg file without this enabled, the plugins which are
installed by the nagios-plugins and nagios-plugins-basic packages will
not be enabled, causing undefined service check command errors in the
nagios pre-flight check. Because the nagios-plugins-basic package is
installed as a Depends for the nagios3 package, and nagios-plugins is
usually brought in, due to nagios3 having a Recommends on it, it a
good idea to have this plugin location enabled.
|
|
|
|
|
|
|
|
|
|
nagios::default resource; add support for lighttpd and headless httpd configurations; move common commands definitions into nagios::commands
|