[Date Prev][Date Next] [Chronological] [Thread] [Top]

openldap 2.1.11



I just moved to 2.1.11 in conjunction with Berkeley 4.1.25 and, having changed
both at once, didn't know which to blame, but it appears that it may be 2.1.11.

I had:

index		objectClass						eq
index		uid							pres,eq
index		wpieduPersonUUID,wpieduPersonFlag,wpieduPersonPrivacy	pres,eq
index		wpieduPersonClass,wpieduPersonMajor			pres,eq
index		eduPersonAffiliation,eduPersonPrimaryAffiliation	pres,eq
index		cn,sn,title,ou,wpieduPersonAdvisor			pres,eq,sub
index		mailLocalAddress					eq
index		jpegPhoto,labeledURI					pres

and found I didn't get all the indices poplulated:  in particular cn.bdb is
virtually empty.  This was a clean build this morning:

-rw-------    1 root     root     65436032 Jan  7 09:39 log.0000000001
-rw-------    1 root     root       233472 Jan  7 09:39 uid.bdb
-rw-------    1 root     root        20480 Jan  7 09:39 cn.bdb
-rw-------    1 root     root       458752 Jan  7 09:39 objectClass.bdb
-rw-------    1 root     root          285 Jan  7 09:37 DB_CONFIG
-rw-------    1 root     root      1712128 Jan  7 09:37 dn2id.bdb
-rw-------    1 root     root     11304960 Jan  7 09:37 id2entry.bdb
-rw-------    1 root     root       184320 Jan  7 09:37 eduPersonAffiliation.bdb
-rw-------    1 root     root       167936 Jan  7 09:37 eduPersonPrimaryAffiliation.bdb
-rw-------    1 root     root        24576 Jan  7 09:37 jpegPhoto.bdb
-rw-------    1 root     root        45056 Jan  7 09:37 labeledURI.bdb
-rw-------    1 root     root       794624 Jan  7 09:37 ou.bdb
-rw-------    1 root     root      1314816 Jan  7 09:37 sn.bdb
-rw-------    1 root     root       651264 Jan  7 09:37 title.bdb
-rw-------    1 root     root      2846720 Jan  7 09:37 wpieduPersonAdvisor.bdb
-rw-------    1 root     root       135168 Jan  7 09:37 wpieduPersonClass.bdb
-rw-------    1 root     root        20480 Jan  7 09:37 wpieduPersonFlag.bdb
-rw-------    1 root     root       147456 Jan  7 09:37 wpieduPersonMajor.bdb
-rw-------    1 root     root         8192 Jan  7 09:37 __db.001
-rw-------    1 root     root     131080192 Jan  7 09:37 __db.002
-rw-------    1 root     root     131080192 Jan  7 09:37 __db.003
-rw-------    1 root     root       327680 Jan  7 09:37 __db.004
-rw-------    1 root     root       368640 Jan  7 09:37 __db.005
-rw-------    1 root     root        16384 Jan  7 09:37 __db.006

I flattened out the index list to one per line:

index		objectClass						eq
index		uid							pres,eq
index		wpieduPersonUUID	pres,eq
index		wpieduPersonFlag	pres,eq
index		wpieduPersonPrivacy	pres,eq
index		wpieduPersonMajor			pres,eq
index		wpieduPersonClass			pres,eq
index		eduPersonAffiliation	pres,eq
index		eduPersonPrimaryAffiliation	pres,eq
index		wpieduPersonAdvisor			pres,eq,sub
index		ou			pres,eq,sub
index		title			pres,eq,sub
index		sn			pres,eq,sub
index		cn			pres,eq,sub
index		mailLocalAddress					eq
index		labeledURI					pres
index		jpegPhoto					pres

and got the more complete list of indices.  Also, it appeared that cn was more
completely populated, too, since it now finds my name by substring, whereas it
didn't before:

-rw-------    1 root     root      2596864 Jan  7 10:09 cn.bdb
-rw-------    1 root     root         8192 Jan  7 10:09 __db.001
-rw-------    1 root     root     131080192 Jan  7 10:09 __db.002
-rw-------    1 root     root     131080192 Jan  7 10:09 __db.003
-rw-------    1 root     root       327680 Jan  7 10:09 __db.004
-rw-------    1 root     root       368640 Jan  7 10:09 __db.005
-rw-------    1 root     root        16384 Jan  7 10:09 __db.006
-rw-------    1 root     root          285 Jan  7 10:09 DB_CONFIG
-rw-------    1 root     root      1712128 Jan  7 10:09 dn2id.bdb
-rw-------    1 root     root       184320 Jan  7 10:09 eduPersonAffiliation.bdb
-rw-------    1 root     root       167936 Jan  7 10:09 eduPersonPrimaryAffiliation.bdb
-rw-------    1 root     root     11304960 Jan  7 10:09 id2entry.bdb
-rw-------    1 root     root        24576 Jan  7 10:09 jpegPhoto.bdb
-rw-------    1 root     root        45056 Jan  7 10:09 labeledURI.bdb
-rw-------    1 root     root     85458605 Jan  7 10:09 log.0000000001
-rw-------    1 root     root       458752 Jan  7 10:09 objectClass.bdb
-rw-------    1 root     root       794624 Jan  7 10:09 ou.bdb
-rw-------    1 root     root      1314816 Jan  7 10:09 sn.bdb
-rw-------    1 root     root       651264 Jan  7 10:09 title.bdb
-rw-------    1 root     root       233472 Jan  7 10:09 uid.bdb
-rw-------    1 root     root      2846720 Jan  7 10:09 wpieduPersonAdvisor.bdb
-rw-------    1 root     root       135168 Jan  7 10:09 wpieduPersonClass.bdb
-rw-------    1 root     root       147456 Jan  7 10:09 wpieduPersonMajor.bdb
-rw-------    1 root     root        20480 Jan  7 10:09 wpieduPersonPrivacy.bdb
-rw-------    1 root     root       245760 Jan  7 10:09 wpieduPersonUUID.bdb

Could there be an error in parsing the index lines of the config file?  Should
I not have been using commas in those entries anymore?