Le Fri, Mar 03, 2023 at 02:30:04PM +0100, Michal Politowski a écrit :
>
> I can also confirm that setting LogLevelMax=info stops the flooding.
>
It would be great to have some kind of acknowledgement by maintainers, but in
the meantime, the following procedure could be used:
# systemctl edit r
Package: rtkit
Version: 0.13-5
Followup-For: Bug #939615
I can also confirm that setting LogLevelMax=info stops the flooding.
If you don't want to override upstream by default here, then please
at least make note of it in README.Debian.
Although I would say that flooding syslog with _debug_ messag
Modifying the systemd message level, as suggested in
https://github.com/heftig/rtkit/pull/26#issuecomment-1361251871 seems to
do the trick. I think that should be shipped in the absence of upstream
movement.
rtkit cannot be silenced by changing log levels, or even by redirecting output
to /dev/null. My
/etc/systemd/system/rtkit-daemon.service.d/log.conf looks like this:
[Service]
MaxLogLevel=3
StandardOutput=null
StandardError=null
...and still rtkit writes reams of junk to the system log. Since it i
Package: rtkit
Version: 0.12-4
Severity: important
Tags: upstream
Hello,
beginning with the latest update, rtkit-daemon is filling my syslog with
near identical, informational messages like:
Sep 06 20:41:57 localhost rtkit-daemon[14050]: Supervising 17 threads of 9
processes of 1 users.
5 matches
Mail list logo
