Red Hat Directory Server 8.0 Administrator's Guide

dn: cn=Sue Jacobs,ou=Marketing,dc=example,dc=com
changetype: modrdn
newrdn: cn=Susan Jacobs
deleteoldrdn: 1
4.2.1. A Note on Renaming Entries
The modrdn change type cannot move an entry to a completely different subtree. To move an
entry to a completely different branch, you must create a new entry in the alternative subtree
using the old entry's attributes, and then delete the old entry.
Also, for the same reasons that you cannot delete an entry if it is a branch point, you cannot
rename an entry if it has any children. Doing so would orphan the children in the tree, which is
not allowed by the LDAP protocol. For example, of the following three entries, only the last two
entries can be renamed:
ou=People,dc=example,dc=com
cn=Paula Simon,ou=People,dc=example,dc=com
cn=Jerry O'Connor,ou=People,dc=example,dc=com
The entry that identifies the People subtree can be renamed only if no other entries exist below
it.
4.3. Modifying an Entry Using LDIF
changetype: modify can add, replace, or remove attributes or attribute values in an entry.
When you specify changetype: modify, you must also provide a change operation to indicate
how the entry is to be modified. Change operations can be as follows:
•
add:attribute
Adds the specified attribute or attribute value. If the attribute type does not currently exist for
the entry, then the attribute and its corresponding value are created. If the attribute type
already exists for the entry, then the specified attribute value is added to the existing value. If
the particular attribute value already exists for the entry, then the operation fails, and the
server returns an error.
•
replace:attribute
The specified values are used to entirely replace the attribute's values. If the attribute does
not already exist, it is created. If no replacement value is specified for the attribute, the
attribute is deleted.
•
delete:attribute
Chapter 2. Creating Directory Entries
36