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

[Poul-Henning Kamp]

In message <20080328201301.GA20923 at cox.net>, Greg Hennessy writes:

>> 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.



] Coordinated Universal Time (UTC) includes leap seconds. However,
] in POSIX time (seconds since the Epoch), leap seconds are ignored
] (not applied) to provide an easy and compatible method of computing
] time differences. Broken-down POSIX time is therefore not necessarily
] UTC, despite its appearance.

More at A.4.14 in:

http://www.opengroup.org/onlinepubs/009695399/xrat/xbd_chap04.html


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.