[ntp:questions] Re: win32 undisciplined local clock sync time

Harlan Stenn stenn at ntp.isc.org
Mon Nov 28 18:50:06 UTC 2005


iburst will only help of the "destination" machine is in "state 4", which
means the ntpd on the destination machine is sync'd and has a known good
drift value.

The very first time ntpd is started on a machine this can take anywhere from
an hour to a day or more.

Once a good drift value is obtained (and assuming the platform can keep time
"well enough"), a restart should get to state 4 in about 11 seconds or so.


More information about the questions mailing list