Once upon a time, Owen DeLong <[email protected]> said: > UTC (and the system clock) should not move backwards, but, rather they repeat > second 59. UTC goes 58->59->00 most of the time, but during a leap second, it > should go 58->59->59->00). It's not so much going backwards as dropping a > chime.
That would be true if the highest resolution clock was one second, but that's not the case. Anything that uses gettimeofday() sees time repeat (which means it counts up to 59.999999 seconds and then goes back to 59.000000). -- Chris Adams <[email protected]> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
