diff options
author | Marc Balmer <mbalmer@cvs.openbsd.org> | 2006-10-27 11:28:41 +0000 |
---|---|---|
committer | Marc Balmer <mbalmer@cvs.openbsd.org> | 2006-10-27 11:28:41 +0000 |
commit | e04f10b1c4d5f400e36cd20970ffe49c0f99e4c7 (patch) | |
tree | e3e282f4c80c4e3ba6dbed98a89e6455e1bb13c4 /share/man/man4/udcf.4 | |
parent | ec852c40ef3b496b075b991e59916d13c6095f3a (diff) |
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 'share/man/man4/udcf.4')
0 files changed, 0 insertions, 0 deletions