Using ! in check_command

[jeff vier]

On Tue, 2004-06-15 at 18:32 -0400, Chris Hammond wrote:
> Very popular answer isn't it Jeff. :)

It's often correct, so, yes :)

Unfamiliarity with escaping reserved characters seems to be a problem
with non-Unix folk coming into the field.  I think it's a lot better
than the Windoze answer (which would be "don't use that character").

> On Tue, 2004-06-15 at 18:16, jeff vier wrote:
> > On Tue, 2004-06-15 at 15:24 -0500, Michael Eck wrote:
> > > Greetings,
> > > Is there a trick than anybody knows of the use a ! as a character in a 
> > > password for a check_command?
> > > The obvious problem is that it's also the field delimiter.
> > 
> > Have you tried escaping it?
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> > ::: Messages without supporting info will risk being sent to /dev/null



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null