Bert Gøtterup Petersen wrote:
Hi
I didn't think NTP used old timers like that...
NTP isn't!
This is an OS/Windows HAL layer bug.
Any idea on how to avoid this?
Replace the OS?
:-)
Terje
Bert
"Terje Mathisen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Bert Gøtterup Petersen wrote:
When running Windows I see a spike of about 16ms in the loopstats-files
on all the Windows nodes. The peculiar thing is that the spike occurs
every 24 hours and 15 minutes per machine, but not at the same time on
different machines.
Hmmm. Could this be an internal windows OS counter wrapping around?
24 hours + 15 min = 86400 + 900 = 87300 s
The original keyboard timer chip which generates the Dos 55 ms timer tick
had a 64 K period which was close to but not exactly one hour...
87300 / (24 * 65536) = 0.055038
Yes! This is the original DOS timer tick period which Windows is still
emulating for anything running inside a Dos box, as well as programs using
very old Windows APIs.
I'm willing to bet that the spike is caused by a once/day fixup of any
residual errors caused by the fact that this emulation isn't totally
accurate!
Terje
--
- <[EMAIL PROTECTED]>
"almost all programming can be viewed as an exercise in caching"
--
- <[EMAIL PROTECTED]>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
