simple NRPE question

[Kerry Cox]

It's been awhile since I last used nrpe so it took me some time to get
back up to speed.
I have it installed and running and checking stats on a remote box.
Here is the feedback I am getting:

Running on box 10.52.38.242:

linux:/usr/local/nagios/libexec # ./check_nrpe -H 10.52.38.229 -c check_disk1
DISK OK [452754 kB (96%) free on /dev/hda1]
linux:/usr/local/nagios/libexec # ./check_nrpe -H 10.52.38.229 -c check_disk2
DISK OK [10149224 kB (51%) free on /dev/hda2]
linux:/usr/local/nagios/libexec # ./check_nrpe -H 10.52.38.229 -c check_disk3
DISK OK [6936164 kB (35%) free on /dev/hda3]
linux:/usr/local/nagios/libexec # ./check_nrpe -H 10.52.38.229 -c check_disk4
DISK OK [10149224 kB (51%) free on /dev/hda2]
linux:/usr/local/nagios/libexec # ./check_nrpe -H 10.52.38.229 -c check_disk5
DISK OK [3913416 kB (39%) free on /dev/hda5]

My question is: how do I now get this information to show up on the
master Nagios box or 10.52.38.242?

I am able to see the data from the local checks on .242, but the
remote check results coming from .229 are not appearing yet, i.e. disk
space, users, processes, etc.?
Is there something else I have to add to the *.cfg files on the master
Nagios machine?

I'd like to make a detailed HowTo for configuring NRPE sometime soon
since it seems like this is a frequently visited topic on the Nagios
mailing list. Just have to get my own configuration working correctly.
Thanks much.
KJ


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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