Any way to get Nagios to ignore errors on startup?

[Scott Greenman]

I have a set of services that I monitor in two different locations using two
different Nagios servers.  The services define the host-groups they apply to in
their definitions.  Some of these host-groups exist in one location but not the
other.  If I try to start Nagios in the location *without* a particular host
group, I get an error:
 
Error: Could not find any hostgroup matching 'all-bogus'
Error: Could not expand hostgroups and/or hosts specified in service
 
Is there any way to make Nagios consider this a warning instead of an error, so
it could still run.  I'd prefer to not have to keep two sets of service
definitions around, one for each site, that differ only in that one lists some
host-groups that the other does not.
 
Thanks
 
Scott Greenman

----------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070116/091d3e9b/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- 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