Kins Orekhov <[EMAIL PROTECTED]> writes:

> Yes, I have tried that and it didn't work for me.

> Comments for tai64nfrac says: 
> .... 
> Expects the input stream to be a sequence of lines beginning with @ (1), a
> timestamp in external TAI64N format, and a space.  Replaces the @ and the
> timestamp with fractional seconds since epoch (1970-01-01 00:00:00
> UTC). (2) The output time format is expected by qmailanalog (3).
> ....

> (1) - lines in my logs beginning with:
> 1999-11-24 17:43:07.542160 status: local 0/10 remote 0/20

> This is not what tai64nfrac expects (at least, no @ at the beginning).

You've already run tai64nlocal on your log file.  tai64nfrac doesn't
expect that (because I don't do that; I just run tai64nlocal when I need
to, since it's fast enough).

> (2) - looks like tai64nfrac supposed to replace with the same time format
> as I already have (see (1) )

No, that's just documentation of what the epoch is.  tai64nfrac does
produce the output you're expecting.

> Can someone educate me about those time formats (TAI64/TAI64N,
> fractional, etc.) I'm really confused about them.

qmail-analog expects seconds and fractional seconds since epoch.  For
documentation of TAI64, TAI64N, and related subjects, see
<http://cr.yp.to/proto/utctai.html>.

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

Reply via email to