Update documentation.

Refs #5795
This commit is contained in:
Gunnar Beutner 2014-05-22 13:33:54 +02:00
parent 46165dbccf
commit 7223ae1dc2
5 changed files with 7 additions and 7 deletions

View File

@ -91,7 +91,7 @@ The `include` directive can be used to include other files.
/** /**
* The Icinga Template Library (ITL) provides a number of useful templates * The Icinga Template Library (ITL) provides a number of useful templates
* and command definitions. * and command definitions.
* Common monitoring plugin command definitions are included seperately. * Common monitoring plugin command definitions are included separately.
*/ */
include <itl> include <itl>
include <plugins> include <plugins>

View File

@ -308,7 +308,7 @@ failure of the `icinga2a` instance, `icinga2b` will take over automatically.
endpoints = [ "icinga2a", "icinga2b" ] endpoints = [ "icinga2a", "icinga2b" ]
} }
The `check-satellite` zone is a seperated location and only sends back their checkresults to The `check-satellite` zone is a separated location and only sends back their checkresults to
the defined parent zone `config-ha-master`. the defined parent zone `config-ha-master`.
object Zone "check-satellite" { object Zone "check-satellite" {

View File

@ -16,7 +16,7 @@ For general support questions, please refer to [https://www.icinga.org/support/]
Make sure that the debug symbols are available for Icinga 2. Make sure that the debug symbols are available for Icinga 2.
The Icinga 2 packages provide a debug package which must be The Icinga 2 packages provide a debug package which must be
installed seperately for all involved binaries, like `icinga2-bin` installed separately for all involved binaries, like `icinga2-bin`
or `icinga2-ido-mysql`. or `icinga2-ido-mysql`.
# yum install icinga2-bin-debuginfo icinga2-ido-mysql-debuginfo # yum install icinga2-bin-debuginfo icinga2-ido-mysql-debuginfo
@ -61,12 +61,12 @@ If Icinga 2 aborted its operation abnormally, generate a backtrace.
Identifying the problem may require stepping into the backtrace analysing Identifying the problem may require stepping into the backtrace analysing
the current scope, attributes and possible unmet requirements. `p` prints the current scope, attributes and possible unmet requirements. `p` prints
the value of the selected variable or function call result, if applicable. the value of the selected variable or function call result.
(gdb) up (gdb) up
(gdb) down (gdb) down
(gdb) p checkable (gdb) p checkable
(gdb) p checkable-GetName() (gdb) p checkable.px->m_Name
### <a id="development-debug-gdb-breakpoint"></a> GDB Breakpoints ### <a id="development-debug-gdb-breakpoint"></a> GDB Breakpoints

View File

@ -166,7 +166,7 @@ Example:
* CSV * CSV
CSV Output uses two levels of array seperators: The members array separator CSV Output uses two levels of array separators: The members array separator
is a comma (1st level) while extra info and host|service relation separator is a comma (1st level) while extra info and host|service relation separator
is a pipe (2nd level). is a pipe (2nd level).

View File

@ -15,7 +15,7 @@ include "constants.conf"
/** /**
* The Icinga Template Library (ITL) provides a number of useful templates * The Icinga Template Library (ITL) provides a number of useful templates
* and command definitions. * and command definitions.
* Common monitoring plugin command definitions are included seperately. * Common monitoring plugin command definitions are included separately.
*/ */
include <itl> include <itl>
include <plugins> include <plugins>