NFS Services Administrator's Guide

Configuring and Administering NFS
Configuring and Administering an NFS Server
Chapter 228
the server. If the destination of the symbolic link does not exist on the
client, a No such file or directory message will be displayed
whenever anyone attempts access to it.
Figure 2-1 illustrates the problem of symbolic links in NFS mounts,
where the destination of the symbolic link exists on the NFS server but
might not exist on the NFS client.
Figure 2-1 Symbolic Links in NFS Mounts
Examples from /etc/exports
The following example exports the /usr/bin directory to NFS clients
cabbage, cauliflower, and broccoli. Users on client broccoli have
read/write access to the /usr/bin directory. Users on cabbage and
cauliflower have read-only access. In addition to the export options,
the HP-UX permissions for the /usr/bin directory must be set to allow
access to the world or to a group that includes the users on broccoli,
cabbage and cauliflower.
/usr/bin -access=cabbage:cauliflower:broccoli,rw=broccoli
The following example allows all NFS clients read-only access to the
directory /usr/share/man. The /usr/share/man directory must also
allow read access to NFS users (for example, with -r--r--r--
permissions).
/usr/share/man -ro
The following example exports the /var/mail directory. It allows root
access to clients sage, thyme, and basil. The root users on all other NFS
clients are considered “unknown” to the NFS server, so they are given
NFS server NFS client
/
/exports
/dir1
/file1
/nonexports
/link
/file2
/
/nfs
/dir1
/file1 /link
/file2?
symbolic link
Where is