Thanks for the info and thoughts. The idea would do something like your second suggestion; run logcheck on apt logs separately, but within Debian instead of just on my system. Perhaps we could also distribute the ignore regexes across packages like logcheck itself does. Since not everyone is going to want this, probably this would be in a separate apt logcheck package. Since apt term.log collects all apt output, but doesn't collect output from apt hooks (which is often useful), unattended-upgrades-dpkg.log collects only automated apt output, but *does* collect output from apt hooks, this idea is going to require some changes to one or either of those packages so that users don't get duplicate entries. The apt/u-u tools already report errors fine, this isn't about that, but about reporting anomalous messages that aren't apt errors, like notices or warnings from maintainer scripts or apt hooks etc. The cron-apt error check is likewise not useful for this idea. PS: do you know if logcheck supports printing nearby ignored lines for context for each non-ignored log message that was printed? That would be essential for this apt log filtering because the non-ignored messages are usually produced by package maintainer scripts and the ignored nearby lines contain the name of the relevant packages. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part