From d722b63408e37dbf11010513faf742f191e8ffcf Mon Sep 17 00:00:00 2001 From: Daniel Date: Tue, 24 May 2022 15:02:24 +0200 Subject: [PATCH] Update description of use_aggressive_host_checking #278 (#386) Update description of `use_aggressive_host_checking` in the sample configuration to clarify what effect it has on host states. Signed-off-by: nook24 --- sample-config/naemon.cfg.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sample-config/naemon.cfg.in b/sample-config/naemon.cfg.in index 6c155963..5d7c159d 100644 --- a/sample-config/naemon.cfg.in +++ b/sample-config/naemon.cfg.in @@ -521,9 +521,11 @@ interval_length=60 # AGGRESSIVE HOST CHECKING OPTION # If you don't want to turn on aggressive host checking features, set # this value to 0 (the default). Otherwise set this value to 1 to -# enable the aggressive check option. Read the docs for more info +# enable the aggressive check option. When disabled (0), Naemon will treat +# WARNING states as UP for host checks. This let's you use the same +# check plugin for host and service checks. Read the docs for more info # on what aggressive host check is or check out the source code in -# base/checks.c +# src/naemon/checks_host.c use_aggressive_host_checking=0