Pierangelo Masarati writes: >> 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.
No. The LDIF format does support modifying an entry without specifying "add/delete/replace: <attribute type>". That's a part of the ldapadd/ ldapmodify format from umich ldap which was left out of the LDIF RFC. The umich ldap 3.3 manpage said: If changetype is "modify" and no "add:", "replace:", or "delete:" lines appear, the default is "replace" if the -r flag is set and "add" otherwise. According to the ldapmodify(1) manpage versions, the -r flag disappeared and became the default for changetype modify in OpenLDAP-2.1. Which makes sense, remember that "replace:" is synomymous with "add:" when the attribute does not already exist. So with ldapmodify one could then omit "replace:" and often "add:" lines. -- Hallvard --- 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.
