service_notification_commands

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Brunker, Jay
> Sent: Thursday, March 16, 2006 4:14 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] service_notification_commands
> 
> 
> 
> YANNQ ( Yet Another Nagios Newbie Question )
> 
> I'm correcting errors from my pre flight test and I am working on the
> service_notification_commands errors in 'contacts.cfg'
> 
> right now.
> 
> Are there any existing/pre built commands for such things are
'notify-by-
> email' or 'notify-by-pager' ?

Yes, they're included in the sample config files that you can optionally
install at compile time (make install-config). If you don't want to
install the sample configs (and they're good examples), you can find the
command definitions for these in
/path/to/src/nagios-2.0/sample-config/template-object/miscommands.cfg
(_not_ miscommands.cfg.in).

For hosts -
host-notify-by-email
host-notify-by-epager

For services -
notify-by-email
notify-by-epager
 
> OK, so if I need to build my own commands do those definitions go in
the
> 'contacts.cfg' ?
> ... or would those commands go in a 'commands.cfg' file ?

Generally they'd go in commands.cfg but in reality they can go in any
file you define as a cfg_file in nagios.cfg. It's up to you whether you
have a single, few or hundreds of cfg_files and how they're organized.

--
Marc



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
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