Am 16.01.2011 17:04, schrieb Grégory Starck: > but why like you to have the address be a duplicate/copy of the > host_name ?
Which make me think about another issue: There is even more redundant
data in each Host-configuration:
"host_name", "alias", "display_name" and "address".
IMHO only host_name and display_name are enough. The others should be
removed.
Rationale:
* One of address or hostname is enough. If an address should be used
to reach the host, put an address there. If a hostname should be
used (to be resolved via NNS), put the hostname there.
* According to
<http://www.shinken-monitoring.org/wiki/official/configuringshinken-objectdefinitions#host_definition>
I see no need "display_name". It looks like if can not be used by
macros, so simply drop it.
* Again according to the docs, "alias" is what I would call a
"display name". So "alias" should become "display_name".
BTW: Resolving the hostname on the arbiter may lead to double when using
realms and/or split-DNS.
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult mit Mitglied bei http://www.7-it.de
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
