op5 check_esx plugin and net usage

[Peter Östlin]

On Tue, Mar 23, 2010 at 3:38 AM, Joseph L. Casale
<jcasale at activenetwerx.com> wrote:
> Seems this plugin wraps over ~100000K and returns an invalid result.
>
> Anyone seen this, is it fixable or a limit somewhere?

You mean when net usage exceed 100MB? Can you please post the command
line used and some example output?

Also, are you using the latest version? I don't see any changes
related to this recently but it is always a good idea to verify that
you are using the latest version. You get the latest source at:
http://www.op5.org/community/projects/op5-plugins


Regards
Peter Östlin
op5 AB

>
> Thanks,
> jlc
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> 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
>



-- 
op5 AB
Första Långgatan 19
SE-413 27 Göteborg
Mob: +46 733-70 90 31
Fax: +46 31-774 04 32
http://www.op5.com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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