Skip to content

Commit

Permalink
Update description of use_aggressive_host_checking #278 (#386)
Browse files Browse the repository at this point in the history
Update description of `use_aggressive_host_checking` in the sample configuration to clarify what effect it has on host states.

Signed-off-by: nook24 <info@nook24.eu>
  • Loading branch information
nook24 committed May 24, 2022
1 parent f626880 commit d722b63
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions sample-config/naemon.cfg.in
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit d722b63

Please sign in to comment.