Please tell me what I'm doing wrong! :) Somebody has to be doing this
properly, and it's sure not me.
What I want is simple enough, I want to know how many messages were
sent/received, etc. June 18th. That information is contained within my
"current" file, but I can find no way to report on this data using
qmailanalog, tai64n, tai64nlocal, tai64n2tai, etc.
I have a "current" log file that contains log entries that span
approximately 1 week. I can successfully use qmailanalog to view
information about the messages that were sent and logged into my "current"
file. This gives me information beginning when the log file was created and
ending at the last entry of the log file, but I don't want a report that
spans the entire week, I want one for a particular day.
It seems logical that some magic combination of the following should give me
the information that I need. (BTW, I never actually change the data in my
"current" file, I always write out to another file when converting this
data).
Convert my "current" file to a human-readable format, grep out lines with
the information I want into another file, convert that information back into
tai64n format, convert that into tai format, run matchup on the file and
then run it through the qmailanalog scripts to report on the dates I want
information on.
This does not work. If I convert tai64n files into human-readable ones,
then convert that file back into tai64n files I get bad data:
@400000003b3118d1244c4a2c 2001-05-31 09:52:32.237949500 status:
Notice that tai64n did convert the date, but also left the human-readable
date in the file.
For Charles sake, I don't want to simply look at the log files. I want a
qmailanalog-style report on a subset of the information contained within my
"current" file.
> -----Original Message-----
> From: Charles Cazabon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 20, 2001 12:39 PM
> To: Qmail Mailing List
> Subject: Re: qmailanalog
>
>
> Drew Hawn <[EMAIL PROTECTED]> wrote:
> > Thanks for the info Charles, but I'm confused. How do most
> of you folks
> > pull out information from your logs?
>
> With qmail-analog, tai64nlocal, and "less", in my case. Most
> people here
> probably use something similar.
>
> > Log files generated by qmail are unreadable/unusable in the current
> > (multilog) format.
>
> tai64n timestamps aren't supposed to be human readable.
> They're supposed to
> be easily parsable by programs. That's the whole point of
> tai64nlocal -- you
> log with tai64n timestamps, and if you want to read the log with
> human-readable timestamps, you do:
> tai64nlocal < log | pager_of_choice
>
> Don't run the logs through tai64nlocal before they hit the disk.
>
> > In order for them to make sense to me, and in order to sift them for
> > specific dates I have to convert them to human readable format.
>
> No, it's much simpler than that. A program to filter a log
> with tai64nlocal
> timestamps for particular dates is trivial; Bruce's qlogtools probably
> includes one (though I haven't checked). After you've
> filtered them, you run
> it through tai64nlocal before reading it.
>
> > Once I have removed data that is not pertinent I then have
> to change them
> > back into multilog format using tai64n, and then convert
> them into the older
> > TAI64 format that qmailanalog understands, then run them through the
> > qmailanalog scripts.
>
> Don't remove any data. What isn't pertinent? qmail-analog
> needs all of the
> various data that qmail-send logs to be able to accurately
> summarize it.
>
> Charles
> --
> --------------------------------------------------------------
> ---------
> Charles Cazabon
> <[EMAIL PROTECTED]>
> GPL'ed software available at:
> http://www.qcc.sk.ca/~charlesc/software/
> Any opinions expressed are just that -- my opinions.
> --------------------------------------------------------------
> ---------
>
