[Date Prev][Date Next]
Re: ldap_add: Internal (implementation specific) error (80)
if my rootdn is server 1 is cn=Manager,dc=k2comp and in my server 2
cn=repAdmin,dc=k2comp how can i make them update each other and do not
do an endlles update?????
Pierangelo Masarati wrote:
Joao Pereira wrote:
Shouldn't multimaster work??????
it is not guaranteed
ive compilled with --enable-multimaster.....
good it still compiles...
and would need it working like that
in any case, you cannot use the updatedn to directly write to a
multimaster. writes by the updatedn must come from the replication
agent, and they are supposed to contain the structuralObjectClass
along with other non-user modifiable data. If you write with that
identity, writes do not propagate to other masters in the pool.
Otherwise, how do you suppose a multimaster pool doesn't get into an
endless replication loop?
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497