check_nrpe on UNIX system

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Marco Borsani
> Sent: Friday, November 05, 2004 9:23 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] check_nrpe on UNIX system
> 
> Hi all.
> 
> 1)
> I don't find any documentation regarding check_load plugin .
> I supposed that -w and -c parameters would be % numbers, but I used
> numbers over 100 and I did not receive any error message.

'check_load --help' gives you --

-w, --warning=WLOAD1,WLOAD5,WLOAD15
   Exit with WARNING status if load average exceeds WLOADn
-c, --critical=CLOAD1,CLOAD5,CLOAD15
   Exit with CRITICAL status if load average exceed CLOADn

Using -w 2,2,2 -c 5,5,5 would issue a warning if load is greater than 2
for any interval and critical if it exceeds 5 for any interval. Load is
typically expected to be in the single digits or a fraction of 1. Using
a number like 100 is unlikely to produce any type of alert and if you do
have a machine that is exceeding 100 then you've got bigger issues ;)

> 2)
> I'd like to find plugins to control the memory usage and processes
(not
> the
> number but if it is up or not) via NRPE, like I am doing with check_nt
via
> NSClient.

check_procs can be used to determine if a specific process is running or
not. I am not aware of a plugin that can check the memory utilization of
a specific process but you could always write something.

--
Marc 




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&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