[LEAPSECS] operational time -- What's in a name?

Greg Hennessy greg.hennessy at cox.net
Fri Mar 28 16:13:01 EDT 2008



> Well, time_t is UTC, which two unfortunate problems.


Is it? I always thought it was a count of the number of seconds since
the start of the unix epoch, not counting leap seconds.

There having been 24 (I think) leap seconds since 1970, the unix
epoch, if POSIX is UTC, then it can't be true that time_d % 86400 == 0
is midnight.

I've always considered time_t to be POSIX time, not UTC.



More information about the LEAPSECS mailing list