3 ms·
A removed leap-second is gobs easier to handle. I can't say if it will or won't be handled properly, because I never tested it, but roughly you have three optio
by toast0 6y ago
A removed leap-second is gobs easier to handle. I can't say if it will or won't be handled properly, because I never tested it, but roughly you have three options:
a) software ignores it, and your clock is a second behind as of the discontinuity, and adjusts eventually
b) software handles it properly and jumps ahead
c) software handles it by explicitly dithering the difference over a day
d) c, but it also jumps ahead at the discontinuity
e) your network has a mix of b, c, and d, resulting in wonky clocks throughout the day, but generally still +/- 1 second of real time. This could be problematic for forensics, or for distributed software that uses time as measured on nodes to determine order of operations, but using time as measured on nodes requires constant vigilence to ensure clocks are in sync enough.
An added leap second is a lot trickier because at least Linux and FreeBSD simply repeat the last second of the minute at the discontinuity if you don't take special action to dither it. That brings two new problems:
a) real time is no longer monotonic
b) a logic error can result in repeating that second forever