Hi Ando. I've tested on RHEL 4/5 x86 and all seems good. I'll test on =

Windows in a little while.

Back-ported to 2.4.22 and tested in Windows. Works.

-Matt

=20 Thanks! =20 -Matt =20 On May 17, 2010, at 6:27 PM, masarati@aero.polimi.it wrote: =20

...

=20

...

Indeed, syncprov_operational() is right: it duplicates the entry =

only if

...

...

contextCSN is already present in the entry, and thus may need to be updated. What's wrong is back-bdb, which gives up when the entry =

does not

...

...

have e_private set appropriately, while it could do more to find out =

about

...

...

the entry's subordinates. This may explain why in some cases the attribute is present. This occurs whenever contextCSN is not =

already

...

...

present in the entry. I'm preparing a fix for back-bdb.

=20 Fixed in HEAD; please test. Thanks, p. =20

=20