[389-users] Re: Solving Naming Conflicts

2017-11-09 Thread William Brown
On Thu, 2017-11-09 at 20:26 -0600, Sergei Gerasenko wrote: > Yep, that’s a very good tutorial indeed! To answer my own question > then, since the default scope is sub and the filter is cn=replica, > the replica entry is found? Exactly! :) > > > > On Nov 9, 2017, at 5:03 PM, William Brown > >

[389-users] Re: Solving Naming Conflicts

2017-11-09 Thread Sergei Gerasenko
Yep, that’s a very good tutorial indeed! To answer my own question then, since the default scope is sub and the filter is cn=replica, the replica entry is found? > On Nov 9, 2017, at 5:03 PM, William Brown wrote: > > Hey mate, > > I think this could really help you. I wrote a series of blog

[389-users] Re: Solving Naming Conflicts

2017-11-09 Thread William Brown
On Thu, 2017-11-09 at 13:10 -0600, Sergei Gerasenko wrote: > > Not quite. When we have this scenario: > > > > M1M2 > > > > T0  Add E1 > > > > T1Add E2 > > ... > > Thank you, William.  > > > > > Also, and this is more of a general LDAP question, in the same > > > article they

[389-users] Re: Solving Naming Conflicts

2017-11-09 Thread Sergei Gerasenko
> Not quite. When we have this scenario: > > M1M2 > > T0 Add E1 > > T1Add E2 ... Thank you, William. >> Also, and this is more of a general LDAP question, in the same >> article they talk about removing dangling RUVs. They do a search >> for: >> >> dn:cn=replica,cn=dc\3Dex