Very basic notifications question

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Matthew Macdonald-Wallace
> Sent: Tuesday, March 18, 2008 12:17 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Very basic notifications question
> 
> On Tue, 18 Mar 2008 11:52:24 -0500
> "Marc Powell" <marc at ena.com> wrote:
> 
> > There's nothing special about what you're looking for. Very typical
> > nagios config...
> Marc,
> 
> Thanks for the response, at the moment we have .cfg files for all of
> our hosts in the format <hostname>.cfg and in these files we have a
> list of all the services.

hostname.cfg contains service{} definitions? Just modify the parameters
in each service definition then.
 
> If I create a file that has the notification settings for each service
> (they are called the same for each server), will nagios understand
> that, or do we need to seriously look at how we have implemented
nagios
> and re-write the files so that the hostname.cfg's only contain the
> hostname/IP and the services are listed elsewhere?

I can't really answer this effectively. There shouldn't be a file just
for notification settings for services... I don't really understand how
you've got things set up. The end result is that you want to modify the
parameters for the service{} definitions (or template they use) for the
services you want to change. Maybe if you provided specific details,
with examples, that'll help clarify.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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