[Date Prev][Date Next]
contextCSN with empty suffix
we have a customer who runs an openldap installation with an empty suffix as in
which is a potential problem when migrating to syncrepl as they do not have
an entry to store the contextCSN.
In our lab using openldap 2.4.19 we succeeded in inserting an entry with
an empty dn as follows:
This entry received the contextCSN entries and everything looks good
from what I can see:
I have no idea how ugly this hack is and am concerned this might break
with a future release when either searching for contextCSN below the suffix
is perhaps supported again or entries with an empty dn break.
I am about to advise the customer to move to a directory with an
nonempty suffix matching their root entry but would like to hear
nevertheless what you think of above.
CK Software GmbH
Christian Kratzer CK Software GmbH
Email: firstname.lastname@example.org Schwarzwaldstr. 31
Phone: +49 7452 889 135 D-71131 Jettingen
Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart
Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer