Sending passive host checks - OCHP vs Notification

[Tedman Eng]

I'm in the process of setting up a new distributed 2.0 installation.
The central server in this setup will perform no active checks, and no
freshness checks.
(sometimes parents have to just trust their children)

My question is this: 
Is it possible to use the host_notification_command instead of the
obsess_host_command to send hoststates to the central server?  My reasoning
is that notifications are only sent when the hoststate changes, versus OCHP
sending hoststate after every host check.  This may save some bandwidth,
especially when one of the child servers has many problem hosts to
check/re-check.

Though this is not the offically sanctioned method, are there any problems
with using this method?


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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