Udo van den Heuvel wrote:
Nicholas Suan wrote:
On Sun, 2006-07-02 at 08:36 +0100, David J Taylor wrote:
Folks,
I recently had a glitch at 00:00 UTC on 2006 July 01 which I have
traced to a server telling me a leap-second was due when it was not.
http://www.david-taylor.myby.co.uk/ntp/ntp-events.htm#2006-07-01
Whilst I haven't been able to check which server gave this
indication, it may have been one of the UK pool servers.
All of my servers did this, even ones that don't use the pool as a
time source:
My server did not log anything.
It did so (sparsely) on newyear. Don't have the exact lines.
Did something go wrong? How can I check?
How can I fix?
- yes, the time-keeping went wild.
- I check using MRTG:
http://www.david-taylor.myby.co.uk/ntp/NTPandMRTG.txt
- you can also see if the value in ntp.drift is grossly different from
what you expect. I am finding values just short of the limit (say +496
and the limit is +500).
- I don't know how to fix the leap-second issue, but I found that stopping
ntp, setting the value in ntp.drift to a sensible figure for the
particular system, and restarting ntp cures the problem. If you don't
know a correct value for ntp.drift on your system, just delete the file.
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.net
Email: [EMAIL PROTECTED]
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
