This bug is now fixed in commit 7122b30d
https://salsa.debian.org/ddp-team/release-notes/-/commit/7122b30dd1a483379759558faa720db7b570010c
(i dont know if the bug should be set closed/pending or if that happens later?)
Makes sense.
Just wanted to add a link to the related logcheck bug which just got
filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023755
- even if this gets fixed in logcheck, users of rsyslog need to make
the same change to all locally-written logcheck rules (and there are
probably some
Michael Biebl wrote:
> Am 07.11.22 um 23:15 schrieb RL:
>> Are both rsyslog and systemd's journal still both the default in bookworm?
>>
>> I see rsyslog is still priority: important - any plans to reduce that in
>> future releases?
>
> That's actually good point: rsyslog in bookworm has been demo
Am 07.11.22 um 23:15 schrieb RL:
Are both rsyslog and systemd's journal still both the default in bookworm?
I see rsyslog is still priority: important - any plans to reduce that in
future releases?
That's actually good point: rsyslog in bookworm has been demoted to prio
optional [1], so is no
The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.documentation as well.
Michael Biebl writes:
> The rsyslog configuration changed significantly in bookworm.
Hi, I'd potentially be happy to contribute some text for release-notes
on rsyslog.
Package: release-notes
Severity: normal
The rsyslog configuration changed significantly in bookworm.
Copying the relevant parts from the changelog:
rsyslog (8.2210.0-3) unstable; urgency=medium
* Stop splitting up mail.*
This avoids having mail related messages duplicated in mail.log and
6 matches
Mail list logo
