Post your comments for Leap Second Bedevils Web Systems Over Weekend here
Page 1 of 1
Leap Second Bedevils Web Systems Over Weekend
#2
Posted 02 July 2012 - 08:06 AM
( FROM ANOTHER FORUM ):
Please, Correct Me If I Am Wrong.
I Understand The Need To Add An Extra Second.
But Most Software Is Not Prepared To Handle The '60' In The Seconds Field.
So, Instead Of Adding An Extra Second Immediately Before Midnight, Why Not Add It Immediately After - ... '57' '58' '59' '00' '00' '01' '02' ... ?
Repeating Just One Second Is Something Very Small, Compared To The Winter Daylight Savings Correction When A Whole Hour Is Repeated, Right ?
Please, Correct Me If I Am Wrong.
I Understand The Need To Add An Extra Second.
But Most Software Is Not Prepared To Handle The '60' In The Seconds Field.
So, Instead Of Adding An Extra Second Immediately Before Midnight, Why Not Add It Immediately After - ... '57' '58' '59' '00' '00' '01' '02' ... ?
Repeating Just One Second Is Something Very Small, Compared To The Winter Daylight Savings Correction When A Whole Hour Is Repeated, Right ?
#3
Posted 02 July 2012 - 08:16 AM
A41202813, on 02 July 2012 - 08:06 AM, said:
( FROM ANOTHER FORUM ):
Please, Correct Me If I Am Wrong.
I Understand The Need To Add An Extra Second.
But Most Software Is Not Prepared To Handle The '60' In The Seconds Field.
So, Instead Of Adding An Extra Second Immediately Before Midnight, Why Not Add It Immediately After - ... '57' '58' '59' '00' '00' '01' '02' ... ?
Repeating Just One Second Is Something Very Small, Compared To The Winter Daylight Savings Correction When A Whole Hour Is Repeated, Right ?
Please, Correct Me If I Am Wrong.
I Understand The Need To Add An Extra Second.
But Most Software Is Not Prepared To Handle The '60' In The Seconds Field.
So, Instead Of Adding An Extra Second Immediately Before Midnight, Why Not Add It Immediately After - ... '57' '58' '59' '00' '00' '01' '02' ... ?
Repeating Just One Second Is Something Very Small, Compared To The Winter Daylight Savings Correction When A Whole Hour Is Repeated, Right ?
Typically daylight saving time is handled with a change to the effective timezone—in the UK we have GMT (Greenwich Mean Time) in the winter months, and BST (British Summer Time) in the Summer, so strictly speaking the hours are not duplicated. Whether repeating 00 would cause problems, I'm not sure. Google made use of a "leap smear", by slightly lengthening their "seconds" leading up to the change.
Edit: the trouble with repeated seconds comes from sub-second comparisons—is 00:00:00.500 before or after 00:00:00.250? Using 60 preserves event ordering, as does the leap smear.
This post has been edited by crosswordbob: 02 July 2012 - 08:24 AM
If I dispute one single point in a post, that should not be taken as an indication that I agree/disagree with any other point made by that poster or anyone else in the thread. Or anywhere else. Ever.
#4
Posted 02 July 2012 - 01:33 PM
The Linux kernel patch that was released in March did NOT fix this issue. The problem is present even in current Linux kernels - this was not a matter of "unpatched systems", as the article incorrectly asserts. Despite attempts to test for problems, this issue was not caught until it bit people on Saturday. A patch is now in development, as the issue, post facto, seems to have been isolated and understood. Some informative discussion can be found here: http://www.gossamer-...1559653#1559653
Share this topic:
Page 1 of 1
Help











