--nextPart5570914.oU2PjW0ia6
Content-Type: text/plain;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Tuesday 16 November 2004 20:53, Russell Jackson wrote:
> > Unless I'm just not seeing a way around this, I suggest that
> contact-groups be optional and allow a contact list be defined directly
> within host and service definitions. This would aid greatly in the
> maintainablity of the configuration files in this situation.
That could be nice-to-have (tm)...
BUT, in the meantime, you can auto-generate your configurations.
Just generate a contactgroup for each contact you have.
for every ${contact} insert this into an auto-generated file (and include i=
t=20
in nagios.cfg)
define contactgroup{
contactgroup_name ${contact}
members ${contact}
}
A nice bash script will set you up just fine...
I also recommend setting up a Makefile so you can just "make" and do all so=
rt=20
of auto-configs.
=2D-=20
Eldad Zack
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
--nextPart5570914.oU2PjW0ia6
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQBBmopfT+MN7JbqCpMRAugZAJ93kxchPZGmENTtotdq13/jndiyPQCfSBhS
zms7AvBc6sX8TxmC7WMM7E8=
=RRbG
-----END PGP SIGNATURE-----
--nextPart5570914.oU2PjW0ia6--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]