On Sep 13, 2007, at 18:51, Jan Hoevers wrote:
> The scoring algorithm gives penalties to servers with an offset of
> more
> than 100 millisec. Take a good look at the correlation between the
> score
> history and offset history graphs. Do you agree that this is what's
> happening?
Yeah - that is what is happening.
It doesn't really matter if it's not entirely accurate, as long as
the system ends up with a "yes" answer
to 2a or 2b in this decision tree:
1) Is the server responding reasonably to ntp requests?
if yes:
2a) is the server marked active in the pool?
if no:
2b) is the server marked in-active in the pool?
Being 100ms off for short intervals is okay for clients using sntp
(presumably they don't want much accuracy) and ntpd will probably
pick another server to synchronize with, but your server is still
helpful in deciding the correct time if one of the other configured
clocks is going completely nuts.
- ask
--
http://develooper.com/ - http://askask.com/
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
