Estagiario TI Compal wrote:
> Hello, for security reasons i have obfuscated the hostnames and ip
> adresss of the configuration files. I will not send the configuration
> files into the mailing list because internal security policy.
>
ip addresses doesn't matter, but if you've changed all the host_name
variables it will be difficult to reproduce the errors you're seeing.
> The configuration files are structured into networks, each network
> has sites that are other networks, i.e., organization pt.xpto in the
> directory "networks" have the all sites with the hosts and services
> running in that site.
>
> For this especific case tou can find the file with the wilcard
> problem in: nagios/networks/networks/pt.xpto/contacts/hmgr.cfg
>
> as yo can see the file hmgr.cfg is a general contact of organization
> pt.xpto.
>
> if the contact was from a especific site the contact will be at,
> i.e.,
> nagios/networks/networks/pt.xpto/networks/site1/contacts/hmgr.cfg
>
> Are you a nagios-core developer?
>
Nopes. Ethan holds CVS access tight, so he's the only one. I've set up a
git repository though (soon available from ghost.op5.se) where I keep
patches we (OP5) use, along with some experimental stuff I intend to
submit for the 3.0 branch. When I've tested the patches there I'll send
them to Ethan and hopefully he'll apply them to the master repo. git is
nice for this, as it has tools to automatically send commits as patch
emails, and the distributed repository model works much better for open
source development than cvs, which requires trusting everybody in the
core team with the entire core.
> When can i have some feedback please?
>
I'm not sure. I'll see if I can start looking at this tonight, but I'm
fairly busy with other projects as well so I can't promise anything.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]