Andriy Galetski wrote:
That's how the syncrepl protocol is defined. If this is a problem for you, then you should not use syncrepl.Hi All !
My system is Linux with OpenLdap 2.2.23 & BDB 4.3
syncrepl type=refreshOnly scope=sub bindmethod=simple
BDB backend (provider) ==> shell backend (consumer)
Add DN witn attr ==> Add DN witn attr (Ok)
MODIFY some attr in
some DN ==> Add whole whole DN & attr (not good)
DELETE some DN ==> Do nothing !!! ( except replace: contextCSN )Hm, for simple deletes this should not happen. It is explicitly checked in the test suite (scripts/test017) and definitely works.
(it's BAD) :(
or some attr
..........
When check OpenLdap 2.3.1alpha I see the same behaviour :(
That specific problem probably still exists in the 2.2 provider. There are several cases where the 2.2 provider fails to detect changes that should be propagated to refreshOnly consumers. In the 2.3 provider, using a sessionlog should fix all of these cases. Since the provider codebase has been completely rewritten for 2.3, I don't foresee any further provider-related fixes ever showing up in 2.2.I seek through lists and find similar problem: http://www.netsys.com/openldap-software/2004/01/msg00749.html
-- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support