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.
if (($mon == 5) && ($mday==30)) {
$sec = $sec + 1;
} else {
$sec = $sec;
}
Of course! My systems are second-to-none. You should see what it clocks in at - not exactly a minute set of figures! That's if you have the time..
One small step for man; one leap second for computer systems?
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?
Anybody else getting sick and tired of the government doing crap like this? It's like when Congress decided a few years back to change the start and end dates for Daylight Savings Time. I still have VCRs and computers that change to DST on the "wrong" days now because of this garbage.
Congress and the federal government: LEAVE THE DATE AND TIME ALONE. It's just fine without your intervention. This is why I am supporting Ron Paul in the 2012 elections -- he recognizes that there is a Constitutional role for the federal government. And screwing around with people's clocks is not in the Constitution.
that i wont get back.. tho i lost like 30 seconds of my life reading this story and commenting..
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
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.
...I suppose this is going to throw off my mayan calendar?... :(
"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
will be screwed
It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
Two days ago there were several articles stating that leap second might be abolished: http://www.scientificamerican.com/podcast/episode.cfm?id=leap-seconds-may-disappear-12-01-02 "This month the International Telecommunication Union will consider a proposal to abolish leap seconds."
Yes!! An extra second for drinking.
Who is this "Leap"? Why is his second coming so important?
Hey, did you think gettimeofday returned the number of seconds since the epoch? That a call to gettimeofday would return a value >= to the last call? Well, it doesn't, because it's based on UTC, which is defined as seconds since the epoch, minus leaps seconds.
As a result, a value returned by gettimeofday does not refer 1:1 to a point in time, and the clock will skip a second backwards at random moments (leap seconds happen when IERS says so).
I mean, you could put the leap second logic in the same place timevals are converted to a user-displayable format, like timezones, DST and, i don't know, leap YEARS, but NO, lets be absolutely retarded and break every program in the world that dares to make the assumption that time moves forward. There is also no other way to get the unix time.
Most people don't even know about it, which results in bugs (there was a story about that earlier), but honestly, I consider the systems that work like this broken and not the applications.
Is that ((leap second) coming) or (leap (second coming))?
There's a significant difference!
I'm old enough to remember when discussions on Slashdot were well informed.
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.
wat, no luv for Gene Ray all up in this thread?!!! For shame.
I never did understand what irradiating genetic material had to do with the natural timeframe of reality, but then, I'm not one of dem there big brains with a website on teh intarwebs.
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
> but NO, lets be absolutely retarded and break every program in the world that dares to make the assumption that time moves forward.
Unfortunately, we no longer can assume this now that we see faster-than-light transport may be on the horizon (viz. Tevatron experiments).
It took me a few seconds to figure out the title. At first I thought we were supposed to jump for joy that Jesus was making a comeback in June. Oh I don't know...which is more exciting?
http://www.acetonestudio.com
Yes, indeed. The gettimeofday() function should be used only when you need the time of day. If you actually don't care what time of day it is, but just want to measure the length of time between two events, you need a different time source.
man 2 clock_gettime
CLOCK_MONOTONIC
Clock that cannot be set and represents monotonic time since
some unspecified starting point.
CLOCK_MONOTONIC_RAW (since Linux 2.6.28; Linux-specific)
Similar to CLOCK_MONOTONIC, but provides access to a raw hard
ware-based time that is not subject to NTP adjustments.
Since the whole idea of CLOCK_MONOTONIC is that it is a time source unaffected by time changes, I assume that the "NTP adjustments" mentioned are merely adjustments to the clock speed rather that non-linearity introduced by changes to the system time. In other words, the difference is that CLOCK_MONOTONIC gives you seconds that are always exactly one second long to the precision that NTP allows, while CLOCK_MONOTONIC_RAW gives you seconds which may run too fast or too slow depending on your hardware, but both clocks are unaffected by changes to system time.
Well remember when there were only 10 months per year..... I don't know what the world is coming to nowadays.
All cows eat grass!