have you looked at DNX? I think it's the way to solve your problem. <div class="gmail_quote">On Tue, Jun 24, 2008 at 2:06 PM, Brian A. Seklecki <<a href="mailto:lavalamp@spiritual-machines.org">lavalamp@spiritual-machines.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">All: In the el-generic Master w/NSCA distributed configuration, has anyone developed a hack to have cmd.cgi pass a SCHEDULE_FORCED_HOST_CHECK or SCHEDULE_FORCED_SVC_CHECK received by the master instance, onto a designated slave? We have a config where our slaves are in remote facilities and the master can only rely on passive checks -- attempting to force an active check on the master is a no-go due to network ACLs and other limitations. It would be nice to only need one web interface on the master NSCA receiver. The problem is two-fold (and this gets into the whole inter-component architecture discussion) -- 1) Even with a cmd.cgi hack, there is no native meta-data within Nagios to associate a host/service with a designated slave. 2) There is no clean communications channel other than a shell script wrapper (ssh and keys, etc. that stdout's to the slave's nagios.cmd -- this could get ugly...fast) ~BAS ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. <a href="http://sourceforge.net/services/buy/index.php" target="_blank">http://sourceforge.net/services/buy/index.php</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>