[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: contextCSN

Guillaume Arteta wrote: 
Yet, when I test the script with João Alfredo, it returns me an "ok",
the entryCSN are identical.
*A restart of splapd used to resynchronize the contextcsn.*

_In contrast, for dc = XXXXXX, dc = fr. _

The contextcsn is ok, but I have errors with the entryCSN :|

cat / tmp/masterldap1.full

dn: ou = people, dc = XXXXX, dc = fr
entryCSN: 20080529153849.000000Z # 000000 # 000000 # 000

dn: ou = Users, dc = XXXXX, dc = fr
entryCSN: 20081126190244.000000Z # 000000 # 000000 # 000

####################

cat / tmp/masterldap2.full

dn: ou = people, dc = XXXXXX, dc = fr
entryCSN: 20080529153849Z # 000000 # 000000 # 00

dn: ou = Users, dc = XXXXX, dc = fr
entryCSN: 20081126190244Z # 000000 # 000000 # 00


Are not a bugg?.

No. It appears that your entries on masterldap2 were created with OpenLDAP 2.3 and haven't been changed since they were created. The values you see there are semantically equivalent to the values on masterldap1; i.e. as far as we care they are identical.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/