Re: (ITS#8977) Make IDL sizes configurable in back-mdb

[quanah@symas.com]

--On Monday, May 06, 2019 9:28 PM +0000 quanah@symas.com wrote:

To further document the issues after further testing with OpenLDAP master 
as of 6/25/2019

a) If a value for idlexp is set in a slapd.conf file that is not allowed (< 
16 or > 31), converting to cn=config using slaptest will incorrectly report 
that the target "slapd.d" directory doesn't exist, like:

/usr/local/etc/openldap# /usr/local/sbin/slaptest -f slapd.conf -F 
/tmp/slapd.d
slaptest: bad configuration directory!

ls -ld /tmp/slapd.d
drwxr-xr-x 2 root root 40 Jun 25 17:59 /tmp/slapd.d


b) If the idlexp value is corrected to be within the allowed range, the 
converted cn=config database loses the backend configuration and the idlexp 
setting:

/usr/local/sbin/slaptest -f slapd.conf -F /tmp/slapd.d
config file testing succeeded

cd /tmp/slapd.d/

find . -type f | xargs grep -i idlexp
./cn=config/cn=schema.ldif:olcAttributeTypes: ( OLcfgBkAt:12.1 NAME 
'olcBkMdbIdlExp' DESC 'Power of 2 u
./cn=config/cn=schema.ldif: onfiguration' SUP olcBackendConfig STRUCTURAL 
MAY olcBkMdbIdlExp )

No olcBackend... file exists, etc.

Suggested remedies:

a) The man page documentation be updated to note the limitations on valid 
ranges for the idlexp setting (16<=x<=31), at least for 64-bit systems.

b) slaptest provides a valid error if the idlexp setting is not within the 
valid range (as opposed to complaining the target directory does not exist, 
when in fact it does).

c) That conversion from slapd.conf to cn=config be fixed so that it works.


--Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>