nsclient memory check?

[Anthony Montibello]

When I was making NC_Net I struggled briefly with this issue, and
found that it is using:
Performance counter category Memory:
and counters: Commit Limit and Committed Bytes

I hope this helps with your problem.
Maybe you can try nsclient++

Good Luck
TOny

On 7/4/05, Steve Shipway <s.shipway at auckland.ac.nz> wrote:
> Can anyone confirm for me just exactly what is being checked by the NSClient
> 'MEMUSE' check?  (Currently using pNSclient v2.0.1)
> 
> I always assumed that it represented the Total and Available virtual memory,
> which was then used to calculate percentage.  However, this no longer seems
> to match observations.
> 
> As far as I can tell it seems to be returning the page file available and
> used space, which is a bit odd.  It doesn't seem to match either physical or
> virtual counts as reported by perfmon or sysinfo...  sadly, I do not have
> the source code or documentation for it, and there seem to be no more web
> sites supporting this software since ready2run dropped it and ran :).
> Upgrading to NCNet is not an option as we cannot install .Net on our
> servers.
> 
> Can anyone enlighten me?
> 
> Steve
> 
> ---
> Steve Shipway: ITSS, University of Auckland
> Email: s.shipway at auckland.ac.nz  Web: http://www.steveshipway.org/
> ** We can only discover new oceans when we have the **
> ** courage to lose sight of the shore.              **
> 
> 
>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
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