[icinga-checkins] icinga.org: icinga-doc/next: typos / wrong formatting

git at icinga.org git at icinga.org
Wed Apr 10 21:09:54 CEST 2013


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

Author: Wolfgang <wnd at gmx.net>
Date:   Tue Dec  4 22:27:27 2012 +0100

typos / wrong formatting

---

 de/distributed.xml        |   18 ++++++++++--------
 en/upgrading_idoutils.xml |    2 +-
 2 files changed, 11 insertions(+), 9 deletions(-)

diff --git a/de/distributed.xml b/de/distributed.xml
index ee7bd5b..88d66e2 100644
--- a/de/distributed.xml
+++ b/de/distributed.xml
@@ -130,14 +130,15 @@
 
     <para>Die Definition für den <emphasis>submit_check_result</emphasis>-Befehl sieht ungefähr so aus:</para>
 
-    <screen>
- <emphasis role="bold">define command{ command_name submit_check_result command_line &url-icinga-libexec;/eventhandlers/submit_check_result $HOSTNAME$ '$SERVICEDESC$' $SERVICESTATE$ '$SERVICEOUTPUT$' }</emphasis>
-    </screen>
+    <programlisting> define command{ 
+    command_name submit_check_result
+    command_line &url-icinga-libexec;/eventhandlers/submit_check_result $HOSTNAME$ '$SERVICEDESC$' $SERVICESTATE$ '$SERVICEOUTPUT$'
+ }</programlisting>
 
     <para>Die <emphasis>submit_check_result</emphasis> Shell-Scripte sehen ungefähr so aus (ersetzen Sie <emphasis>central_server</emphasis>
     durch die IP-Adresse des zentralen Servers):</para>
 
-    <screen> #!/bin/sh
+    <programlisting> #!/bin/sh
  # Arguments:
  #  $1 = host_name (Short name of host that the service is
  #       associated with)
@@ -167,7 +168,7 @@
  # pipe the service check info into the send_nsca program, which
  # in turn transmits the data to the nsca daemon on the central
  # monitoring server
- /bin/printf "%s\t%s\t%s\t%s\n" "$1" "$2" "$return_code" "$4" | &url-icinga-base;/bin/send_nsca -H <emphasis> central_server</emphasis> -c &url-icinga-base;/etc/send_nsca.cfg</screen>
+ /bin/printf "%s\t%s\t%s\t%s\n" "$1" "$2" "$return_code" "$4" | &url-icinga-base;/bin/send_nsca -H <emphasis> central_server</emphasis> -c &url-icinga-base;/etc/send_nsca.cfg</programlisting>
 
     <para>Das Script oben geht davon aus, dass das send_nsca-Programm und die Konfigurationsdatei (send_nsca.cfg) in den Verzeichnissen
     <emphasis>&url-icinga-base;/bin/</emphasis> und <emphasis>&url-icinga-base;/etc/</emphasis> zu finden sind.</para>
@@ -332,9 +333,10 @@
     Befehl namens 'service-is-stale' und benutzen den Befehlsnamen in der <emphasis>check_command</emphasis>-Option Ihrer Services. Hier
     nun, wie die Definition aussehen könnte...</para>
 
-    <screen>
- <emphasis role="bold"> define command{ command_name service-is-stale command_line &url-icinga-libexec;/check_dummy 2 "CRITICAL: Service results are stale" }</emphasis>
-    </screen>
+    <programlisting> define command{
+    command_name service-is-stale
+    command_line &url-icinga-libexec;/check_dummy 2 "CRITICAL: Service results are stale"
+ }</programlisting>
 
     <para>Wenn &name-icinga; feststellt, dass das Service-Ergebnis abgestanden ist und das <emphasis
     role="bold">service-is-stale</emphasis>-Kommando aufruft, wird das <emphasis>&url-icinga-libexec;/check_dummy</emphasis>-Plugin
diff --git a/en/upgrading_idoutils.xml b/en/upgrading_idoutils.xml
index 28498ad..3c4e4df 100644
--- a/en/upgrading_idoutils.xml
+++ b/en/upgrading_idoutils.xml
@@ -211,7 +211,7 @@
   </section>
 
   <section xml:id="upgrade1.0.3">
-    <title>>Upgrading &name-idoutils; to 1.0.3</title>
+    <title>Upgrading &name-idoutils; to 1.0.3</title>
 
     <para>There were some few minor changes:</para>
 





More information about the icinga-checkins mailing list