>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am
23.09.2021 um 18:23 in
Nachricht <CCB081B25BAA15B3E2B491A7(a)[192.168.1.11]>:
--On Thursday, September 23, 2021 6:45 PM +0200 Michael Ströder
<michael(a)stroeder.com> wrote:
> Personally I have on my systems:
>
> In file /etc/systemd/journald.conf:
>
> [Journal]
> Storage=none
> ForwardToSyslog=yes
>
> In /etc/rsyslog.conf:
>
> $AddUnixListenSocket /dev/log
>
> And I start slapd with -d 0 and loglevel set.
As a side note, I've encountered deadlocks on RHEL7 on extremely busy
systems when journald is integrated with syslog like this. It also has a
strong negative effect on performance. Whether the deadlock is RHEL7
specific or not is unknown.
When OpenLDAP 2.6 releases, syslog (and journald) can be bypassed entirely
and a purely local log file can be used, resulting in a significant
performance increase.
Out of curiosity: When is that log file flushed (entry-based, time-based,
priority-based). It may make a difference when slapd crashes.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<
http://www.symas.com>