To: authorities responsible for the measurement and distribution of time
A positive leap second will be introduced at the end of June 2012. The sequence of dates of the UTC second markers will be:
2012 June 30, 23h 59m 59sThe difference between UTC and the International Atomic Time TAI is:
2012 June 30, 23h 59m 60s
2012 July 1, 0h 0m 0s
from 2009 January 1, 0h UTC, to 2012 July 1 0h UTC : UTC-TAI = - 34s
from 2012 July 1, 0h UTC, until further notice : UTC-TAI = - 35s
This means that tomorrow, 4:59:59 PM PDT will be followed by 4:59:60 PM PDT prior to the advent of 5:00:00 PM PDT.
Of course there is a leapsecond.com:
Now that you know what a leap second is, have you wondered if you can see one? Can you hear a leap second? Several of us enjoy capturing leap seconds. You have to be quick; you have to plan ahead. You have only one second to fish and then wait a year or two, or even seven, before your next chance. Below are examples of catching a leap second in the act.
As a kid in the summer of 1972 I used a short-wave radio cassette audio tape recorder to record the first leap second. Alas, I still can't find that tape.
Also, great news, everybody! The venerable leap second has gotten a stay of execution until at least 2015: ITU Radiocommunication Assembly defers decision to eliminate the leap second. The Earth gently wobbles in relief.
> Which, I think I've mentioned, is the coolest name for any organization ever.
The Directorate of Time was awesome in exactly the same way, until the Navy renamed it.
The Directorate of Time was awesome in a slightly different way.
Because it had a Director.
Whose job title was Director of the Directorate of Time.
If I had that job, I think I would be compelled to legally change my name to "The Doctor".
The only possible rival for coolest name would be the Aircrash Bureau, which tells you when you're going down.
The tone at the ITU Radiocommunication Assembly in January was something like "You raised this under-considered document to the international assembly without having achieved consensus?". The aftermath was Resolution COM6/20 (WRC-12) which has become WRC-15 agenda item 1.14, and its rather severe tone indicates that the plenary assembly expects the sub-groups to march double-time in order to present a better proposal by 2015.
International travel could be quite disorienting back before the creation of the International Earth Rotation Service, back when every country set their own rate of rotation.
Are you kidding??!? In the eighteenth and nineteenth centuries each town set its own rotation.
In the nineteenth century, the town's railway station rotated independently of the town hall. So to speak.
In the 13th century, Benedictine monks would occasionally record things like "yon towne hath a widdershins turning much unlike it's Fellowes, which is cause for muche distress amongst the Merchants"
Let's hope the IERS doesn't give serious consideration to Tom Van Baak's proposals:
"Earth as a frequency standard, suggested improvements:
* Thoroughly clean, and dry with cloth
* Remove surrounding gas and water vapor
* Wait for core to cool before use
* Re-align axis of rotation (wobbling)
* Keep away from nearby moon (tides)
* Keep away from sun (tempco)
* Re-adjust rate (avoid leap seconds)"
iOS Dali Clock did not display 14:59:60. I'm disappointed!
Yeah, that's because NTP drifts the clock to compensate for leap seconds. Sadness.
I captured it, as I'm sure many did. Thanks for reminding me. leap second 2012
Aaaand the leap second can crash Linux:
Yep, there's a patch proposed to fix the livelock.
Oddly none of my SMP NTP machines crashed.
My personal ones were fine. After 6 weeks off, though, I'm going to go back to work today and find out what happened over the weekend...
Yeah, that was pretty special. Also JVM and mysql processes going CPU-bound.
Reading up on this stuff I found that Arthur David Olson designed, coded, and deployed a fix for this years ago, as part of his nearly-universal timezone database. Instead of fucking around with the system clock, you let the clock proceed at one second per second always and just correct the textual representations of times. Each leap second just means some new timezone definitions. Unfortunately the current POSIX explicitly prohibits this. I'm hoping that yesterday's Leapocalypse will get people to revisit this stupid standards issue and do it the right way.
The hard part of change is getting good ideas inserted into the ITU-R process.
As things stand that can only be done by delegates of member nations.
Don't miss this analysis of the ITU bureaucrats http://boingboing.net/2012/02/21/fcc-commissioner-dont-let-t.html
Thanks for the leapsecond.com link. It looks pretty awesome: