Am Donnerstag 10 Dezember 2009 14:22:26 schrieb ralf@openldap.org:
Update of /repo/OpenLDAP/pkg/ldap/servers/slapd
Modified Files: bconfig.c 1.404 -> 1.405
Log Message: global limits can also be set in "cn=config" (more forITS#6428)
While working on this, I learned that the global limits can either be set in the "cn=config" entry or in "olcDatabase=frontend,cn=config". Is there a special reason for this?
This seems also to be the case for some other attributes: olcSecurity, olcRestricted, olcRequires. Just to name a few.
Ralf Haferkamp wrote:
Am Donnerstag 10 Dezember 2009 14:22:26 schrieb ralf@openldap.org:
Update of /repo/OpenLDAP/pkg/ldap/servers/slapd
Modified Files: bconfig.c 1.404 -> 1.405
Log Message: global limits can also be set in "cn=config" (more forITS#6428)
While working on this, I learned that the global limits can either be set in the "cn=config" entry or in "olcDatabase=frontend,cn=config". Is there a special reason for this?
This seems also to be the case for some other attributes: olcSecurity, olcRestricted, olcRequires. Just to name a few.
Just for backward compatibility. These options were always documented as "global" but in fact are not, they are only valid for databases.
Originally, these attributes were write-only in cn=config - they would only be returned in the frontendDB entry. That seems to be broken now...