Re: Seeking clarifaction of tai64nlocal and leap seconds

Peter Wolfenden <[email protected]> writes:

> Multilog does indeed generate "pure" (which I used perhaps confusingly
> as a shorthand to mean "complying with documented standards") TAI64*
> date records.

I'm a little confused as to how multilog can do that without knowledge of
leap seconds.  The system time is generally going to be in UTC, not TAI,
so wouldn't multilog have to have leap second tables available to convert
from UTC to TAI?

See also http://cr.yp.to/daemontools/tai64n.html (referenced from the
multilog page) which says:

    The current implementation of tai64n relies on the UNIX gettimeofday
    library routine to return the current time as the number of TAI
    seconds since 1970-01-01 00:00:10 TAI.

Doesn't that mean that it's (somewhat blindly) assuming that there have
been 10 leap seconds since epoch, and will start generating incorrect
timestamps as further leap seconds are added?

-- 
Russ Allbery ([email protected])             <http://www.eyrie.org/~eagle/>