Andreas Hasenack schrieb:
To put the overlay into the database context does not make any difference.
It seems, I was wrong. Sorry. After I made a new change to one entry on the master and waited a bit longer, the changes were replicated to the consumer.
In the long run this replication won't work with openldap 2.3.x. See ITS#4626. You need to use one replication for each database, ignoring the glue at the provider.
I think, that's what I'm doing now.
provider: ----------- database bdb suffix ou=humans,ou=foo subordinate overlay syncprov
database bdb suffix ou=sys,ou=foo subordinate overlay syncprov
database bdb suffix ou=foo
overlay glue
consumer 1: ----------- database bdb suffix ou=humans,ou=foo subordinate
syncrepl rid=401 provider=ldap://provider type=refreshAndPersist retry="60 10 300 10 3600 10" searchbase="ou=humans,ou=foo" bindmethod=simple binddn="cn=human,ou=mgr,ou=foo" credentials=nothing updateref ldap://provider
database bdb suffix ou=foo
overlay glue
consumer 2: ----------- database bdb suffix ou=sys,ou=foo subordinate
syncrepl rid=401 provider=ldap://provider type=refreshAndPersist retry="60 10 300 10 3600 10" searchbase="ou=sys,ou=foo" bindmethod=simple binddn="cn=sys,ou=mgr,ou=foo" credentials=nothing updateref ldap://provider
database bdb suffix ou=foo
overlay glue
Is this fine (for now and 2.4)?
Hans