>> 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.

I've set RateLimitInterval=0 and RateLimitBurst=0 in /etc/systemd/journald.conf

From man journald.conf (systemd 219 on CentOS 7):

RateLimitInterval=, RateLimitBurst=

Configures the rate limiting that is applied to all messages generated on
the system. If, in the time interval defined by RateLimitInterval=, more
messages than specified in RateLimitBurst= are logged by a service, all
further messages within the interval are dropped until the interval is
over. A message about the number of dropped messages is generated. This
rate limiting is applied per-service, so that two services which log do
not interfere with each other's limits. Defaults to 1000 messages in 30s.
The time specification for RateLimitInterval= may be specified in the
following units: "s", "min", "h", "ms", "us". To turn off any kind of
rate limiting, set either value to 0.


>> 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.

Just guessing: systemctl disable systemd-journald.socket

/usr/lib/systemd/system/systemd-journald.socket:
...
[Socket]
ListenStream=/run/systemd/journal/stdout
ListenDatagram=/run/systemd/journal/socket
ListenDatagram=/dev/log
...

Gerald

Reply via email to