Le 30/03/2022 à 18:36, Viktor Dukhovni a écrit :
On Wed, Mar 30, 2022 at 06:11:33PM +0200, Michael Ströder wrote:
Or simply set in /etc/systemd/journald.conf:
[Journal]
Storage=none
ForwardToSyslog=yes
That does not fully solve the problem, since IIRC rate limits and
performance limitations still apply, perhaps somewhat improved for the
latter.
Rate limiting is out of the picture.
ForwardToSyslog and other similar journald options activate raw message
forwarding before any journald processing. This is pure socket to socket
forwarding without any processing. No rate limiting or other processing.
I've used to use rsyslog on top of journald forwarding since years on
Ubuntu on low end and high end machines with very high smtp/postfix
workloads on both without any trouble.
Systemd/journald is far from perfect, but clearly not the culprit here.
Emmanuel.
