You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs on host objects list check_period as a required attribute but Naemon starts fine (even without warnings) if it's not set. In this case I guess it works just like if the time period was set to 24x7.
This behavior should either be changed or documented. There might be similar problems for other attributes but check_period was the only one I looked at.
The text was updated successfully, but these errors were encountered:
The docs on host
objects
list check_period as a required attribute but Naemon starts fine
(even without warnings) if it's not set. In this case I guess it
works just like if the time period was set to 24x7.
This behavior should either be changed or documented. There might be
similar problems for other attributes but check_period was the only
one I looked at.
check_period isn't required, and if one isn't supplied 24x7 will be
used. I'll make a note to amend the docs.
I've opened naemon/naemon.github.io#59 to track this documentation update instead. Thanks for reporting it @julianbrost, and sorry for the late feedback!
…-doesnt-compile-with-gcc7 to master
* commit 'b73ef00e50ca33e6c63116bcc7d0ed5beaba9675':
Check snprintf for encoding errors and truncation
Mark intentional fallthroughs in switch statements
The docs on host objects list
check_period
as a required attribute but Naemon starts fine (even without warnings) if it's not set. In this case I guess it works just like if the time period was set to24x7
.For services there is a check at naemon/configuration.c:1505 but for hosts there is only a check at naemon/configuration.c:1585 which only checks whether the timeperiod is valid if any is given.
This behavior should either be changed or documented. There might be similar problems for other attributes but
check_period
was the only one I looked at.The text was updated successfully, but these errors were encountered: