Well, in this LDIF, the two ou: values are not contiguous. slapadd is
supposed to reorder its input to make the values contiguous, but apparently
it's not doing a good job here. In which case the entry would indeed get
loaded with two separate ou attributes.
Pretty sure this is the culprit, no need to dig any further in the database.
[EMAIL PROTECTED] wrote:
dn: uid=XXX,ou=students,ou=people,dc=ncsu,dc=edu
objectClass: person
objectClass: inetOrgPerson
objectClass: ncsuPerson
uid: XXX
cn: XXX
sn: XXX
title: Senior
ncsuTwoPartName: XXX
organizationalStatus: registered
o: NC State University
gn: XXX
initials: XXX
displayName: XXX
ncsuAltDisplayName: XXX
ncsuCampusID: XXX
ncsuClassCode: SR
ou: Physics
ncsuCurriculumCode: PY
ou: B S - Philosophy
ncsuCurriculumCode: LSL
mail: [EMAIL PROTECTED]
ncsuPrimaryEMail: [EMAIL PROTECTED]
registeredAddress: XXX
postalAddress: XXX
telephoneNumber: XXX
l: Raleigh
st: NC
postalCode: 27603
ncsuPrimaryRole: staff
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/
