On Wed, Jun 15, 2011 at 15:21 UTC, Charles Elliott <[email protected]> wrote: > server 127.127.1.0 iburst minpoll 4 maxpoll 4 > fudge 127.127.1.0 stratum 12 > > Yet NTPD is constantly changing the curTimeAdjustment. Here is the evidence > from my program:
ntpd "freewheels" as orphan parent or using the LOCAL driver at the last-known frequency adjustment persisted in the driftfile, which given your configuration must have a default path even if one is not given. Assuming your system was synchronized to a NTP source at some time in the past, that frequency correction likely brings your PC's clock much closer to beating at 1 second per second. ntpd logs the initial "drift" value, if found, at startup. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
