Bug#808429: systemd: Please add logcheck rules

[Kevin Locke]

Hi Michael,

Thanks for the very fast response!

On 12/19/2015 06:24 PM, Michael Biebl wrote:
> Am 20.12.2015 um 02:11 schrieb Kevin Locke:
>> systemd currently logs many informational messages to the system log and
>> does not exclude any of these messages from logcheck, which results in
>> an overwhelming number of systemd log messages being reported.
>>
>> The logcheck maintainers recommend that packages maintain their own
>> logcheck rules.[1]
>
> Speaking for myself, as one of the systemd maintainers, I don't use and
> have never used logcheck. So it's unlikely that I'll do a proper job at
> maintaining the logcheck rules. I therefor feel uneasy to accept this
> patch and I think it would probably be better added to the logcheck
> package, where people that actually use it, maintain it.

I can understand that.  Keep in mind, the rules are just regular 
expressions which match log messages that can be ignored under normal 
conditions, so understanding the internals of logcheck is not required. 
  But without using logcheck, it's likely they will become out of date 
and result in bugs from users (which offloads the logcheck work, but 
requires more bug handling work).

I think part of the reasoning of the logcheck maintainers, other than 
reducing their own burden, is that the rules are often version-specific 
(as log messages change across versions) so putting them in the 
logcheck-database package would require matching against any possible 
version of the other packages.  Additionally, package maintainers are 
more likely to know when messages (or message formatting) changes 
significantly.

However, if you and the other systemd maintainers are uncomfortable 
including the rules in the systemd package, feel free to reassign this 
bug to the logcheck-database package.

Thanks,
Kevin