Blair Noctis writes:
> Package: wnpp
> Severity: wishlist
> Owner: Blair Noctis
> X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng
>
> * Package name: lsix
> Version : 1.8.2
> Upstream Contact: b9
> * URL : https://github.com/hackerb9/lsix
> * License
Blair Noctis writes:
> Package: wnpp
> Severity: wishlist
> Owner: Blair Noctis
> X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng
>
> * Package name: lsix
> Version : 1.8.2
> Upstream Contact: b9
> * URL : https://github.com/hackerb9/lsix
> * License
Santiago Ruano Rincón writes:
> Dear Publicity, Localization and Internationalization Teams,
>
> I've added to the publicity-team/announcements repository two
> announcements, the first for Buster LTS reaching EOL, and the second for
> Bullseye moving over LTS:
>
> [Buster LTS EOL]
>
Package: sbuild
Version: 0.85.0
Severity: wishlist
X-Debbugs-Cc: richard.lewis.deb...@googlemail.com
Dear Maintainer,
sbuild is really great. I have a small feature request to make it easier to
navigate the autopkgtest options:
In sbuild.conf i use
$autopkgtest_root_args = '';
On Sun, 12 May 2024 17:01:36 +0100 Richard Lewis
wrote:
> > This bug is nearly 20 years old. (It is a shame no-one replied - the links
> > no longer work and there is not enough info recorded to action)
> >
> > Unless anyone is watching and can proivde more i
On Sat, 1 Jun 2024 at 14:21, Kiss Gabor (Bitman) wrote:
>
> On Sat, 1 Jun 2024, Richard Lewis wrote:
>
> > > does not cover log entry
> > >
> > > Jan 4 07:23:42 gatling pure-ftpd: (?@203.158.197.21) [INFO] Logout.
> > >
> > > The problem i
On Wed, 07 Dec 2011 09:39:55 -0800 andrew bezella wrote:
> Package: logcheck-database
> Version: 1.3.13
> Severity: minor
>
> in most cases whitespace is allowed in SERVICE names, but for the
> SERVICE FLAPPING ALERT it is not. using the cases where
> whitespace is allowed as a template, i made
On Thu, 05 Aug 2010 11:28:16 +0200 Albert Dengg wrote:
> please update the ignore rules for nagios:
> nagios (at least nagios3) will write two lines for each passive
> service check that it resives through nsca:
> nagios3: EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;...
> nagios3:
On Wed, 28 Jul 2010 13:52:44 +0200 Hendrik Jaeger wrote:
> Package: logcheck-database
> Severity: wishlist
> Tags: patch
>
>
> Hi,
>
> check_radius output filter:
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ check_radius: rc_avpair_gen:
> received VSA attribute with unknown Vendor-Id [[:digit:]]+$
A
On Tue, 16 Oct 2012 03:04:36 +0200 Sebastian Steinhuber
wrote:
> Package: logcheck-database
> Version: 1.3.15
> Severity: minor
> Tags: patch
>
> Dear Maintainer,
> to drop messages of the form:
>
> Oct 15 21:01:22 dds cyrus/cyr_expire[26497]: DIGEST-MD5 common mech free
>
> I added a line (#13)
On Fri, 17 Oct 2014 00:57:07 +0200 =?UTF-8?B?SsOpcsO0bWUgRHJvdWV0?=
wrote:
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ amavis\[[[:digit:]]+\]:
> \([-[:digit:]]+\) Passed (CLEAN|SPAM(MY)?)( {RelayedInbound})?,( LOCAL)?(
> \[(IPv6:)?[[:xdigit:].:]{3,39}\](:[[:xdigit:]]{0,5})?){0,2} <[^>]*> ->
>
On Tue, 02 Oct 2012 14:28:24 +0200
> With sendmail, self-signed certificates trigger a warning like:
>
> | Oct 2 13:02:07 hostname sm-mta[24652]: STARTTLS=client,
> relay=host.example., version=TLSv1/SSLv3, verify=FAIL,
> cipher=DHE-RSA-AES256-SHA, bits=256/256
>
> There is a logcheck rule for
On Wed, 06 Jul 2011 10:22:21 +0200 Wojciech Nizinski wrote:
> Please add following ignore rule for arpwatch:
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ arpwatch: short \(want 42\)$
It's a shame no-one replied since 2011,
Is there still interest in adding this rule to logcheck-database?
it looks
control: tags -1 + moreinfo
thanks
On Sat, 21 Feb 2015 14:57:15 + Andrew Gallagher wrote:
> spamd no longer suffixes "(closed before headers)" with "at /usr/sbin/spamd
> line N"
>
> Updated rule attached. This may also apply to other errors that I haven't
> been able to test yet.
It's a
control: tags -1 + moreinfo
thanks
On Wed, 26 Feb 2014 22:21:18 +0100 Gabriel Niebler
wrote:
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ hostapd: [[:alnum:]]+: STA
> ([0-9a-f]{2}:){5}[0-9a-f]{2} IEEE 802\.11: authenticated$
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ hostapd: [[:alnum:]]+: STA
control: tags -1 + moreinfo
On Wed, 29 Aug 2012 07:03:36 +0200 Sven Fischer
wrote:
> Package: logcheck
> Version: 1.3.13
> Severity: normal
>
> In ignore.d.server/imapproxy the first two lines (LOGIN and LOGOUT) for the
> regex contain double quotes. These are too much, hence the regex does not
control: tags -1 + moreinfo
thanks
On Wed, 04 Jan 2012 09:58:11 +0100 Gabor Kiss wrote:
> /etc/logcheck/ignore.d.server/pure-ftpd rule
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ pure-ftpd:
> \([._[:alnum:]-]+@[._[:alnum:]-]+\) \[INFO\] Logout\.$
>
> does not cover log entry
>
> Jan 4 07:23:42
control: tags -1 moreinfo
On Sun, 18 Dec 2011 11:11:13 + debian-b...@nospam.pz.podzone.net wrote:
> Package: logcheck
> Version: 1.2.69
>
> The inetutils-syslogd (2:1.5.dfsg.1-9) package provides a system
> logging daemon. syslogd periodically logs the following message:
>
> Dec 17 00:29:11
control: tags -1 + confirmed
On Mon, 17 Sep 2018 20:48:12 +0200 mi te wrote:
> Package: logcheck
> Version: 1.3.18
> Severity: normal
>
> Dear Maintainer,
>
> After upgrade to Stretch, get a notification from logcheck every time after
> BIND is restarted for logrotate.
> They should be added to
On Thu, 30 May 2024 at 20:43, Boyd Stephen Smith Jr.
wrote:
>
> On Thursday, May 30, 2024 12:37:49 PM CDT Richard Lewis wrote:
> > Is there still interest in updating rules for dovecot?
>
> Best I can volunteer is my current dovecot-local that is in active use.
> (Attached.)
On Tue, 23 Oct 2012 17:55:06 +0200 =?utf-8?B?TG/Dr2M=?= Minier
wrote:
> Package: logcheck
> Version: 1.3.15
> Severity: minor
> Tags: patch
>
> Hi,
>
> Got this log from time to time in System Events:
> Oct 23 13:48:16 pig2 named[28880]: success resolving
>
On Tue, 18 Sep 2012 06:00:06 +0200 Paul Muster wrote:
> Update:
>
> > (1) please change
> >
> > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: client
> > [.:[:xdigit:]]+#[[:digit:]]+: updating zone '[-._[:alnum:]]+/IN':
> > (adding an RR|deleting rrset) at '[._[:alnum:]-]+' A$
>
On Wed, 28 Jul 2010 13:49:43 +0200 Hendrik Jaeger wrote:
> Package: logcheck-database
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> We have some additional rules for bind:
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ named\[[0-9]+\]:
> (general: )?(info: )?received control channel command 'stats'$
Luca Boccassi writes:
> Here's two paragraphs, one for each change, for the release notes:
- More context and explanation would be helpful - suggestions below,
- Based on the discussion on d-devel, the tmpfs change is much less
controversial and so should be lower down.
- how do we
Luca Boccassi writes:
> Here's two paragraphs, one for each change, for the release notes:
- More context and explanation would be helpful - suggestions below,
- Based on the discussion on d-devel, the tmpfs change is much less
controversial and so should be lower down.
- how do we
On Sat, 21 Feb 2015 14:53:21 + Andrew Gallagher wrote:
> New versions of saslauthd say "pam_unix(smtp:auth)" instead of "(pam_unix)".
> New rule is:
>
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ saslauthd\[[[:digit:]]+\]:
> pam_unix\(smtp:auth\) authentication failure; logname= uid=0 euid=0
On Sun, 19 Oct 2014 14:06:02 +0100 Peter Wyss wrote:
> Package: logcheck-database
> The logcheck ignore.d.server rules for openvpn need some adjustments.
>
> The following 2 entries need to be adjusted to include [AF_INET]:
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
>
On Wed, 14 Nov 2012 03:50:07 +0100 Carlos Alberto Lopez Perez
wrote:
> Package: logcheck-database
> Hello,
>
> After deploying DMA, I found that logcheck is not filtering the typical
> notification messages of mail delivery that any mailer daemon generates.
>
> I successfully filtered all this
On Wed, 22 Dec 2021 11:08:09 +0100 Amadego wrote:
> These are a proposal for escluding lines that are not harmful:
>
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ smtpd\[[[:digit:]]+\]:
> [[:xdigit:]]{16} mta (connecting|connected|disconnected|tls ciphers=).*$
> ^\w{3} [ :[:digit:]]{11}
On Thu, 09 May 2013 14:49:29 -0700 Gerald Turner wrote:
> Gerald Turner writes:
> > Hello, there are a few commas that are out of place in one of the
> > spamassassin expressions:
>
> FYI, but is still present in logcheck-database 1.3.15 (wheezy).
(hello again)
It looks like the spamd rules
On Wed, 28 Jul 2010 13:47:53 +0200 Hendrik Jaeger wrote:
> Package: logcheck-database
> We use these rules for atftpd messages:
>
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ atftpd\[[[:digit:]]+\]:
> timeout: retrying...$ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
> atftpd\[[[:digit:]]+\]: Fetching
On Fri, 22 Mar 2019 03:41:03 +0900 Yasuhiro KIMURA wrote:
> There is following rule in ignore.d.server/postfix.
>
> ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/smtpd?\[[[:digit:]]+\]:
> ((Anonymous|Trusted|Verified) )?TLS connection established (to|from)
> [^[:space:]]+:
Hi, logcheck has several old bugs suggesting new rules for dovecot. It's a
pitty no-one replied, but let's change that now.
Unfortuntely, the patches in these bugs do not cleanly apply to the latest
version. I had a look at updating but not being a dovecot user akes it less
thn feasible
Is
On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi wrote:
> On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl
> > Please do not not ship conflicting configuration for /run/lock
> >
> > /usr/lib/tmpfiles.d/debian.conf:d /run/lock1777 root root - -
> > /usr/lib/tmpfiles.d/legacy.conf:d
On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi wrote:
> On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl
> > Please do not not ship conflicting configuration for /run/lock
> >
> > /usr/lib/tmpfiles.d/debian.conf:d /run/lock1777 root root - -
> > /usr/lib/tmpfiles.d/legacy.conf:d
control: tags -1 wontfix
control: retitle -1 remove logcheck user on purge
Tagging wontfix: debian policy is to not remove system users, since
they may still open files
On Sat, 3 Apr 2010 02:07:20 +0400 Dmitry Semyonov wrote:
> Another reason to set LC_ALL=C is grep slowness in UTF-8 locale.
> Depending on used patterns, I saw "grep -E" to be 6 times slower
> compared to C locale, and I guess this was not the worst case. The
> performance problem seems to be
On Wed, 25 Jun 2003 10:35:02 -0400 Erik Jacobson wrote:
> While looking through a few pages worth of FTP logs and other such
> things in my logcheck reports, I would think that many people might find
> the ability to have rewrite rules for logcheck. It would enable
> administrators to sift out
On Wed, 10 Oct 2012 09:24:26 -0400 CJ Fearnley wrote:
> File: /etc/logcheck/ignore.d.server/saslauthd
> The following patch fixes a bug in the regex for ignoring
> useless lines from saslauthd authentication failures
> (/etc/logcheck/ignore.d.server/saslauthd) on this Squeeze system:
>
>
On Mon, 07 Mar 2011 11:19:04 + "Benjamin M. A'Lee"
wrote:
> Various files under ignore.d.* use "[0-9.]{7,15}" to match an IPv4
> address, e.g., a connection to rsyncd. However, this does not match
> IPv6 addresses, causing spurious reports.
>
> A better regexp might be something like:
Russ Allbery writes:
> Simon McVittie writes:
>
>> I know fail2ban and logcheck do read plain-text logs (although as
>> mentioned, fail2ban already has native Journal-reading support too), and
>> I would guess that fwlogwatch, snort and xwatch probably also read the
>> logs.
>
> logcheck also
Simon McVittie writes:
> On Mon, 27 May 2024 at 03:29:53 +0100, Luca Boccassi wrote:
>> The list of affected packages according to apt-cache showpkg is not
>> that long either:
>>
>> logcheck
> However, for packages that want to read a traditional /var/log/syslog
> or similar, notably
On Tue, 14 Mar 2023 10:19:19 -0400 Simon Deziel wrote:
> On 2023-03-14 08:49, Richard Lewis wrote:
> > On Mon, 13 Mar 2023, 12:36 Simon Deziel, wrote:
> >
> >> egrep still consumes a lot of memory for me. A workaround I've been
> >> using is to add th
On Thu, 16 Jun 2011 16:38:49 +0200 Nenad Cimerman
wrote:
TLDR: some time in the last 15 years, this bug against logcheck has
been fixed, as far as i can tell
> My system is setup with non-POSIX default locale (see below), using UTF-8
> character encoding.
> This leads to many lines inside
On Sun, 19 May 2024 at 05:06, Stefanos Harhalakis wrote:
> See attached patch for matching NVMe devices too in smartd logs
Thanks - yes i'd noticed that the rules for smartd need an update and
this is on the radar - however, the
update to the names of the .state files i was not aware of!
I
On Sat, 18 May 2024 at 08:39, Shai Berger wrote:
> This morning, when chkrootkit made its daily run, I had
> in /tmp a file named: 'חברת חשמל לישראל בע"מ - חשבון דו חודשי.pdf'
> (the single quote marks on the edges are not part of the name, but
> the double quote mark in the middle is)
>
> This
Luca Boccassi writes:
> what would break where, and how to fix it? I only found autopkgtest so
> far, which uses /tmp/ in the guest and expects it to survive across
> reboots, and I have a MR up already for that. Anything else?
Perhaps whatever makes these files in /tmp? i think something to do
On Sun, 4 May 2014 22:33:23 +1000 Scott Leggett wrote:
> I just spent half an hour figuring out how to get window titles to
> reflect my session in byobu.. and I find the exact patch required is
> already here (thanks Josh).
>
> I guess this is just a +1 for patching skel.bashrc so that ssh-ing
On Fri, 06 May 2011 11:32:03 -0700 Gerald Turner wrote:
> Hello, I've seen some legitimate mails with unusual Message-Id headers
> that cause logchecks dovecot delivery rule to be bypassed.
>
> Example: … sieve: msgid=<20110422T2108.GA.(stdi.s...@fsing.rootsland.net>:
> stored mail into mailbox
On Sun, 12 May 2024 at 19:57, Marc Haber wrote:
>
> On Sun, May 12, 2024 at 06:54:59PM +0100, R Lewis wrote:
> > 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
control: tags -1 + moreinfo
thanks
On Wed, 25 Nov 2020 13:13:14 +0500 Alex Volkov wrote:
> IDK how it was in 2006 when this stupid decision was made, but nowadays
> `smartd` has all the needed filtering features in itself, in a case someone
> gets "annoyed" by attribute changes. Yeah, sure, it
control: tags -1 moreinfo
control: severity -1 wishlist
thanks
On Mon, 15 May 2017 10:42:03 +0200
> I am very happy with logcheck. It is great working and very usefull. However,
> it would be nice, if you could add a ruleset for suricata (a successor to the
> well known snort IDS), so I get
On Tue, 14 Jan 2014 13:33:25 +0100 Arne Wichmann wrote:
> There is one thing I would like to have in logcheck for quite a long time
> already:
>
> Invent a mechanism by which a pattern is only mailed (or not mailed) if
> another pattern was seen a given time before it (or also possibly after
>
On Sun, 20 Jan 2019 15:50:55 +0530 Charles Atkinson
wrote:
> Please consider introducing wildcards into the paths in the .logfiles
> configuration files. Perhaps similar to the way they are used in logrotate's
> paths.
> A use case is when using logcheck to check logs from multiple
> This bug is nearly 20 years old. (It is a shame no-one replied - the links
> no longer work and there is not enough info recorded to action)
>
> Unless anyone is watching and can proivde more info about what the issue
> is/was then i suggest we close it.
A year later: closing.
logcheck can
On Mon, 24 Aug 2009 08:36:21 -0400
=?iso-8859-1?B?RnLpZOlyaWMgQnJp6HJl?= wrote:
> On Thu, Mar 31, 2005 at 09:54:34AM -0500, Marc Sherman wrote:
> > I reported a bug on a couple clamav packages (302253, 302254) which
> > noted that in Sarge, logcheck files are supposed to be root:logcheck
> > 640,
On Wed, 16 Aug 2006 05:33:26 -0500 bingo wrote:
> It would be good if logtail supports locking.
I think we need some more information if this bug is to be action-ed.
logcheck uses logtail2 now (and syslog is not the default):so perhaps
it is not relevant after nearly 20 years (there were other
On Mon, 2 Jun 2014 10:25:40 -0700 (PDT) Chris Stromsoe wrote:
> logtail2 does not do any sanity checking on the final line of input to
> make sure that it is complete and "\n" terminated. If syslog is not set
> to flush on every write, it's possible for consecutive runs of logcheck to
> get a
On Fri, 14 Mar 2008 21:50:17 -0400 =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?= <
> When testing a checked-out copy of the rulefiles against an old log copy
> and sending the output to stdout, I still have to use sudo because
> logcheck insists on creating a lockfile. It'd be nice to provide an
> option
On Sat, 16 May 2020 17:12:42 -0700 Wade Richards wrote:
> This is regarding Debian bug #47608 "wrong charset in logcheck mail
> (charset=unknown-8bit)"
>
>
> The maintainer has closed this bug as 'wontfix', but if an end-user is
> looking for a work-around, you can add the following to your
>
On Sat, 18 Mar 2023 18:55:25 + Richard Lewis
wrote:
> On Sat, 18 Mar 2023, 15:12 Holger Levsen, wrote:
>
> > On Thu, Mar 16, 2023 at 06:00:06PM +, Holger Levsen wrote:
> > > aaah, thanks! I only checked
> > /usr/share/doc/logcheck/NEWS.Debian.gz
&
On Fri, 28 May 2010 19:04:17 +0200 Holger Levsen wrote:
> I often add logcheck ignore rules for security related events (like ssh login
> attemps. etc), cause they are too many and login is protected reasonably
> anyway.
>
> But then I would like to get summaries for some ignored patterns,
Sven Mueller writes:
> Am 07.05.2024 22:56 schrieb Richard Lewis
> :
>
> Luca Boccassi writes:
>
> > qwhat would
> > break where, and how to fix it?
>
> Another one for you to investigate: I believe apt
> source and 'apt-get
>
Luca Boccassi writes:
> On Mon, 6 May 2024 at 15:42, Richard Lewis
> wrote:
>>
>> Luca Boccassi writes:
>>
>> > Hence, I am not really looking for philosophical discussions or lists
>> > of personal preferences or hypotheticals, but for facts: w
Luca Boccassi writes:
> qwhat would
> break where, and how to fix it?
Another one for you to investigate: I believe apt source and 'apt-get
source' download and extract things into /tmp, as in the mmdebootstap
example mentioned by someone else, this will create "old" files that
could
Luca Boccassi writes:
> Hence, I am not really looking for philosophical discussions or lists
> of personal preferences or hypotheticals, but for facts: what would
> break where, and how to fix it?
cleaning /tmp or /var/tmp: users may lose files if they dont realise a
directory tmp can be
Luca Boccassi writes:
> Hence, I am not really looking for philosophical discussions or lists
> of personal preferences or hypotheticals, but for facts: what would
> break where, and how to fix it?
- tmux stores sockets in /tmp/tmux-$UID
- I think screen might use /tmp/screens
I suppose if you
Holger Levsen writes:
> I'm a bit surprised how many people seem to really rely on data in /tmp
> to survive for weeks or even months. I wonder if they backup /tmp?
I use /tmp for things that fall somewhere between "needs a backup" and
"unimportant, can be deleted whenever". I think all of the
Luca Boccassi writes:
> qwhat would
> break where, and how to fix it?
Another one for you to investigate: I believe apt source and 'apt-get
source' download and extract things into /tmp, as in the mmdebootstap
example mentioned by someone else, this will create "old" files that
could
Luca Boccassi writes:
> Hence, I am not really looking for philosophical discussions or lists
> of personal preferences or hypotheticals, but for facts: what would
> break where, and how to fix it?
- tmux stores sockets in /tmp/tmux-$UID
- I think screen might use /tmp/screens
I suppose if you
Luca Boccassi writes:
> On Mon, 6 May 2024 at 15:42, Richard Lewis
> wrote:
>>
>> Luca Boccassi writes:
>>
>> > Hence, I am not really looking for philosophical discussions or lists
>> > of personal preferences or hypotheticals, but for facts: w
Luca Boccassi writes:
> Hence, I am not really looking for philosophical discussions or lists
> of personal preferences or hypotheticals, but for facts: what would
> break where, and how to fix it?
cleaning /tmp or /var/tmp: users may lose files if they dont realise a
directory tmp can be
On Fri, 3 May 2024, 12:44 Francesco Potortì, wrote:
>
> > One cure would be to have logcheck ignore user-level messages, and only
> care about system-level ones. Is that possible?
> >
> >maybe it is possible - how do you define "system-level message"?
>
> Those created by root-owned processes,
control: close 1070436
thanks
On Sun, 5 May 2024, 19:10 Jochen Sprickerhof, wrote:
> Hi Richard,
>
> * Richard Lewis [2024-05-05 11:32]:
> >If i try and run tests that use 'unshare --net' with a
> >schroot backend they fail inside autopkgtest even though
> >this work
Package: autopkgtest
Version: 5.28
Severity: normal
X-Debbugs-Cc: richard.lewis.deb...@googlemail.com
Dear Maintainer,
If i try and run tests that use 'unshare --net' with a
schroot backend they fail inside autopkgtest even though
this works in the schroot being used.
This works fine in a
control: reassign -1 logcheck-database
thanks
(this is mostly about logcheck-database)
On Fri, 3 May 2024, 09:39 Francesco Potortì, wrote:
>
>
> Starting maybe a couple years ago, logcheck spits an amount of stuff that
> has now become unamnageable.
logcheck-database was mostly dormant sround
On Thu, 2 May 2024, 03:45 Vincent Lefevre, wrote:
> On 2024-05-01 19:05:06 +0100, Richard Lewis wrote:
> > I agree that you should be able to filter out duplicate lines. And i
> think
> > this is possible with a custom filter.
>
> Yes, but "sed" may not b
lOn Mon, 29 Apr 2024, 14:19 Helge Kreutzmann, wrote:
> Am Sat, Apr 27, 2024 at 07:11:40PM +0100 schrieb Richard Lewis:
> > On Sun, 17 Jul 2022 17:28:11 +0100 Richard Lewis
> > wrote:
>
> > Hi Helge. Apologies no-one has replied to this bug report for 2 years
> &g
On Wed, 1 May 2024, 00:57 Vincent Lefevre, wrote:
> On 2024-05-01 01:29:10 +0200, Vincent Lefevre wrote:
> > For instance, /var/log/chkrootkit/log.expected contains
> >
> > WARNING: Output from ifpromisc:
> > lo: not promisc and no packet sniffer sockets
> > : PACKET
>
On Sat, 03 Feb 2007 10:29:38 +0100 Jonas Koelker wrote:
> I (think I) want to see how many times the messages I care about are
> repeated. This means I can't ignore "last line repeated $n times"
> messages (obviously). But since those can also occur after messages
> that are ignored, I can't
Paul Gevers writes:
> Hi,
>
> [Release Team member hat on]
no hats here, but wanted to agree
> On 27-04-2024 11:48 p.m., Manny wrote:
>> As an aptitude user, I was bothered by the lack of aptitude ways of
>> doing things in the upgrade guide.
>
> I anything, I prefer the Release Notes to move
On Tue, 16 Oct 2012 03:14:20 +0200 Sebastian Steinhuber
wrote:
> Dear Maintainer,
> to drop (slightly boring) messages from the package rrdcached of the
> form:
> Oct 15 22:59:29 dds rrdcached[12045]: flushing old values
>
> I added a file named ignore.d.server/rrdcached, containing the line:
>
On Fri, 14 Sep 2007 14:06:58 +0200 martin f krafft wrote:
> also sprach Alex Prinsier [2007.09.14.1344
> +0200]:
> > Please copy over the filters from cyrus-imapd-2.2. I'm running
> > logcheck on a loghost, which doesn't run cyrus itself. There might
> > be a better alternative to copying the
Closing this bug from 2010 (14 years ago!) -- the then-maintainer
found that most of the suggestions were either already present or
should not actually be added, for various reasons.
A requested was made to resubmit as more independent bugs - if that
was done, we dont need this bug, and if not
package: logcheck-database
# think it's reasonable to add rkhunter rules - although the ones in
this bug need updates
severity 511483 normal
tags 511481 - wontfix
On Tue, 10 Aug 2010 10:28:54 +1000 Nemo wrote:
> > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
> > transmission-daemon\[[[:digit:]]+\]: Saved
> > "/var/lib/transmission-daemon/info/.*" \(bencode.c:1651\)$
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ transmission-daemon\[[0-9]+\]: .* DHT
> > announce
On Sun, 17 Jul 2022 17:28:11 +0100 Richard Lewis
wrote:
> > The pattern for rsyslogd can be improved. Please add the following
> > line:
> >
> > imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' \(fd 3\) from
> > systemd. \[v8.2206.0\]
> >
>
On Tue, 16 Jun 2009 11:27:57 -0700 Russ Allbery wrote:
> chrysn writes:
> touch /etc/default/locale will also make these go away with no behavior
> changes. In my experience, it happens on systems upgraded from older
> versions of Debian but not with new installs. I think this is more a
> bug
On Tue, 18 Aug 2009 20:24:31 -0400
=?iso-8859-1?B?RnLpZOlyaWMgQnJp6HJl?= wrote:
> On Fri, Jan 02, 2009 at 10:21:51AM +0100, Jan Evert van Grootheest wrote:
> > Package: logcheck-database
> > Version: 1.2.68
> >
> > It has now started to spam the logs with lots of
> > Jan 2 09:22:57 sisko
On Mon, 02 Aug 2010 10:29:03 +0200 Hannes von Haugwitz
wrote:
> > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ rsyslogd: \[origin
> > software="rsyslogd" swVersion="3.18.6" x-pid="[[:digit:]]+"
> > x-info="http://www.rsyslog.com"\] restart$
>
> Daemon restart messages are willingly not included in
On Tue, 23 Apr 2024, 00:12 Thorsten Glaser, wrote:
> P: openjdk-8-doc: debian-changelog-line-too-short CVEs
> [usr/share/doc/openjdk-8-doc/changelog.Debian.gz:4]
>
> The changelog in question is:
>
> * New upstream release
> * CVEs
> - CVE-2024-21011
> - CVE-2024-21085
> -
On Tue, 23 Apr 2024, 00:12 Thorsten Glaser, wrote:
> P: openjdk-8-doc: debian-changelog-line-too-short CVEs
> [usr/share/doc/openjdk-8-doc/changelog.Debian.gz:4]
>
> The changelog in question is:
>
> * New upstream release
> * CVEs
> - CVE-2024-21011
> - CVE-2024-21085
> -
On Thu, 18 Apr 2024, 23:18 Santiago Vila, wrote:
> El 18/4/24 a las 22:17, Richard Lewis escribió:
> >>> '^[a-zA-Z0-9_][a-zA-Z0-9._-]*\.sh$'
> >>
> >> Hi. I confirm that this is appropriate for what we distribute:
> >
> > What about local sc
> >'^[a-zA-Z0-9_][a-zA-Z0-9._-]*\.sh$'
>
> Hi. I confirm that this is appropriate for what we distribute:
What about local scripts added by users (which this change might
prevent loading): perhaps a NEWS.Debian entry would suffice?
On Fri, 12 Apr 2024, 19:00 Johannes Schauer Marin Rodrigues, <
jo...@debian.org> wrote:
> Hi Francesco,
>
> Quoting Francesco Poli (wintermute) (2024-04-11 00:13:51)
> >
> > sbuild --dist unstable --purge-build=never --purge-deps=never
> --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu
On Wed, 28 Feb 2024 18:37:41 +0100 Michael Biebl wrote:
> On Fri, 17 Nov 2023 14:40:05 +0100 Christoph Anton Mitterer
> wrote:
> > Package: systemd
> > Version: 255~rc2-1
> > Because of #1056135 I was downgradin systemd/udev packages to 254.5-1.
> > While apt was still running, this causes the
On Wed, 28 Feb 2024 18:37:41 +0100 Michael Biebl wrote:
> On Fri, 17 Nov 2023 14:40:05 +0100 Christoph Anton Mitterer
> wrote:
> > Package: systemd
> > Version: 255~rc2-1
> > Because of #1056135 I was downgradin systemd/udev packages to 254.5-1.
> > While apt was still running, this causes the
On Mon, 26 Feb 2024, 13:03 Michael Biebl, wrote:
> Hi
>
> On Thu, 22 Feb 2024 19:01:05 +0000 Richard Lewis
> wrote:
> > On Thu, 22 Feb 2024, 10:15 Ralf Schlatterbeck, wrote:
> >
> > > On Wed, Feb 21, 2024 at 02:52:33PM +0100, Ralf Schlatterbeck wrote:
&g
On Thu, 22 Feb 2024, 10:15 Ralf Schlatterbeck, wrote:
> On Wed, Feb 21, 2024 at 02:52:33PM +0100, Ralf Schlatterbeck wrote:
> >
> > I forgot to mention:
> > There is an upstream (rsyslog) bug-report at
> > https://github.com/rsyslog/rsyslog/issues/5332
>
> Upstream has decided that it is not a
You have my prayers. Please focus on family at this time.
My own daughter spent over a year in that Texas Children's neonatal ICU.
It is the best around and with prayers I'm sure she will pull through.
RichKJ5DOW
On Wednesday, February 21, 2024 at 07:45:56 PM CST, Scott Medbury via
1 - 100 of 685 matches
Mail list logo
