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:
Jun 30 18:59:59 lupineblue kernel: Clock: inserting leap second
23:59:60 UTC
Jun 30 18:59:59 miska kernel: [17417912.380000] Clock: inserting leap
second 23:59:60 UTC
Jun 30 18:59:59 inuyasha kernel: Clock: inserting leap second 23:59:60
UTC
Jun 30 18:59:59 cactus kernel: Clock: inserting leap second 23:59:60
UTC Jun 30 18:59:59 kouga kernel: Clock: inserting leap second
23:59:60 UTC Jun 30 18:59:59 nira kernel: Clock: inserting leap
second 23:59:60 UTC Jun 30 16:59:59 iceflow kernel: Clock: inserting
leap second 23:59:60 UTC
Jun 30 19:59:59 mpu kernel: Clock: inserting leap second 23:59:60 UTC
Glad to hear I am not alone! On my network, only two out of 6 PCs were
affected.
Why do you think it happened?
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
