Brown Diego wrote:
Those methods are only used for replication fix up operations e.g. if you rename a child entry on one server, and at the same time add children to that same entry on another master, the replication fix up code has to be able to reconcile those two conflicting operations.Hi,Operation 1: I read there is no way of renaming a ou or an entry if it has children.Please refer: http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Creating_Directory_Entries-LDIF_Update_Statements.html#LDIF_Update_Statements-Renaming_an_Entry_Using_LDIF new RDN: ou= alumini (keep existing values) modifying RDN of entry ou=students, o=school.com <http://school.com> ldap_rename: Operation not allowed on nonleafSince the ou students has child entries in it. Operation 2: But, ldbm_modrdn.c file has the methods to rename the child entries also when their parent entry is renamed. i.e deleting the old parent DN and changing the new superior DN (new parent modified using modrdn operation).Example: moddn_rename_childrenWhen the operation 1. is not allowed how Operation 2 is possible ? What is the necessity of using methods insideldbm_modrdn.c file.
If I am not wrong, can anybody clarify my doubt. Thanks in advance, Brown Diego. ------------------------------------------------------------------------ -- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
