Hi,
On Thu, Mar 17, 2016 at 02:46:43PM +0100, Enrico Zini wrote:
> Would it be possible to have updates of logcheck rules for stable,
> either via backports or proposed-updates, so that it can be useful by
> default on stable systems?
I'll look after logcheck within the next weeks.
Best regards
fixed in 3b37edb, thanks
___
Logcheck-devel mailing list
Logcheck-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/logcheck-devel
Hi,
On Thu, Apr 03, 2014 at 11:31:42AM +0200, Martín Ferrari wrote:
On a similar note. I have already accumulated a few regexes to add to
postfix. In my case, I have plenty of lines for
postfix/submission/smtpd. I don't know how's postfix criteria to create
these log lines, but it seems it is
Hi,
On Wed, May 16, 2012 at 01:40:48AM +0900, Drey Tee wrote:
Sorry for bothering you, but I can't find a solution for my problem.
I installed 1.3.14 on freebsd from src, followed install instructions,
but stuck on starting because bash is installed in /usr/local/bin/bash
and not in /bin/bash
tags 712941 unreproducible moreinfo
thanks
Hello,
On Thu, Jun 20, 2013 at 07:33:51PM -0400, shiz...@vif.com wrote:
Since I upgraded to wheezy in may, logcheck reports contain only one
line:
egrep: character class syntax is [[:space:]], not [:space:]
I'm not able to reproduce this issue
# fixed in 20a68db
tags 652148 + pending
thanks
Hello,
Thanks for your contribution. I've added the rules to git[0].
Best regards
Hannes
[0]
http://anonscm.debian.org/gitweb/?p=logcheck/logcheck.git;a=commit;h=20a68dbcc687700e37fdcefdc423bdc24822f4ad
On Sat, Jul 09, 2011 at 05:00:01PM -0700, John Clements wrote:
It turns out that on my machine, amavisd-new doesn't necessarily
include a Message-ID field in its log lines. Also, it now appears
to place quarantined messages into subdirectories indexed by a single
character.
Thanks for your
On Wed, Aug 31, 2011 at 04:48:05PM +0200, Uwe Storbeck wrote:
For me these log messages contain a space at the end of the line
(snmpd version 5.4.3~dfsg-2). So this rule may need an additional
? or * at the end to work for all cases:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ snmpd\[[0-9]+\]:
On Mon, Jul 11, 2011 at 03:36:35PM +0200, Florian Mutter wrote:
Jeff Jansen bamakoj...@gmail.com Wed Jan 30 02:02:01 UTC 2008:
[...]
I found this old mail and wanted to ask, if there is any plan to
include this patch? I think there is also a little bug in the patch.
It needs to be 'ls -1
On Fri, Jul 08, 2011 at 12:24:54AM -0400, Jeremy L. Gaddis wrote:
One thing that Hannes mentioned was in response to commits 5f7da05[1]
and cf5e9d3[2] which I made to address bug #590559[3]. As he mentioned
in his email, webmin was removed from the Debian archive over five years
ago[4]. He
Hi,
Thanks for your contribution. Could you please provide some example log
lines showing the new format?
Greetings
Hannes
___
Logcheck-devel mailing list
Logcheck-devel@lists.alioth.debian.org
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
Hi,
Like Gerfried said, please file different bug reports for different
packages the next time.
Some comments about your rule suggestions:
Radosław Antoniuk wrote:
#dkimproxy
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: connect from .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
Michel Messerschmidt wrote:
On Tue, Jul 06, 2010 at 06:26:10PM -0700, Russ Allbery wrote:
I wonder if the right way of handling this would be to instead install a
logcheck rule as part of the libpam-krb5 package that looks something
like:
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
Juan Manuel Perrote wrote:
Hello my name is Juan Manuel.
I interested on install logcheck on RedHat Linux 64 bit, please can you tell
if is logcheck compatible with this operating system, and where I can
download the latest version.
You can download the latest source tarball using the source
tag 583600 +wontfix
thanks
Hi,
interesting feature request, but due to the current design of logcheck
it is not practicable. So I tag this bug as wontfix.
Greetings
Hannes
___
Logcheck-devel mailing list
Logcheck-devel@lists.alioth.debian.org
reassign 583155 amavisd-new
thanks
Hi,
amavisd-new has its own rules for logcheck. So I reassign this bug to
amavisd-new.
However the current version of amavisd-new does not contain the rules,
due to the missing taking back of changeset 7899d57341c4 (while
changeset a08df29d4ad7 has been
Didier Raboud wrote:
The /etc/logcheck/ignore.d.server/schroot fails to detect the session opened
messages that are IMHO completely normal. The attached patch solves this.
Can you please provide some sample log lines and/or a patch against the
HEAD code in the logcheck git?
Thanks
Hannes
tags 574858 +moreinfo
thanks
Bob Proulx wrote:
I believe what was intended was the following:
# Hostname either fully qualified or not.
if [ $FQDN -eq 1 ]; then
HOSTNAME=$(hostname --fqdn 2/dev/null)
else
HOSTNAME=$(hostname --short 2/dev/null)
fi
Fixed in
Applied to git, thanks for contribution.
Greetings
Hannes
Kerstin Puschke wrote:
logcheck cd's to $STATEDIR before cleaning up temp dir
Now you can run logcheck as a user who has no permissions for
/var/lib/logcheck (where logcheck used to cd to)
Signed-off-by: Kerstin Puschke
Applied to git, thanks for contribution.
Greetings
Hannes
Kerstin Puschke wrote:
Look for header.txt and footer.txt in $RULEDIR instead of hardcoded
/etc/logcheck
This makes header.txt. and footer.txt customizable even if using a
non-default rule directory.
Signed-off-by: Kerstin
tags 569843 +unreproducible +moreinfo
thanks
Mats Erik Andersson wrote:
The syslog messages for acpid when a window client connects
or disconnect all have a trailing single space at each line.
Therefore the existing two patterns in
/etc/logcheck/ignore.d.server/acpid
fail to filter out the
Michał Sawicz wrote:
I'd like to point out that currently dnsmasq (as of version 2.48, see
http://www.thekelleys.org.uk/dnsmasq/CHANGELOG) marks the log messages
with the subsystem, so currently messages from dhcp look like so:
Mar 30 17:14:24 media dnsmasq-dhcp[1420]: DHCPREQUEST(eth1)
Hi,
This message should be filtered in workstation level.
Please ensure that you use this level (set REPORTLEVEL in
/etc/logcheck/logcheck.conf to workstation) and provide feedback if
that solves your problem.
Thanks,
Hannes
___
Logcheck-devel
Michael Tautschnig m...@debian.org wrote:
Sorry for the late reply. I'm absolutely willing to submit small and useful
bits, I'm just a bit unclear about the policy. If bootup messages are
intentionally excluded, then some of the current rules should in fact be dropped
as well. Does bootup also
tags #547182 +unreproducible +moreinfo
thanks
Hi,
I tried to reproduce this in squeeze and sid with no success. The log
line contains only sudo not the full path /usr/bin/sudo. So I'm tagging
this bug as unreproducible.
Please provide more info about howto reproduce this behaviour, if its
Hi,
We prefer if package maintainers take care of the rules themselves
and they are distributed with the package to which they apply.
So if you are willing to include the rule in sslh itself it would be
great, otherwise I would include it in logcheck-database.
I've adjusted the rule to be a
Frédéric Brière fbri...@fbriere.net wrote:
Thanks for your contribution. Unfortunately, I don't think anyone has
the time to go through these 599 rules and sort out that big pile. From
a quick glance, most of these appear to be bootup messages, which are
willingly not included in
Hi,
at first we should clarify how to handle debian bug #498992.
Hannes
___
Logcheck-devel mailing list
Logcheck-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/logcheck-devel
Frédéric Brière fbri...@fbriere.net wrote:
On Thu, Aug 20, 2009 at 08:51:21PM +0300, Jari Aalto wrote:
A more appropriate default would be every 24h (once a day).
I can't speak for other people, but when I was sysadmin, I wanted to be
informed of any problems *now*, not the day after.
I
Package: logcheck-database
Version: 1.3.3
Severity: normal
Tags: patch
Hi,
the attached patch adds ignore.d.server/apcupsd to ignore messages like these
Aug 7 18:15:53 berlin apcupsd[2155]: UPS Self Test switch to battery.
Aug 7 18:16:00 berlin apcupsd[2155]: UPS Self Test completed: Battery
Package: logcheck-database
Version: 1.3.3
Severity: wishlist
Tags: patch
Hi,
the attached patch modifies ignore.d.server/kernel to also ignore
messages like this
Aug 18 20:19:51 t400 kernel: [25946.743205] EXT3-fs: mounted filesystem with
writeback data mode.
Hannes
-- System Information:
32 matches
Mail list logo