(ITS#3852) Monitor DB Location in config file

[bill@macallister.grass-valley.ca.us]

Full_Name: Bill MacAllister
Version: 2.2.27
OS: Fedora Core 4
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (63.204.65.11)


I noticed that if I place the "database monitor" section before any other
database specifications then a rootdse search does not return any attributes. 
If the "database monitor" section is moved to the end of the file then a rootdse
search returns the expected values.

Using the slapd.conf that is delivered with OpenDAP and adding the following as
the first database

 database monitor

 access to dn.subtree="cn=Monitor"
    by dn.exact="cn=root,dc=prideindustries,dc=com" write
    by * read

results in a rootdse search of

 $ ldapsearch -h localhost -x -b "" -s base +
 # extended LDIF
 #
 # LDAPv3
 # base <> with scope base
 # filter: (objectclass=*)
 # requesting: + 
 #

 # search result
 search: 2
 result: 0 Success

 # numResponses: 1

If the "database monitor" section is moved to the end of the slapd.conf file
then a rootdse search results in:

 $ ldapsearch -h localhost -x -b "" -s base +
 # extended LDIF
 #
 # LDAPv3
 # base <> with scope base
 # filter: (objectclass=*)
 # requesting: + 
 #

 #
 dn:
 structuralObjectClass: OpenLDAProotDSE
 namingContexts: dc=my-domain,dc=com
 monitorContext: cn=Monitor
 supportedControl: 2.16.840.1.113730.3.4.18
 supportedControl: 2.16.840.1.113730.3.4.2
 supportedControl: 1.3.6.1.4.1.4203.1.10.1
 supportedControl: 1.2.840.113556.1.4.1413
 supportedControl: 1.2.840.113556.1.4.1339
 supportedControl: 1.2.840.113556.1.4.319
 supportedControl: 1.2.826.0.1.334810.2.3
 supportedExtension: 1.3.6.1.4.1.1466.20037
 supportedExtension: 1.3.6.1.4.1.4203.1.11.1
 supportedExtension: 1.3.6.1.4.1.4203.1.11.3
 supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
 supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
 supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
 supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
 supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
 supportedLDAPVersion: 3
 supportedSASLMechanisms: CRAM-MD5
 supportedSASLMechanisms: DIGEST-MD5
 subschemaSubentry: cn=Subschema

 # search result
 search: 2
 result: 0 Success

 # numResponses: 2
 # numEntries: 1