[181467] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Tore Anderson)
Fri Jun 26 01:43:44 2015
X-Original-To: nanog@nanog.org
Date: Fri, 26 Jun 2015 07:42:29 +0200
From: Tore Anderson <tore@fud.no>
To: Stefan Schlesinger <sts@ono.at>
In-Reply-To: <BF80D13E-D8B8-4768-A751-3DC66AF5DCA9@ono.at>
Cc: NANOG mailing list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
* Stefan Schlesinger <sts@ono.at>
> > On 25 Jun 2015, at 03:14, Damian Menscher via NANOG <nanog@nanog.org> wrote:
> >
> > http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html
> > comes dangerously close to your modest proposal.
>
> I wonder why Google hasn't published the patch yet. Leap smear sounds
> like the sane way to do leap seconds, and it would't break software
> at all, because time adjustments in the sub-second area are proven to
> work quite well.
It's implemented in chronyd versions 2.0 and up, for what it's worth.
The required config directive is "leapsecmode slew".
There's a nice blog post explaining how this feature, as well as some
other approaches on how to deal with the leap second, work here:
http://developerblog.redhat.com/2015/06/01/five-different-ways-handle-leap-seconds-ntp/
Tore
