What I like most of this list is that I always learnt (or remember) something in few posts.
About the ServerID>0:
Sure, didn't realized that and makes total sense, as ServerID is used to generate CSN changes, so if ServerID=0 then is not writting CSNs -> not a provider.
About my setup and needs:
At the end I'm going to deploy a N-way multimaster, but while testing just wanted to ensure no "accidental" writes reach the new 'tested' member.
You solved perfectly all my concerns
Thanks much
Missatge de Quanah Gibson-Mount quanah@symas.com del dia dj., 9 d’abr. 2020 a les 17:31:
--On Thursday, April 9, 2020 6:19 PM +0200 Michael Ströder michael@stroeder.com wrote:
a) syncprov (and possibly accesslog), no serverID >1, and no syncrepl statement, it is a standalone provider
should be: serverID > 0 <=> serverID >= 1
b) syncprov (and possibly accesslog), serverID > 1, and a syncrepl statement, it is a multimaster node
should be: serverID > 0 <=> serverID >= 1
Correct, thanks. :)
Isn't mirrormode true not also needed for MMR?
Ah right, thanks. :)
I'm not really clear what you mean by "read only" in any of these cases. If you want an LDAP server that accepts no writes at all, then you shouldn't configure replication, as any writes that occur on the provider will then occur on the consumer, and additionally set the readonly configuration parameter to TRUE.
He probably wants to implement a 2-tier replication topology where applications/systems access pure consumer replicas which do not accept write operations from normal clients but only the modifications retrieved via syncrepl from providers. (At least that's how Æ-DIR is designed. ;-)
Yeah, that's my guess too, but their statements make that hard to determine. ;)
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com