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 comment in the default naemon.cfg describes retention_update_interval as:
# RETENTION DATA UPDATE INTERVAL
# This setting determines how often (in minutes) that Naemon
# will automatically save retention data during normal operation.
# If you set this value to 0, Naemon will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting. If you have disabled
# state retention, this option has no effect.
retention_update_interval=60
But Naemon uses retention_update_interval * interval_length to calculate retention_update_interval itself. So the the value in naemon.cfg for retention_update_interval is not set in minutes. It is value * interval_length.
I don't know exactly how to update the text, but the current one is wrong^^
Just in case if you are asking yourself, how Nagios does this:
Nagios uses retention_update_interval * 60 (60 is hardcoded), so it is always in minutes, but i prefer the Naemon way. Just the documentation is confusing :)
The comment in the default
naemon.cfg
describesretention_update_interval
as:But Naemon uses
retention_update_interval * interval_length
to calculate retention_update_interval itself. So the the value innaemon.cfg
forretention_update_interval
is not set in minutes. It isvalue * interval_length
.naemon-core/src/naemon/sretention.c
Line 27 in ba3dc3e
I don't know exactly how to update the text, but the current one is wrong^^
Just in case if you are asking yourself, how Nagios does this:
Nagios uses
retention_update_interval * 60
(60 is hardcoded), so it is always in minutes, but i prefer the Naemon way. Just the documentation is confusing :)https://github.com/NagiosEnterprises/nagioscore/blob/345fd4e8257085ce7f3806ee4fb04008919f24e5/base/events.c#L593
The text was updated successfully, but these errors were encountered: