Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Setting Up and Administering an HP-UX NFS Diskless Cluster
NFS Diskless Questions and Answers
Chapter 10934
As a result, NFS mount points are established for /usr, /sbin, and the
/opt directories on the client. If a subdirectory of a sharing point (a
directory specified as a share link) is a separate file system, the
file-sharing model breaks down because NFS does not propagate the
mount point.
If you set up your server so that a subdirectory of a sharing point is a
separate file system, you must export this file system (from the system
that serves it) and mount it (on the client) “by hand” (or you can use SAM
to make the subdirectory a “cluster-wide” file system).
HP does not recommend this configuration; it may cause problems when
you update from one release to the next, and possibly during other
operations.
Question: I want /usr/local to be a separate file system on my server.
Answer: This is less of a problem because:
1. HP does not deliver anything to /usr/local
2. /usr/local is not necessary for booting a system.
If /usr/local is a separate file system on a server, you can use SAM to
export it and make it a “cluster-wide” file system, mounted at
/usr/local on all the clients.
Question: I added a remote client and now I cannot manage it via SAM.
Answer: When SAM adds remote clients, the only name service propagated to
them is the /etc/hosts file. This is because any NIS and DNS
configuration found on the server is likely to be inappropriate for a
remote client on a different network. After adding a remote client, you
must set up the client’s DNS or NIS configuration “by hand”.
Question: Can I spread client swap space among many disks?
Answer: Yes. By default, clients swap to /paging in their root file system. In other
words, a given client swaps to /export/private_roots/ client /paging
on the server. But clients can also swap to other remote file systems via
NFS, or to a local disk via device swap or file system swap.