On Thu, Jan 13, 2011 at 08:44:40PM +0100, Kiss Gabor (Bitman) wrote:
> It would work this week. But I think is not robust enough.
> What if cron-apt author changes again the log format?
> IMHO searching " *" is not slower than looking for " ?".
Logcheck rules have to be as specific as possible and
> You've added " *" to the rules but as far as I can see only one
> whitespace is added. So wouldn't it be sufficient to add " ?"?
It would work this week. But I think is not robust enough.
What if cron-apt author changes again the log format?
IMHO searching " *" is not slower than looking for " ?
On Thu, Jan 13, 2011 at 05:57:25PM +0100, Kiss Gabor (Bitman) wrote:
> > I've asked you for some example log lines so I can test my rule changes
> > before committing them to the git repository. If you want you can send me
> > the log lines in private if they should contain any confidential
> > inf
Dear 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. :-)
>
> I've asked you for some example log lines so I can test my rule changes
> before committing them
On Thu, Jan 13, 2011 at 12:34:24PM +0100, Kiss Gabor (Bitman) wrote:
> > 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. :-)
I've asked you for some example log lines so I can te
> 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:
Hi,
Thanks for your contribution. Could you please provide some example log
lines showing the new format?
Greetings
Hannes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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
reassign 609649 logcheck-database
thanks
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
> 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.
Is it possible t
Hi Gabor
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.
Best regards,
// Ola
On Tue, Jan 11, 2011 at 09:28:07AM +0100, Kiss Gabor (Bitman) wrote:
> Package: cron-apt
> Version: 0.8.2
> Severity: mino
Package: cron-apt
Version: 0.8.2
Severity: minor
Some patterns in /etc/logcheck/ignore.d.server/cron-apt do not allow
whitespace between value and unit meanwhile log entries contain it:
(1804 kB, 4096 B, 14.3 MB/s etc.)
A " *" should be added to these patterns. E.g.
^\w{3} [ :[:digit:]]{11} [._[:
12 matches
Mail list logo
