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.
> And make sure journald does not listen on /dev/log and your favourite
> syslog demon listens there.
I don't recall seeing a way to do that, is that configurable? If
systemd can yield the socket for direct creation by syslog-ng (which
would need to be configured take it over), that would be a plausible
solution, assuming of course that glibc actually still logs to the
socket and not some dedicated IPC mechanism that targets only systemd.
--
Viktor.