Leap Second Coming In June, 2012

Zoxed writes "IERS have just announced a leap second due at midnight, June 30th this year. Are your systems ready?" The last leap second added was at the end of 2008.

Listen to WWV in North America

[Clueless Moron]

On 5, 10, 15 or 20 MHz: at 00:00Z you will hear minute consisting of 61 seconds.

If you happen to have a radio controlled timepiece, this will also be your chance to see if they handle the leap second conversion or took the lazy way out and just rely on the next time sync fix the time.

00:00UTC June 30th 2012 is a Saturday evening in North America. What better way to celebrate a Saturday night?

It's a hassle, but a tiny one...

[ElVee]

Leap seconds are a tiny bit of problem when you have to time-stamp transactions coming in from all over the globe and keep them in date/time order. Some OSes don't support leap seconds, which complicates matters. We have the procedures documented from the last time this happened in 2008, but, of course, we've changed OS, DB and message queue vendors since then, so nothing applies anymore.

Time to spin up a new project and pay some high-priced consultants a lot of money to rewrite the procedures documentation yet again. I suspect we'll take the coward's way out and shut down processing for a minute before until a minute after and resync the clocks in the interim.

That will, of course, be charged to our SLA downtime, which will affect everyone's performance reviews at the end of the year. All this for a single goddamn second.

Re:OpenNTPD

[klapaucjusz]

have written most of OpenNTPD.

And you admit it?

I am sick and tired of wasting energy on each and every unfounded accusation someone posts somewhere.

Please show me where the OpenNTPD code computes the dispersion and root delay that it sends to clients, and I will retract my claim.