https://bugs.openldap.org/show_bug.cgi?id=5738
Quanah Gibson-Mount <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Quanah Gibson-Mount <[email protected]> --- Loaded up basic configuration with back-mdb and back-monitor. Initially we have: /opt/openldap25/bin/ldapsearch -LLL -x -H ldap:/// -D cn=config -b cn=monitor -w secret -b cn=backends,cn=monitor monitoredinfo dn: cn=Backends,cn=Monitor monitoredInfo: config monitoredInfo: ldif monitoredInfo: monitor monitoredInfo: mdb dn: cn=Backend 0,cn=Backends,cn=Monitor monitoredInfo: config dn: cn=Backend 1,cn=Backends,cn=Monitor monitoredInfo: ldif dn: cn=Backend 2,cn=Backends,cn=Monitor monitoredInfo: monitor dn: cn=Backend 3,cn=Backends,cn=Monitor monitoredInfo: mdb So assuming I understand the terse subject of this ITS, the expectation is that if we add a moduleload statement for a different backend (say back-ldap), then it should show up under this subtree, which currently does not happen. /opt/openldap25/bin/ldapmodify -H ldap:/// -D cn=config -w secret dn: cn=module{0},cn=config changetype: modify add: olcModuleLoad olcModuleLoad: {1}back_ldap.la modifying entry "cn=module{0},cn=config" /opt/openldap25/bin/ldapsearch -LLL -x -H ldap:/// -D cn=config -b cn=monitor -w secret -b cn=backends,cn=monitor monitoredinfo dn: cn=Backends,cn=Monitor monitoredInfo: config monitoredInfo: ldif monitoredInfo: monitor monitoredInfo: mdb dn: cn=Backend 0,cn=Backends,cn=Monitor monitoredInfo: config dn: cn=Backend 1,cn=Backends,cn=Monitor monitoredInfo: ldif dn: cn=Backend 2,cn=Backends,cn=Monitor monitoredInfo: monitor dn: cn=Backend 3,cn=Backends,cn=Monitor monitoredInfo: mdb However if I restart slapd, it's there: /opt/openldap25/bin/ldapsearch -LLL -x -H ldap:/// -D cn=config -b cn=monitor -w secret -b cn=backends,cn=monitor monitoredinfo dn: cn=Backends,cn=Monitor monitoredInfo: config monitoredInfo: ldif monitoredInfo: monitor monitoredInfo: mdb monitoredInfo: ldap dn: cn=Backend 0,cn=Backends,cn=Monitor monitoredInfo: config dn: cn=Backend 1,cn=Backends,cn=Monitor monitoredInfo: ldif dn: cn=Backend 2,cn=Backends,cn=Monitor monitoredInfo: monitor dn: cn=Backend 3,cn=Backends,cn=Monitor monitoredInfo: mdb dn: cn=Backend 4,cn=Backends,cn=Monitor monitoredInfo: ldap So I would say this bug still exists -- You are receiving this mail because: You are on the CC list for the issue.
