Peter Mogensen wrote:
This of course changes the entryCSN of the root object:
Before the modification:
entryCSN: 20091202100930.380800Z#000000#001#000000
contextCSN: 20091202100930.696427Z#000000#001#000000
After the modification:
contextCSN: 20091202100930.696427Z#000000#001#000000
userPassword:: BASE64
entryCSN: 20091202101058.188515Z#000000#001#000000
modifiersName: cn=config
modifyTimestamp: 20091202101058Z
What surprises me is that contextCSN does not change.
Shouldn't contextCSn change when entryCSN of the root object changes?
Ahh.. this is of course because the above is output from slapcat and
contextCSN has not been synced to disk. ldapsearch gives the updated
contextCSN.
However, when I start server-2 the updated contextCSN is replicated to
server-2, but the entryCSN of the changed root object is NOT! and
neither is any changes.
Like this (not the same values as above):
slapcat Server-1 after modification:
contextCSN: 20091202104225.793759Z#000000#001#000000
userPassWord:: NEW_VALUE
entryCSN: 20091202104340.501585Z#000000#001#000000
ldapsearch for contextCSN on Server-1 after modification:
contextCSN: 20091202104340.501585Z#000000#001#000000
Start server-2 and slapcat:
userPassword:: OLD_VALUE
entryCSN: 20091202104225.457092Z#000000#001#000000
contextCSN: 20091202104340.501585Z#000000#001#000000
So changes made on server-1 before server-2 is started does still not
propagate to server-2.
/Peter
