Logcheck devel - Jan 2011 - Bug#609649: cron-apt: Insufficient logcheck patterns

reassign 609649 logcheck-database
thanks

Hi

On Wed, Jan 12, 2011 at 05:40:35PM +0100, Kiss Gabor (Bitman)
wrote:
> > Thanks for the suggestion, but are you sure that this is actually
> > part of cron-apt? I can not find any logcheck rules in the cron-apt
> > sources.
> 
> Ooops! You are right, I missed the addressee. :-)
> File /etc/logcheck/ignore.d.server/cron-apt
> is part of logcheck-database package.
Oh, I see. I was not aware they had that. Interesting to know.
> Is it possible to redirect my bug report there or
> should I resend it?
No I will re-assign it with this email. See above.
> Thanks for your patience. :-)
No problem at all.

Best regards,

// Ola
 
> Gabor
> 
-- 
 --- Inguza Technology AB --- MSc in Information Technology ----
/  ola at inguza.com                    Annebergsslingan 37        \
|  opal at debian.org                   654 65 KARLSTAD            |
|  http://inguza.com/                Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---------------------------------------------------------------

Processing commands for control at bugs.debian.org:
> reassign 609649 logcheck-database
Bug #609649 [logcheck-database] cron-apt: Insufficient logcheck patterns
Ignoring request to reassign bug #609649 to the same
package
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
609649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609649
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

Hi,

Thanks for your contribution. Could you please provide some example log
lines showing the new format?

Greetings

Hannes

> Thanks for your contribution. Could you please provide some example log
> lines showing the new format?
It is better to send you my current regular expressions. :-)

^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: Get:[[:digit:]]+
((ht|f)tp|file)://[.[:alnum:]/_-]+ [./[:alnum:]-]+ [-[:alnum:]_+.]+
[+.:~[:alnum:]-]+ \[[.[:digit:]]+ *[kMGTPEZY]?B\]$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: Need to get [[:digit:].]+
*([kMGTPEZY]?B)(/[.[:digit:]]+ *([kMGTPEZY]?B))* of archives\.$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: After this operation,
[.[:digit:]]+ *[kMGTPEZY]?B (of additional disk space will be used|disk space
will be freed)\.$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: After unpacking [[:digit:].]+
*([kMGTPEZY]?B) (of additional disk space will be used|disk space will be
freed)\.$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: Del [-[:alnum:]_+.]+
\[[.[:digit:]]+ *[kMGTPEZY]?B\]$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ cron-apt: Fetched [[:digit:].]+
*[kMGTPEZY]?B in ((([[:digit:]]+ *d )?[[:digit:]]+ *h ?)?[[:digit:]]+ *m(in)?
?)?[[:digit:]]+s \([[:digit:].]+ *[kMGTPEZY]?B/s\)$

The matter: they allow optional spaces between value and unit.
Attention. Some log lines contain more than one measurements. E.g.
... Fetched 387 kB in 6 d 18 min (1.3 B/s)

Regards

Gabor