[Nagios-users] $OUTPUT$ as shell script parameter
Jason Martin
jhmartin at toger.us
Wed Sep 15 16:37:36 CEST 2004
On Wed, Sep 15, 2004 at 08:52:16AM +0800, nagios at mm.quex.org wrote:
> On Tue, Sep 14, 2004 at 12:10:55PM -0700, Jason Martin wrote:
>
> > Try surrounding the output macro with single quotes, ex
> > '$OUTPUT$'. The shell won't evaluate special characters inside
> > the single-quotes.
>
> 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
--
Rubber bands have snappy endings!
This message is PGP/MIME signed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 211 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20040915/dc686dfb/attachment.sig>
More information about the Developers
mailing list