Bug#298275: [Logwatch-Devel]

Gary Allen Vollink Gary.Vollink at CorVu.com
Mon Jan 23 13:56:21 MST 2006


Willi Mann wrote:

> See
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298275;msg=20

I read the whole bug, and thread between my first and second replies to
the logwatch Email list.  That's what got prompted me to send the second
reply!  (Silly me, not reading the whole thing before writing).

> Unfortunately I've not gotten any information how the actual lines
> look like.

As I mentioned, I still get a few unsorted lines.  I can add that to the
few listed in the Debian Bug, and try to get a patch together in the
next few days.  Exim 4.60 came out since I last tweaked too, so there
may be messages from there that are not otherwise caught, so I'll see if
I can find any info in the latest Exim docs as well.

>> I still suggest adding the additional lines matches, and will be happy
>> to work on that.
>
>
> That would be nice. What would maybe make sense is to provide the
> *Option* to use the output of eximstats.

I'm not sure if this makes sense from an architecture point of view
though.  It seems that one of the [eventual] goals of the logwatch
script is to be able to allow generation of report information that's
not *just* from yesterday, but also from other (possibly arbitrary)
dates, and the eximstats program (at least my copy) will not do that.

>
> Willi

Thank you,
Gary Allen Vollink


More information about the Logwatch-Devel mailing list