Hrm. Well I don't know what caused it in the first place, but get this... performing this set of operations fixed it altogether:
dn: uid=USERNAME,ou=students,ou=people,dc=ncsu,dc=edu changetype: modify delete: ou - replace: ou ou: B A - Physics ou: B S - Philosophy - delete: ncsucurriculumcode - replace: ncsucurriculumcode ncsucurriculumcode: PYA ncsucurriculumcode: LSL
After that, even the original method works just fine:
dn: uid=USERNAME,ou=students,ou=people,dc=ncsu,dc=edu changetype: modify replace: ou ou: B A - Physics ou: B S - Philosophy - replace: ncsucurriculumcode ncsucurriculumcode: PYA ncsucurriculumcode: LSL
I guess I can just keep an eye on it and see if this happens again, but it's not exactly confidence inspiring. =)
Daniel
--On Wednesday, January 24, 2007 1:53 PM -0500 daniel@ncsu.edu wrote:
Dooh, sorry, this was supposed to go to the list instead of you directly.
---------------------------- Original Message
Subject: Re: Bug(?) With OpenLDAP 2.3.32 From: daniel@ncsu.edu Date: Wed, January 24, 2007 1:51 pm To: "Gavin Henry" ghenry@suretecsystems.com
I'm not supplying the old attribute. This particular individual has a double major and hence the way we are using it, he has two ou's associated with him.
Works for me?
ldap-dev0:~> ldapmodify -Q -h ldap-dev0 dn: suRegID=85e49978f61311d2ae662436000baa77,cn=people,dc=stanford,dc=edu changetype: modify replace: ou ou: B A - Physics ou: B S - Philosophy
modifying entry "suRegID=85e49978f61311d2ae662436000baa77,cn=people,dc=stanford,dc=edu"
Then a second time:
ldap-dev0:~> ldapmodify -Q -h ldap-dev0 dn: suRegID=85e49978f61311d2ae662436000baa77,cn=people,dc=stanford,dc=edu changetype: modify replace: ou ou: B A - Physics ou: B S - Philosophy
modifying entry "suRegID=85e49978f61311d2ae662436000baa77,cn=people,dc=stanford,dc=edu"
so I'm not seeing it. This is with OL 2.3.32.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html