Slashdot Mirror
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.
← Back to Stories (view on slashdot.org)
The *LAST* leap second occured in 2012
I demand at least 3^10x8 seconds advance warning.
When the foot seeks the place of the head, the line is crossed. Know your place. Keep your place. Be a shoe.
I use NTP on my systems!
They fix the timers, I got mine fixed. Automagically!
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
One small step for man; one leap second for computer systems?
php coders. pah.
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?
Well, I think we now have a good example of how NOT to code.
I am very small, utmostly microscopic.
Ugh. You have reminded me why I left Perl behind for a language that has strict typing.
"Please describe the scientific nature of the 'whammy'" - Agent Scully
php scripters. pah.
FTFY
Has NOTHING AT ALL to do with the US government. Pah !
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
Wait a minute. Isn't this the code that documents itself?
I choose friends for sigs
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.
- Pithy comment goes here.
"Officer. The reason I was driving so fast is that I was trying to adjust my watch using relativistic time dilation."
Have gnu, will travel.
I need a lot more warning than this! We won't even be able to have the meeting in time to decide who to invite to the pre-project inception meeting.
I want a list of atrocities done in your name - Recoil
That's because the perl interpreter sends each script to Larry Wall for review and correction.
Such a pity you didn't invest that extra second in checking your spelling and grammar. =p
OpenNTPD just ignored the leap second
OpenNTPD has clearly been written by someone who doesn't understand NTP. For example, it advertises incorrect root delay and disperson values, which can cause clients to fail to achieve a majority vote, or to pick the wrong peer to synchronise against. (Earlier versions were even worse, they advertised themselves as being at stratum 0, which could cause synchronisation loops; this has thankfully been fixed, but it doesn't inspire much confidence in the authors' competence.)
I've also found OpenNTP to fail to regulate the local clock on dodgy hardware (it would oscillate wildly, with an amplitude of 3 seconds or so), in situations where the reference ntpd coped just fine.
Folks, do yourself and everyone a favour -- run the reference NTP, run chrony, heck, run some SNTP client, but please avoid OpenNTPD.