Re: [Nagios-devel] Re: [Nagios-users] $OUTPUT$ as shell script
Posted: Wed Sep 15, 2004 6:37 am
--DO5DiztRLs659m5i
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 15, 2004 at 08:52:16AM +0800, [email protected] wrote:
> On Tue, Sep 14, 2004 at 12:10:55PM -0700, Jason Martin wrote:
>=20
> > Try surrounding the output macro with single quotes, ex
> > '$OUTPUT$'. The shell won't evaluate special characters inside
> > the single-quotes.
>=20
> Has there be any thought toward making the macro values available
> via environment variables? This would be good for commands that want
> to be "intelligent" and have access to all the available information
> (for which writing the commands out and parsing all the arguments is a
> bit tedious), and also solves the problem of having to strip certain
> characters from command output and user comments for fear of
> inadvertently executing them.
Now that is an interesting idea; are there any limits on the
length of an environmental variable that would interfere? Does
it work the same way across platforms?
-Jason Martin
--=20
Rubber bands have snappy endings!
This message is PGP/MIME signed.
--DO5DiztRLs659m5i
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: --no-verbose
iD4DBQFBSFOwl2ODWuqVSBMRAkRmAJQIYt3rDxP93dzVSwvhT1RJCRCgAJ0Y0g9H
/tSaihPLruQXBRh//eMlKw==
=quO5
-----END PGP SIGNATURE-----
--DO5DiztRLs659m5i--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 15, 2004 at 08:52:16AM +0800, [email protected] wrote:
> On Tue, Sep 14, 2004 at 12:10:55PM -0700, Jason Martin wrote:
>=20
> > Try surrounding the output macro with single quotes, ex
> > '$OUTPUT$'. The shell won't evaluate special characters inside
> > the single-quotes.
>=20
> Has there be any thought toward making the macro values available
> via environment variables? This would be good for commands that want
> to be "intelligent" and have access to all the available information
> (for which writing the commands out and parsing all the arguments is a
> bit tedious), and also solves the problem of having to strip certain
> characters from command output and user comments for fear of
> inadvertently executing them.
Now that is an interesting idea; are there any limits on the
length of an environmental variable that would interfere? Does
it work the same way across platforms?
-Jason Martin
--=20
Rubber bands have snappy endings!
This message is PGP/MIME signed.
--DO5DiztRLs659m5i
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: --no-verbose
iD4DBQFBSFOwl2ODWuqVSBMRAkRmAJQIYt3rDxP93dzVSwvhT1RJCRCgAJ0Y0g9H
/tSaihPLruQXBRh//eMlKw==
=quO5
-----END PGP SIGNATURE-----
--DO5DiztRLs659m5i--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]