If your vendor has properly configured your local operating system's mount command (or its equivalent), you can mount a DCE LFS fileset locally, as a file system on its File Server machine. You can access an object in a locally mounted DCE LFS fileset via a local pathname, as well as via a DCE pathname. The same ACL evaluation algorithm is used to determine your permissions in either case. However, if your local identity is different from your DCE identity, the permissions you receive when you access the object via its local pathname are those associated with your local identity, but the permissions you receive for access via the object's DCE pathname are those associated with your DCE identity. This is also true of objects in non-LFS filesets.
For example, suppose you log into the local machine as the root user and then authenticate to DCE as your DCE identity. In this case, if you access an object via its local pathname, you receive root permissions for the object; if you access the same object via its DCE pathname, you receive the permissions associated with your DCE identity.
If you log into the local machine as root without authenticating to DCE, you assume the identity of the local machine's /.../cellname/hosts/hostname/self principal for DCE access. If you access an object via its local pathname, you receive root permissions; however, if you access the object via its DCE pathname, you receive the permissions associated with the self identity of the local machine. To allow processes running as root on a machine (for example, cron jobs) to access an object via its DCE pathname, you can include an entry for the machine's self identity on the ACL of the object. The self identity can also receive permissions from a group to which it belongs or from the other_obj entry (because it is treated as an authenticated user from the local cell).