Am 02.05.24 um 09:39 schrieb Richard Lewis:
lOn Mon, 29 Apr 2024, 14:19 Helge Kreutzmann, <deb...@helgefjell.de <mailto:deb...@helgefjell.de>> 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 > <richard.lewis.deb...@googlemail.com <mailto:richard.lewis.deb...@googlemail.com>> wrote: > Hi Helge. Apologies no-one has replied to this bug report for 2 years > and that this response isnt going to be what you want! Thanks for taking care of it anyhow, I noticed that it is not worth reporting improvements to logcheck proper. i hope to convince you otherwise! pleae report issues again! > debian usually doesnt add rules to filter startup messages as it tends > to add a lot of rules Indeed, startup rules are quite helpful, because then I see what was*different* during startup, i.e. if something got wrong.totally agree For servers, this is not very useful, but for workstatins it is. Btw., the current rules also deal with startup: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: imklog [0-9.]+, log source = /proc/kmsg started.$i think that practice and theory have diverged here! or possibly this is/was produced when logs are rotated.
The latest autopkgtest test for logcheck passed successfully [1], so I'm inclined to close this bug report.
If the log check rules do need an update, they should be accompanied with a corresponding autopkgtest.
As I don't use logcheck, I will have to rely on someone to contribute those changes. Ideally in the form of a MR on salsa at
https://salsa.debian.org/debian/rsyslog Regards, Michael [1] https://ci.debian.net/packages/r/rsyslog/unstable/amd64/46052568/
OpenPGP_signature.asc
Description: OpenPGP digital signature
