[icinga-checkins] icinga.org: icinga-doc/master: custom variables replaced only during runtime

git at icinga.org git at icinga.org
Wed Aug 24 15:28:27 CEST 2011


Module: icinga-doc
Branch: master
Commit: 70dc61455f6b858a4b0deee79da1aae977af97f2
URL:    https://git.icinga.org/?p=icinga-doc.git;a=commit;h=70dc61455f6b858a4b0deee79da1aae977af97f2

Author: Wolfgang <wnd at gmx.net>
Date:   Sun Aug 21 22:59:57 2011 +0200

custom variables replaced only during runtime

---

 de/customobjectvars.xml |   13 +++++++++++++
 en/customobjectvars.xml |   12 ++++++++++++
 2 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/de/customobjectvars.xml b/de/customobjectvars.xml
index 3b80095..6ecf938 100644
--- a/de/customobjectvars.xml
+++ b/de/customobjectvars.xml
@@ -49,6 +49,15 @@
     </listitem>
   </itemizedlist>
 
+  <anchor xml:id="customobjectvars-runtime"/>
+  <important><para>Maßgeschneiderte Variablen werden erst <emphasis>zur Laufzeit</emphasis> ersetzt, weder bei der Überprüfungsphase (icinga
+    -v icinga.cfg) noch während des &name-icinga;-Startprozesses, so dass das Platzieren in Host-Namen, Service-Beschreibungen oder
+    verschiedenen anderen Stellen der Objektdefinition während der Überprüfung zu einer Fehlermeldung ähnlich "<literal><object>
+    contains one or more illegal characters.</literal>" führt. Das Ändern der Direktive "illegal_object_name_chars" wird <emphasis>
+    nicht</emphasis> das Problem lösen.
+    </para>
+  </important>
+
   <para><emphasis role="bold">Beispiele</emphasis></para>
 
   <para>Hier ein Beispiel, wie maßgeschneiderte Variablen in verschiedenen Arten von Objektdefinitionen definiert werden
@@ -173,4 +182,8 @@
   <para>Maßgeschneiderte Objektvariablen werden genau wie Standard-Host-, Service- oder Kontaktvariablen <link
   linkend="objectinheritance">vererbt</link>.</para>
   <indexterm zone="customobjectvars"><primary>Maßgeschneiderte Objektvariablen</primary></indexterm>
+  <indexterm zone="customobjectvars-runtime">
+    <primary>Maßgeschneiderte Objektvariablen</primary>
+    <secondary>Ersetzung erst zur Laufzeit</secondary>
+  </indexterm>
 </section>
diff --git a/en/customobjectvars.xml b/en/customobjectvars.xml
index 4758d86..70fa969 100644
--- a/en/customobjectvars.xml
+++ b/en/customobjectvars.xml
@@ -48,6 +48,14 @@
     </listitem>
   </itemizedlist>
 
+  <anchor xml:id="customobjectvars-runtime" />
+  <important><para>Custom variables are replaced <emphasis>during runtime</emphasis>, neither during the verification phase (icinga -v
+    icinga.cfg) nor during the &name-icinga; start up process so placing them in host names, service descriptions, and several other places
+    of the object definition will lead to an error message during verification like "<literal><object> contains one or more
+    illegal characters.</literal>". Changing the directive "illegal_object_name_chars" will <emphasis>not</emphasis> solve this issue.
+    </para>
+  </important>
+
   <para><emphasis role="bold">Examples</emphasis></para>
 
   <para>Here's an example of how custom variables can be defined in different types of object definitions:</para>
@@ -175,4 +183,8 @@ define contact{
   <para>Custom object variables are <link linkend="objectinheritance">inherited</link> just like standard host, service, or
   contact variables.</para>
   <indexterm zone="custom_object_vars"><primary>Custom Object Variables</primary></indexterm>
+  <indexterm zone="customobjectvars-runtime">
+    <primary>Custom Object Variables</primary>
+    <secondary>Evaluation only at runtime</secondary>
+  </indexterm>
 </section>





More information about the icinga-checkins mailing list