Re: Seeking clarifaction of tai64nlocal and leap seconds
Brian Reichert <[email protected]> Tue, 18 Sep 2012 18:08:10 -0400
| Newsgroups | gmane.comp.djb.syslog |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Apr 01, 2011 at 02:47:41PM -0400, Brian Reichert wrote:
In other threads, on other forums, I've asked about
If libtai's leap-second table was up-to-date:
http://comments.gmane.org/gmane.comp.lib.libtai/361
And here, about the relationship of tai64nlocal and leap seconds
http://comments.gmane.org/gmane.comp.djb.syslog/1319
But I'm only now pawing through daemontools source:
http://cr.yp.to/daemontools/install.html
And to my naive eye, it looks like multilog doesn't use libtai, and
a such, I wonder how (if at all) it has a sense of leap seconds
when it generates timestamps.
The webpage/manpage for multilog says
Timestamping
The action
t
inserts an @, a precise timestamp, and a space in front of each line,
using the same format as tai64n. This is required to be the first
action.
This only describes the format of the timestamp, and what isn't
clear to me is if it _is_ a TAI timestamp. (I, for years, have
assumed that daemontool used libtai, and it's copy of leapsecs.dat.)
Am I missing something? What in the toolchain of mulitlog | tai64n
'knows' about leap seconds?
--
Brian Reichert <[email protected]>
BSD admin/developer at large