>> I use replace ops in my environment so that you can't end up with more >> than one. > > Yep, that's what I do now. The old behaviour relied upon LDAPMODIFY doing > "the right thing" i.e. "replace" was implied (don't blame me); in 2.4.7 at > least, this is no longer the case.
Well, if it were the case, it would be a terrible bug. What do you mean "replace" was implied, BTW? AFAIK you need to specify, within a ldapmodify operation, what type of modification is requested, there is no default. Please provide more info and, if it's the case, file an ITS. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: [EMAIL PROTECTED] --------------------------------------- --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
