summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authormbalmer <mbalmer@openbsd.org>2006-10-27 11:28:40 +0000
committermbalmer <mbalmer@openbsd.org>2006-10-27 11:28:40 +0000
commita901f0e11c16dbce705fa72b1f2330fad2320dc4 (patch)
tree19cadd95f3b3bf2f926b11025493eb285df3a470 /lib
parentPartially revert 1.33 the range calculation change for bandit (diff)
downloadwireguard-openbsd-a901f0e11c16dbce705fa72b1f2330fad2320dc4.tar.xz
wireguard-openbsd-a901f0e11c16dbce705fa72b1f2330fad2320dc4.zip
udcf(4) degraded the sensor status from OK to WARNING on the first receiption
error, which is to fast as this does not give ntpd the opportunity to use the sensor value. If we decode a valid time information, it has to be available to applications for some minimal time. I choose a value of 5 minutes. If we do not receive any new valid time information during this period, the sensor will be degraded to WARNING, and after another fifteen minutes it will be further degraded to CRITICAL. "makes sense to me" henning@, "sure" deraadt@
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions