Re:Confirmed: Windows Azure downtime caused by leap-day bug
by obtu on Thursday March 01, 2012 @06:11AM
(#3651685)
Nope, Unix time is aligned on UTC days, which means it jumps back by one when a leap second is inserted (and would jump forward when one is deleted): https://en.wikipedia.org/wiki/Unix_time
Re:Confirmed: Windows Azure downtime caused by leap-day bug
by thwarted on Thursday March 01, 2012 @04:30PM
(#3654142)
Ah, well I stand corrected. That being said, it seems that UNIX time doesn't take leap seconds into account physically, but they are logically visible when viewing the change over time.
It returns the number of actual seconds that have elapsed since the epoch, the only way to do this is to ignore leap seconds. When leap seconds occur, they don't actually exist, they just change the offset to keep things in sync. Every second the time(3) function returns exists uniquely and none are skipped, there are no ambiguous values, which you can't say if leap seconds were not ignored.