I've noticed that if a producer is rooted at the empty suffix, searches for the rootDSE (base="", scope="base"), return an entry consisting in the rootDSE entry plus the producer's contextCSN.
I've tracked this down to backend_operational(): at some point, when the entry is almost ready, selects the database that serves the empty DN, and calls that database's be_operational() helper; here syncprov_operational() adds the contextCSN.
Is this intended? I'm asking because indeed this is the only way we can get the contextCSN for that database; searches with base="" and scope other than "base" would return the database's entries but no entry with empty dn.
p.
--On Monday, April 19, 2010 4:16 AM +0200 masarati@aero.polimi.it wrote:
I've noticed that if a producer is rooted at the empty suffix, searches for the rootDSE (base="", scope="base"), return an entry consisting in the rootDSE entry plus the producer's contextCSN.
I've tracked this down to backend_operational(): at some point, when the entry is almost ready, selects the database that serves the empty DN, and calls that database's be_operational() helper; here syncprov_operational() adds the contextCSN.
Is this intended? I'm asking because indeed this is the only way we can get the contextCSN for that database; searches with base="" and scope other than "base" would return the database's entries but no entry with empty dn.
I doubt it is intended, and it likely should behave the same as all other scenarios.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org
-
masaratiļ¼ aero.polimi.it -
Quanah Gibson-Mount