[ntp:questions] Re: synchronisation lost errors with
Adrian 'Dagurashibanipal' von Bidder
grazdan at fortytwo.ch
Thu Oct 16 05:48:01 UTC 2003
Clinging to sanity, Ralf Hildebrandt mumbled in his beard:
> I'm using ntpd-4.1.2 (Debian/unstable) with the following config:
> Oct 13 12:11:37 hummus2 ntpd: time reset 13.300551 s
> Oct 13 12:11:37 hummus2 ntpd: synchronisation lost
> Oct 13 12:20:21 hummus2 ntpd: synchronisation lost
> Oct 13 12:23:33 hummus2 ntpd: synchronisation lost
> Oct 13 12:26:53 hummus2 ntpd: time reset 14.710572 s
Your computer's clock is very, very bad. You probably have - as was said - a
ntp.drift of (-)500.000, and 'ntpq -c rv' gives you a 'frequency=500'
Look in the NTP FAQ, question 8.2.something, it tells you how to use the
'tickadj' program to fix this (Once you've calculated the correct value,
you'll need to set that value on reboot, of course).
Better delete the ntp.drift file before starting ntpd after you calculated
the tickadj value - you fiddled with that value, so the cached value could
only confuse ntpd and make it take longer to establish the correct value.
Even the simplified child tax credit form is 12 pages long.
-- Prospect magazine about the english taxation and benefits system
More information about the questions