Hi all,
this appears to be the explanation for the bogus leap second:
https://berthub.eu/articles/posts/leapseconds-expose-bugs-even-when-they-dont-happen/
Have fun,
Darren
On Sat, 2021-11-27 at 09:22 -0600, Steven Sommars wrote:
> FYI.
>
> At 2021-11-27 00:00:00 UTC many public NTP servers
The International Earth Rotation Service (IERS) has declared that there will be
NO leap second in December 2021:
https://datacenter.iers.org/data/latestVersion/16_BULLETIN_C16.txt
https://www.usno.navy.mil/USNO/earth-orientation/leap-second-announcement
Erik
Sorry Andy, the latest IERS Bulletin C (
https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat) specifically says
that there WON'T be a leap second this new-year.
Regards,
Peter Vince
On Sat, 27 Nov 2021 at 20:19, Andy Talbot wrote:
>
> A leap second is due 31 December. I'm
A leap second is due 31 December. I'm sure I've seen reference to a "leap
second pending" flag in some reference to time keeping somewhere.
Andy
www.g4jnt.com
On Sat, 27 Nov 2021 at 15:23, Steven Sommars
wrote:
> FYI.
>
> At 2021-11-27 00:00:00 UTC many public NTP servers began setting the
>>The incorrect leap indicator began 256 weeks + 1 days since the previous
leap second.
The incorrect leap indicator began 256 weeks - 1 day since the previous
leap second.
Sorry for sign error
On Sat, Nov 27, 2021 at 11:38 AM Steven Sommars
wrote:
> A number of the NTP servers are LeoNTP.
A number of the NTP servers are LeoNTP. The 1.24 firmware release (
https://leontp.com/firmware/) seems to fix the problem.
(My local LeoNTP now sets leap=0).
There may be a common bug affecting multiple ntp server models. The
incorrect leap indicator began 256 weeks + 1 days since the
On 27/11/2021 15:22, Steven Sommars wrote:
FYI.
At 2021-11-27 00:00:00 UTC many public NTP servers began setting the leap
indicator to 1.
This may be gpsd related
Yes, I see it on [possibly] one of my ISP's servers:
cpc137586-lock4-2-0-cust263.6-1.cable.virginm.net
86.3.245.8
I wrote
