GPS Leap Second Scheduled!
Quoted 3 lines · David Lang
I am probably missing something, but can't you just ignore the leap second until you discover that the time is 1 sec off and then use the normal NTP procedure to get back to the exact time
Until the NTP procedure discovers and corrects this (a few minutes, plus correction time), anything that expects synchronised time between machines can go wrong.
Admittedly synchronisation isn't perfect anyway.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/faq.html
In article <[email protected]>,
Quoted 8 lines · Jamie Lokier
Quoted 3 lines · David Lang
I am probably missing something, but can't you just ignore the leap second until you discover that the time is 1 sec off and then use the normal NTP procedure to get back to the exact time
Until the NTP procedure discovers and corrects this (a few minutes, plus correction time), anything that expects synchronised time between machines can go wrong.
NTP has the capability to know in advance that a leap second is scheduled and act upon that at the correct time.
Check your logs the next time a leap second happens; xntpd does it.
Signature · 6 lines
Shields, CrossLink. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/faq.html