Quoting Michael Spang ([EMAIL PROTECTED]): > ldapvi uses the replace changetype to add and remove values for attributes. > This causes a race condition if the user of ldapvi changes an attribute > that was externally modified while his editor was open. > > The solution is to use 'add' and 'delete' instead of replace, as > appropriate.
That's what I thought until I got all those bug reports about ldapvi's original behaviour of using add/delete not working as intended. See #374962 for an example where OpenLDAP appears to be doing schema checks between the add and delete, rather than on the combined operation (in this example combined with an attribute type that ignores whitespace, which ldapvi is not aware of). I could make the old behaviour a configuration option... d. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
