-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-12-22 at 18:28 -0000, Dave Howorth wrote: ...
See https://www.theregister.co.uk/2016/12/02/google_public_ntp_servers/ and particularly the comments. As is often the case, El Reg has the skinny.
+++------------ Google's also explained how its NTP servers will handle leap seconds, one of which will delay the arrival of 2017 by a second. “No commonly used operating system is able to handle a minute with 61 seconds,” Google says, so “Instead of adding a single extra second to the end of the day, we'll run the clocks 0.0014% slower across the ten hours before and ten hours after the leap second, and “smear” the extra second across these twenty hours. For timekeeping purposes, December 31 will seem like any other day.” But not if you use an NTP server that uses another method leap second handling. On the page for its time service, Google says “We recommend that you don’t configure Google Public NTP together with non-leap-smearing NTP servers.” - ------------++- Oh, my :-( Given that, I will never use time.google.com - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo9WJYACgkQtTMYHG2NR9XQTQCeK5y+FbTLCjSeY83aauIhF/fM BtgAn1eTyQhf19DFSLj+MbEFMXsAXnbx =Cpoh -----END PGP SIGNATURE-----