On Wed, 3 May 2000, Kins Orekhov wrote:
> > You've already run the logs through tai64nlocal. That converts the
> > TAI64 timestamp into human readable form. Don't do that. Leave the
> > multilog output alone and then run it through tai64nfrac (or
> > tai64nunix) and it will generate timestamps suitable for qmailanalog.
>
> Now, I'm really confused.
>
> Here's the path that logs go thru on my machine:
>
> qmail -> accustamp -> tailocal
accustamp ALREADY gives you timestamps suitable for qmailanalog, as
you state below.
accustamp has been superceded by multilog which gives timestamps in
tai64 format. If, AND ONLY IF, you are using multilog, THEN you need
tai64nfrac (or tai64nunix) to transform the timestamps into a format
suitable for qmailanalog.
>
> If I'm disabling tailocal, then my logs ARE suitable for qmailanalog,
> so why do I need to run my logs thru tai64nfrac if everything
> works fine in this case?
>
> And another question:
> We've been running qmail awhile, so we have a some amount of logs (with
> converted from TAI64 to Local timestamps), so my original question was how
> can I convert local timestamps to TAI64?
>
> I've wrote a small awk-script to accomplish this, but it doesn't work with
> big files on my machine (more then 440-445 lines), and I can't figure out
> why (if someone has suggestions/recommendations, please, let me know):
Why not just store the logs in there accustamp or multilog form and
convert them to localtime ONLY when you need to look at them.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
