escaping arguments - check_snmp_int.pl

[Tom Wouters]

Hi everyone,

I've hit a bit of a snag while trying to monitor the status of some switch 
ports.
I'm using the check_snmp_int script from Patrick Proy,
when i run /usr/lib/nagios/plugins/check_snmp_int.pl -H 10.2.0.111 -C 
public -n "5.(?:6|7)" -2 -k -M -w500,500 -c700,700 -B 
from the commandline (non-root user) it returns an OK status.

yet when i configure the command, and pass the regexp as an argument it 
says it can't find the interface:
 
Status Information:ERROR : Unknown interface 5.(?:6 
Performance Data:7) 

Do i need to escape certain chars in the regexp, or does nagios run the 
command differently?


some more info:
command definition:   check_snmp_int_v2 : $USER1$/check_snmp_int.pl -H 
$HOSTADDRESS$ -C $ARG3$ -2 -n $ARG1$ -B$ARG4$ $ARG2$ 
service definition:   check_snmp_int_v2!"5.(?:6|7)"!-k -M -w500,500 
-c700,700!public!

the only difference i see is just the order in which the parameters are 
passed.

Thanks,

Tom
-- 
Tom Wouters
ICT
AZ Salvator - St.Ursula
Hasselt
0032 (0)11 289609
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090506/ecbaff9b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
-------------- next part --------------
_______________________________________________
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