you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 years ago (1 child)

I didn't say Unix time, I said UTC. And no it won't report negative time, not unless somehow the system clock was modified while it was running..

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago* (last edited 2 years ago) (1 child)

    not unless somehow the system clock was modified while it was running..

    Which is how most systems handle leap seconds.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago* (1 child)

    Leap seconds still make time go forwards, not backwards. NTP clients would also resolve small time discrepancies while still advancing forwards prior to the next time sync.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago* (1 child)

    Leap seconds can make time go both ways, but adding them makes time stop/go back because 24:00:00 cannot be represented as 1/86400 part of day N instead of day N+1 on major OSes. And they were only added so far.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago* (last edited 2 years ago) (1 child)

    It doesn't work like that. UTC goes forward always. Leap seconds are scheduled and known in advance. NTP time services will just smear time advancement a little to account for an additional second. Time never has to go backwards. This is how Google does it.

  • source
  • parent
  • hideshow 2 child comments