usage of check_nrpe

[Anirudh Srinivasan]

I am using NRPE plugins to monitor the remote linux server.

Here is my question :

i use the following command on the NAGIOS MONITORING SERVER:

define command{
        command_name    check_nrpe_syslog
        command_line    $USER1$/check_nrpe -H $HOSTADDRESS$ -c check_log
}

My SERVICES.CFG looks like this:

define service{
use                             default-service
host_name                       test-server
service_description             linux syslog check
check_command                   check_nrpe_syslog
}
on the REMOTE LINUX SERVER:

There are two queries  one is "DEAD" and the other is "error" in my nrpe.cfg
file
 command[check_log]=/usr/lib/nagios/plugins/check_log -F /var/log/messages
-O /var/log/check_log.messages.error -q 'DEAD'
command[check_log]=/usr/lib/nagios/plugins/check_log -F /var/log/messages -O
/var/log/check_log.messages.error -q 'error'

Will this check both the queries  DEAD and error and show on the web
interface or will this check only the query "DEAD". I would like to check
both the query .

How do i work on this . Please help me .

Thanks in adv
-- 
Anirudh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090603/1a02ae2b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
-------------- next part --------------
_______________________________________________
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