[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Q: Multiple accesslog overlays?
- To: Quanah Gibson-Mount <quanah@symas.com>
- Subject: Re: Q: Multiple accesslog overlays?
- From: Geert Hendrickx <geert@hendrickx.be>
- Date: Thu, 22 Aug 2019 15:37:21 +0200
- Cc: openldap-technical@openldap.org
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=hendrickx.be; s=geert; t=1566481041; bh=ysnPnk8rJ+8FGZtD/Vabh4qjs1mfqxlr/AaTZ1pLXwU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=POieuiJk0ovLU6tCZ/XXnG0OwCGulReb7DezVPjKacDKHpBcO+I+sglyuoJOCDgZU nMrJFE45s/k9rCm0tfCJdU+E+u2qXAj9w1ttPXBHcJdQnXL04XINhm3e4RPk8SERcs FIWLTz0Ei1dNdKt40jGtlAAYdVKxAjqgaysxERqLOnbtlNPmz1zIZuIhbvsbwrzdzp zb4jLPPSL8+73sitaxaaW8hUuLHSLffrDd+h8sz4OQJpJNJW+9XWw8mV51n3UPcn59 VqIMZI30uw8oju7muqP6bnzeaHvjCdlBSogF8tCq9QnjNNYvKJpmVa4m/soVg8ktbv yPUDB3EBRtVqg==
- In-reply-to: <95EB261DE85D6BE632FD93FB@[192.168.1.144]>
- References: <5D5A7817020000A100032F44@gwsmtp.uni-regensburg.de> <583C7259A5DA47BB10B2882B@[192.168.1.144]> <20190822111900.GA6110@vera.ghen.be> <95EB261DE85D6BE632FD93FB@[192.168.1.144]>
- User-agent: Mutt/1.12.1 (2019-06-15)
On Thu, Aug 22, 2019 at 06:32:53 -0700, Quanah Gibson-Mount wrote:
> > Turns out that writes failed by an overlay (slapo-unique in our case) are
> > only logged to the accesslog, if this overlay is defined in the config
> > BEFORE the accesslog overlay (as overlays are loaded on a stack, see topic
> > 12.18 in the admin guide). So we now put the accesslog overlay as last
> > instead of first.
>
> Hm, which is against best practices because it can cause other issues, IIRC
> (which is why it's advised to have syncprov followed by accesslog, as the
> first 2 overlays in the stack). This is something that needs redoing for
> 2.5.
What sort of issues Quanah? Do you advise to rollback?
We currently have the following order: syncprov, unique, accesslog.
Before it was: syncprov, accesslog unique.
Are these best practices you mention documented somewhere?
Geert
--
geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!