Marc Muehlfeld wrote: > Martin Burnicki schrieb: >> As a test, you might stop ntpd, then set the system time manually running > > # date -u; ntpdate ptbtime1.ptb.de > Di 16. Okt 09:08:09 UTC 2007 > 16 Oct 11:08:13 ntpdate[2586]: step time server 192.53.103.108 offset > 3.867615 sec > > > >> Then let the system time freewheeling, and run > > # date -u; ntpdate -q ptbtime1.ptb.de > Di 16. Okt 09:17:12 UTC 2007 > server 192.53.103.108, stratum 1, offset 2.711909, delay 0.06961 > 16 Oct 11:17:12 ntpdate[2927]: step time server 192.53.103.108 offset > 2.711909 sec > > # date -u; ntpdate -q ptbtime1.ptb.de > Di 16. Okt 09:33:04 UTC 2007 > server 192.53.103.108, stratum 1, offset 7.275004, delay 0.06960 > 16 Oct 11:33:04 ntpdate[3562]: step time server 192.53.103.108 offset > 7.275004 sec > > > > > Please report whether the difference is growing slow or fast. > > As you can see, it it growing fast (more than 7 sec in 20 minutes)
Oops, that's too much. Maybe the adjtimex tool can help to decrease the initial drift to an acceptable value. Unfortunately I'm not familiar with adjtimex since I haven't had to use it, yet. Maybe you should search the archive of this group (just google ...), or someone else might jump in here ... Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
