How to use check_esx3 Blacklists

[Jim Avery]

On 29 June 2011 09:52, Mies, Christian <Christian.Mies at it-novum.com> wrote:
>
> Hi List,
>
> I try to monitor my Datastores by check_esx3 by Datacenter. I want to exclude each local_* Datastore. The following command is not working ..
>
>
>
> ./check_esx3.pl -D 10.1.82.34 -u <user> -p <pw> -l vmfs -x local_*
>
>
>
> What am I doing wrong?


At first glance, my guess is your shell is interpreting the "*" as a
file wildcard.  You probably need to put quotes around it like so:

./check_esx3.pl -D 10.1.82.34 -u <user> -p <pw> -l vmfs -x "local_*"

Alternatively, backslash-escape it like so:

./check_esx3.pl -D 10.1.82.34 -u <user> -p <pw> -l vmfs -x local_\*

It's not clear whether check_esx3.pl supports wildcard notation
though.  Without actually looking at the code I would guess not, or if
it does it might use regular expressions in which case the syntax
would be:

./check_esx3.pl -D 10.1.82.34 -u <user> -p <pw> -l vmfs -x "local_.*"

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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