[Nagiosplug-devel] RE: [Nagiosplug-help] check_memory weirdness

[Vincent Aniello]

The version of check_mem you provided worked correctly on my RedHat
Enterprise 2.1 servers.

Thanks.

V/


-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of Harper
Mann
Sent: Wednesday, September 15, 2004 12:09 AM
To: Vincent Aniello; nagiosplug-help at lists.sourceforge.net;
nagiosplug-devel at lists.sourceforge.net
Subject: RE: [Nagiosplug-help] check_memory weirdness

Here's a version that uses /proc/meminfo and takes cache into account.
I'd
be curious if it works correctly on your RHEL 2.1, if you want to try
it.

This is submitted for contrib as well...

Cheers,

- Harper

Harper Mann
Groundwork Open Source Solutions
510-599-2075 (cell)


-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of
Vincent
Aniello
Sent: Tuesday, September 14, 2004 4:05 PM
To: nagiosplug-help at lists.sourceforge.net
Subject: [Nagiosplug-help] check_memory weirdness


On one of my RedHat Enterprise 2.1 servers using the check_memory plug I
am seeing strange results:
 
Status: OK - 314% memory free.  

This can't be correct.  Has anyone seen this problem before?

This plug in seems to work correctly on other RedHat Enterprise 2.1
servers.

The check_memory plug in I am using is from the nagios-plugins-1.3.1
package.

V/




-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue.

::: Messages without supporting info will risk being sent to /dev/null