>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am
19.08.2019 um 17:25 in
Nachricht <958015EBB469A710414E5F48(a)[192.168.1.144]>:
‑‑On Monday, August 19, 2019 12:22 PM +0200 Ulrich Windl
<Ulrich.Windl(a)rz.xn--uniregensburg-dm6g.de> wrote:
> I could imagine that either...
>
> * writing each message only once since slapd started
slapd has no clue what search filters a client uses, therefore slapd has no
knowledge of what indices may or may not be necessary without a
client
providing queries. Thus this is impossible for slapd to do.
If slapd can create such a message now, you'd only have to set a flag in
memory that remembers the message had been written already. So that would be
one bit per index per database I guess.
> * suppressing each message for a configurable time interval (like 1 hour,
> 1 day, 1 week, etc.)
So you would add a timer to slapd, which would require additional resource
overhead? What happens if slapd is restarted during that time period? etc.
All in memory, of course: After a restart, the message would be logged again
despite of the interval configured. As a restart will log messages anyway, I
don't see a problem there.
‑‑Quanah
‑‑
Quanah Gibson‑Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<
http://www.symas.com>