NTP servers may incorrectly advertise leap=1 which can propagate to clients. Unfortunately this is not a rare occurrence.
On Wed, Apr 1, 2015 at 8:47 AM, etameta <[email protected]> wrote: > I've seen this on several machines in Italy: > > Apr 1 01:59:59 hostname kernel: [2552517.563918] Clock: inserting leap > second 23:59:60 UTC > > Now, a leap second is NOT scheduled for today, so I wonder what's > happening. > > It's been confirmed on Ubuntu, Debian and RedHat boxes. I don't have access > to boxes with other OSes, but my guess is this isn't client-specific. > > On the machines where it happened, it happened at around 02:00 GMT+0200 > today (April 1st). > > Has it been observed outside Italy? > > Is it an April's fool prank? > > Thanks. > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool > _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
