On Thu, May 15, 2008 at 08:57:59PM +0200, Volker Jahns wrote: > FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time > drift > > running ntpdate every half hour shows that the system looses about 10-14 sec > each time. > 15 May 10:06:48 ntpdate: step time server 184.108.40.206 offset > -13.799602 sec > 15 May 10:36:48 ntpdate: step time server 220.127.116.11 offset > -12.813941 sec > 15 May 11:06:48 ntpdate: step time server 18.104.22.168 offset > -13.651921 sec > 15 May 11:36:50 ntpdate: step time server 22.214.171.124 offset > -11.109298 sec > 15 May 12:06:50 ntpdate: step time server 126.96.36.199 offset > -11.836499 sec
[...] > What would be your suspicion on the large time drift of the FreeBSD > 6.2 system? Its PC commodity-grade. Not all that unusual even for stuff sold claiming to be a "server". This is in no small part why ntpd exists. nptd calculates a correction coefficient and (under FreeBSD) stores it in /var/db/ntpd.drift for use on next start so as to more quickly establish a lock. So in short ntpd calibrates your clock in order to minimize the corrections required. Is The Right Thing To Do. -- David Kelly N4HHE, [EMAIL PROTECTED] ======================================================================== Whom computers would destroy, they must first drive mad. _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"