Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update description of use_aggressive_host_checking #278 #386

Merged
merged 6 commits into from
May 24, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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