On 30/3/2022 8:12 μ.μ., Michael Ströder wrote:
On 3/30/22 18:36, Viktor Dukhovni wrote:
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?
It's a systemd socket unit creating a symlink:
# systemctl cat systemd-journald-dev-log.socket
[..]
[Socket]
ListenDatagram=/run/systemd/journal/dev-log
[..]
Symlinks=/dev/log
I am a bit confused (not surprisingly, as I am no expert).
In my CentOS 7,in /usr/lib/systemd/system/systemd-journald.socket I see:
[Socket]
ListenStream=/run/systemd/journal/stdout
ListenDatagram=/run/systemd/journal/socket
ListenDatagram=/dev/log
SocketMode=0666
PassCredentials=yes
PassSecurity=yes
ReceiveBuffer=8M
So, in order to achieve logging directly to syslog rather than to the
systemd journal would we remove the ListenDatagram=/dev/log entry and
leave the rest untouched?
Would this change affect only services configured to use the journal for
logging? I mean would this change affect services that are already
configured to use directly syslog?
Thanks a lot,
Nick
