On Wed, 16 Jul 2008 23:15:51 +0200 Marc Haber
wrote:
> It would help with debugging to have an option that causes logcheck to
> always look through the entire log file, ie not using logtail.
Looking at this old bug from 2008: does the -t option meet this need?
On Sat, 4 Dec 2021 15:38:15 +0100 (CET) "Timo Sigurdsson" <
public_tim...@silentcreek.de> wrote:
> I've encountered this bug on several machines after upgrading to the
latest stable release (bullseye). Could you please backport this fix to
bullseye so it can be fixed in a point release? Thank
On Wed, 10 Nov 2021 18:53:38 + "Dr. David Alan Gilbert" <
li...@treblig.org> wrote:
> Package: chkrootkit
> Version: 0.55-1+b1
> Severity: important
>
> Dear Maintainer,
> Since upgrade to bullseye I'm seeing chkrootkit warnings of the
> form:
>
> OooPS, not expected 210672 value
>
> I think
For anyone watching this bug, i believe it is closed by the enhanced diff
mode (merged in salsa (thanks Marcos!), and pending an upload):
Once the version in salsa is uploaded if If you add
DIFF_MODE="true"
to /etc/chkrootkit.conf then the cron job will filter the output to give
you stable
Thanks to Marcos a fix is merged in salsa
Hi - longtime logcheck user here (since 2004 at least).
Very keen to keep logcheck in the distribution and looking to get involved
in Debian (spare time only).
happy to submit patches etc but how should that be done - to the bts or via
salsa? will anyone review and merge things?
Is there an
6 matches
Mail list logo
