I agree that i should have had much lower log level.
This is now fixed properly upstream via
https://github.com/systemd/systemd/pull/18638/files
I will try to backport that to stable series or at least drop the log
level to debug.
On Mon, 19 Oct 2020 at 15:05, Michael Biebl wrote:
>
> Am Mo.,
Am 22.10.20 um 21:45 schrieb fox:
While it may be
true that "frontends" might provide some filtering (rsyslog, plenty of
options, journalctl much less)
in COCKPIT that filtering is easy, effective and intuitive to perform
well, us greybeards don't need handholding for configure machines
While it may be
true that "frontends" might provide some filtering (rsyslog, plenty of
options, journalctl much less)
in COCKPIT that filtering is easy, effective and intuitive to perform.
___
systemd-devel mailing list
On 10/22/20 9:55 AM, Dave Howorth wrote:
On Thu, 22 Oct 2020 15:27:58 +0200
Reindl Harald wrote:
Am 22.10.20 um 12:59 schrieb Lennart Poettering:
On Do, 22.10.20 11:11, David C. Partridge
(david.partri...@perdrix.co.uk) wrote:
1) Is there any way in journald.conf to perform a
message
Am 22.10.20 um 16:55 schrieb Dave Howorth:
On Thu, 22 Oct 2020 15:27:58 +0200
Reindl Harald wrote:
Am 22.10.20 um 12:59 schrieb Lennart Poettering:
On Do, 22.10.20 11:11, David C. Partridge
(david.partri...@perdrix.co.uk) wrote:
1) Is there any way in journald.conf to perform a
On Thu, 22 Oct 2020 15:27:58 +0200
Reindl Harald wrote:
> Am 22.10.20 um 12:59 schrieb Lennart Poettering:
> > On Do, 22.10.20 11:11, David C. Partridge
> > (david.partri...@perdrix.co.uk) wrote:
> 1) Is there any way in journald.conf to perform a
> message
> >> suppression
>
Am 22.10.20 um 12:59 schrieb Lennart Poettering:
On Do, 22.10.20 11:11, David C. Partridge (david.partri...@perdrix.co.uk) wrote:
1) Is there any way in journald.conf to perform a message
suppression
similar to the one I used for syslog? If not should there be one?
No.
Does
On Do, 22.10.20 11:11, David C. Partridge (david.partri...@perdrix.co.uk) wrote:
> >>1) Is there any way in journald.conf to perform a message
> suppression
> >> similar to the one I used for syslog? If not should there be one?
>
> >No.
>
> Does that mean no there isn't and also that there
Poettering; Dimitri John Ledkov
Cc: David C. Partridge; systemd Mailing List
Subject: Re: [systemd-devel] Suppressing spam error messages in the system
journal
Am Mo., 19. Okt. 2020 um 15:56 Uhr schrieb Lennart Poettering
:
>
> > 2) Could resolved be changed so that this messag
chanism similar to that
available in rsyslogd?
David
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: 19 October 2020 14:57
To: David C. Partridge
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Suppressing spam error messages in the system
Am Mo., 19. Okt. 2020 um 15:56 Uhr schrieb Lennart Poettering
:
>
> > 2) Could resolved be changed so that this message is only emitted
> > (say) once for every 100 or 500 times that the condition is
> > detected.
>
> We actually try hard to suppress unnecessary log lines, but I think
> this
On Mo, 19.10.20 11:36, David C. Partridge (david.partri...@perdrix.co.uk) wrote:
> Hi all,
>
> system-resolved is spamming the system logs with thousands of messages:
>
> Server returned error NXDOMAIN, mitigating potential DNS violation
> DVE-2018-0001, retrying transaction with reduced
12 matches
Mail list logo
