[Date Prev][Date Next]
Problem with replication
- To: openldap-devel@OpenLDAP.org
- Subject: Problem with replication
- From: "Roos E.W.E." <email@example.com>
- Date: Wed, 25 Oct 2000 11:49:15 +0000
- >received: from oce.nl (PC1-EROO.oce.nl [126.96.36.199]) by smtp02.oce.nl (8.9.3/8.9.3) with ESMTP id NAA22879 for <firstname.lastname@example.org>; Wed, 25 Oct 2000 13:49:15 +0200 (MET DST)
- Organization: Oce Technologies B.V.
With respect to replication I've the following question and/or remark.
This is the situation I'm dealing with. I've two LDAP servers that need
to replicate to each other. This is because each LDAP server can receive
addition, modifications and/or deletions. For that I've compliled
OpenLDAP 2.0.6 with SLAPD_MULTIMASTER defines. First question: Is that
It compiled perfectly, but found the following strange behaviour. When I
add an entry to a server, with a binddn which is the same as the
updatedn of that server, the entry was not added to the LDAP server.
This is not correct behaviour, because the entry must be added to the
LDAP server, but should not be replicated back to the originating
In my humble opinion, the addition of the entry must take place
regardless the origin (binddn) of the entry, but it should only be
replicated when the binddn of the LDAP add operation is different from
the updatedn defined in slapd.conf.
Does someone has a different opinion. Please let me now.