Nagios Support Forum

This is a multi-part message in MIME format.

------_=_NextPart_001_01C59BCF.FB71D60C
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In my situation, putting it in checkcommand creates 2 checkcommands
definitions and 2 service checkcommands. I was trying to create 2
service definitions and one checkcommand to simplify my configs.

=20

I've tried several times putting it in services.cfg, so no they do not
work there. Yes, putting it in checkcommands is a workaround, but not
desired.

=20

Thanks, I suppose. =20

=20

-Lori

-----Original Message-----
From: Andreas Ericsson [mailto:[email protected]]=20
Sent: Saturday, August 06, 2005 7:02 AM
To: Lori Adams
Cc: [email protected]
Subject: Re: [Nagios-devel] $USERn$ macros should be allowed in
services.cfg

=20

Lori Adams wrote:

> It would be nice if $USERn$ macros would be allowed in services.cfg.

>=20

=20

I thought they were.

=20

> =20

>=20

> Example:

> define service {

>=20

> check_command some_command!$USERn$

>=20

=20

You can do this anyway, by putting the USER-macro in the checkcommand=20

definition instead.

=20

> }

>=20

> =20

>=20

> I just had this come for the second time in my configuration. =20

>=20

> =20

>=20

> It's especially useful, because the $USER$ macros accept exclamation

> points, and don't cause issues with checkcommands. =20

>=20

> =20

>=20

> Thanks,

>=20

> =20

=20

You're welcome, I suppose.

=20

--=20

Andreas Ericsson [email protected]

OP5 AB www.op5.se

Lead Developer


------_=_NextPart_001_01C59BCF.FB71D60C
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
















In my situation, putting it in checkcommand creates 2 =
checkcommands
definitions and 2 service checkcommands.  I was trying to create 2 =
service
definitions and one checkcommand to simplify my =
configs.

 

I've tried several times putting it in =
services.cfg,
so no they do not work there.  Yes, putting it in checkcommands is =
a
workaround, but not desired.

 

Thanks, I suppose. 

<span =


...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: br