OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
Figure 20-3. Example Namespace Before and After the Append Operation
ZK− 5699A −GE
Before Append After Append
/.:/.:
/rnd/eng/rnd/eng
obj1link1 obj2 link2obj1 link1 obj2 link2
obj1 link1
/eng
20.2.2 Modifying ACLs at the Target Location
To preserve the access by principals to the merged information in the target directories,
the ACLs on the newly created objects at the target location need to match those of the
objects in the source directories. Because the directory merge command does not
recreate the source ACLs on the CDS objects at the new location, you may need to
modify the target ACLs after the merge operation. To modify these ACLs, use the
dcecp acl replace or acl modify command, depending on whether you want to replace
an entire ACL or just modify ACL entries.
20.3 Handling Errors
Most of the errors that the directory merge command encounters during its operations
are caused by the following:
• Duplicate names that are detected during the merge
• Names in the source subtree whose master clearinghouses were not reachable when
the command was executing
• Entries not created in the target location due to insufficient permissions
The following subsections explain how to recover from these errors.
20.3.1 Duplicate Names
If the full name of a CDS object entry or soft link is identical to a full name of an object
entry or soft link at the target location, the directory merge command lists these
duplicate names and stops. Duplicate names are not merged to avoid overwriting and
20 − 6 Tandem Computers Incorporated 124243