Your message dated Sat, 16 Aug 2025 13:10:48 +0100
with message-id
<caj3buorryrkycb5h+b5rm35nj0bfiaquvn1wrao+v3_xiym...@mail.gmail.com>
and subject line Re: [logcheck-database] stop filtering smartd attribute change
events
has caused the Debian Bug report #975694,
regarding [logcheck-database] stop filtering smartd attribute change events
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
975694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: logcheck-database
Version: 1.3.20
Severity: wishlist
--- Please enter the report below this line. ---
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 "can send warning mails",
but by default only in a case of attribute FAILURE, and some Old-age related
attributes NEVER fail (like Power-On Hours on WD, which counts down to 1 and
just sits happily there, never getting to "failing" 0). In such cases at least
seeing them changing (or not) is useful. Overall, it's not the place for a
*maintainer* to decide (instead of a user) which events of a third-party
package are annoying and which are not.
--- System information. ---
Architecture:
Kernel: Linux 5.8.10-bootes0-p-1000
Debian Release: 10.6
991 stable security.debian.org
991 stable ftp.fi.debian.org
990 buster-backports ftp.debian.org
99 testing ftp.fi.debian.org
99 stable-backports www.deb-multimedia.org
99 stable www.deb-multimedia.org
500 stable deb.torproject.org
500 buster ookla.bintray.com
500 buster linux.dropbox.com
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Sun, 12 May 2024 19:53:08 +0100 Richard Lewis
<[email protected]> wrote:
> On Wed, 25 Nov 2020 13:13:14 +0500 Alex Volkov <[email protected]> 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 "can send warning
> > mails",
> > but by default only in a case of attribute FAILURE, and some Old-age related
> > attributes NEVER fail (like Power-On Hours on WD, which counts down to 1 and
> > just sits happily there, never getting to "failing" 0). In such cases at
> > least
> > seeing them changing (or not) is useful. Overall, it's not the place for a
> > *maintainer* to decide (instead of a user) which events of a third-party
> > package are annoying and which are not.
>
> Following up on the above bug from 2020 -- we need more information
> here: what is the issue that you would like fixed?
> you can already (even in 2020) add or subtract any rules for logcheck
> that you like. smartd has a way to alert you to issues, but
> that is nothing to do with logcheck.
>
> in the absence of a clearer statement we would need to close this one.
A year later, closing this as there isnt enough information to make
any changes. smartd rules got updated in trixie.
If there is some issue still, please re-open with the details
--- End Message ---
