[154394] in North American Network Operators' Group
RE: F-ckin Leap Seconds, how do they work?
daemon@ATHENA.MIT.EDU (Keith Medcalf)
Tue Jul 3 15:08:16 2012
Date: Tue, 03 Jul 2012 13:06:11 -0600
In-Reply-To: <4FF33AE1.50105@foobar.org>
From: "Keith Medcalf" <kmedcalf@dessus.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
God damn that's a horrid piece of shit web site. You have to disable secur=
ity and permit remote code execution or it does not work.
What a crock!
---
() ascii ribbon campaign against html e-mail
/\ www.asciiribbon.org
> -----Original Message-----
> From: Nick Hilliard [mailto:nick@foobar.org]
> Sent: Tuesday, 03 July, 2012 12:33
> To: Saku Ytti
> Cc: nanog@nanog.org
> Subject: Re: F-ckin Leap Seconds, how do they work?
>
> On 03/07/2012 18:59, Saku Ytti wrote:
> > Leap bugs are NOT known. Most people have no idea unixtime is not
> > monotonically increasing.
> > I had no idea myself until sunday, I had assumed we really go 59 -> 60 =
->
> > 00, but we go 59 -> 59 -> 00. So 59.1 can happen before or after 59.2.
> > To me this is fundamentally and inherently broken.
>
> Well, yeah, it's not obvious that a minute can have anywhere between 59 a=
nd
> 62 seconds. Certainly if POSIX were being redesigned, they ought to
> consider using libtai.
>
> Google's approach to this is interesting:
>
> > http://googleblog.blogspot.ie/2011/09/time-technology-and-leaping-
> seconds.html
>
> i.e. controlled clock slew until the correct offset is reached, thereby
> allowing their developers to assume a monotonic system clock.
>
> Nick
