Nagios Support Forum

--Apple-Mail-176--1066755165
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii

Hello all,

On nagios-users, someone reported that a custom variable did not work =
when used as a macro (substitution did not occur). See the thread at

http://thread.gmane.org/gmane.network.n ... us=3D65324

Short story - The documentation states that custom macro names are case =
insensitive when in fact, they are case-sensitive in that they are =
converted to all upper case and must be referenced as such when used. =
This is implied by the examples but unclear due to the previous case =
insensitive statement. The one line change attached updates that to =
indicate conversion to uppercase.

--
Marc

p.s. Is anyone actually using the tracker (besides Ton?) I'd submit it =
there but one I added in July hasn't been touched.


--Apple-Mail-176--1066755165
Content-Disposition: attachment;
filename=customobjectsdoc.patch
Content-Type: application/octet-stream;
name="customobjectsdoc.patch"
Content-Transfer-Encoding: 7bit

--- html/docs/customobjectvars.html.orig 2009-11-18 09:38:37.000000000 -0600
+++ html/docs/customobjectvars.html 2009-11-18 09:40:25.000000000 -0600
@@ -98,7 +98,7 @@

Custom variable names must begin with an underscore (_) to prevent name collision with standard variables

-Custom variable names are case-insensitive
+Custom variable names are converted to all uppercase before use.

Custom variables are inherited from object templates like normal variables


--Apple-Mail-176--1066755165--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]