Chapter 4. Accessing DFS from an NFS Client
After a Gateway Server machine and one or more NFS clients are configured according to the instructions in “Chapter 2. Configuring Gateway Server Machines” on page 5 and “Chapter 3. Configuring NFS Clients to Access DFS” on page 13, users of the NFS clients can access data in the DFS filespace. Users can access files and directories in DFS by full /.../cellname/fs pathnames or by abbreviated pathnames that use the /: link to the DFS filespace. The following are equivalent pathnames for the file myfile in the DFS filespace of the DCE cell abc.com:
/.../abc.com/fs/myfile /:/myfile
All users have unauthenticated access to DFS. Users who have DCE accounts can authenticate to their DCE identities for authenticated access to DFS. The following subsections provide more information about these two types of access.
When accessing DFS data from a DFS client, the DFS Cache Manager caches local copies of files accessed from File Server machines. When accessing DFS data from an NFS client, NFS background I/O daemons cache local copies of files accessed via the NFS server. The caching of information by the NFS daemons can affect how quickly changes you make to data in DFS become visible to other users.
Unauthenticated Access to DFS
Unauthenticated access is provided to users who access DFS without first authenticating to DCE. For a user who does not have an account in the DCE registry database, unauthenticated access is the only available form of access. Unauthenticated access requires no preliminary steps; users simply access data in DFS from an NFS client.
Unauthenticated users receive the following permissions for objects (files and directories) in the DFS filespace:
vFor objects in
vFor objects in DCE LFS filesets, unauthenticated users receive the permissions granted by the any_other entry, if it exists, on the ACL of the object. The mask_obj entry filters permissions granted via the any_other entry.
© Copyright IBM Corp. 1989, 1999 | 17 |
