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 10 935
NOTE You cannot configure swap for NFS Diskless clients into their kernels;
you must do it either by running swapon from the command-line, or
through entries in the client’s /etc/fstab.
Apart from this limitation, a client has the same choices for swap as the
server.
If you want the client to swap to some other destination than /paging,
remove the swapfs entry for / in the client’s /etc/fstab.
CAUTION When default swap to /paging is disabled, the client does not have any
swap space as it begins to boot; it swaps to RAM until a swap device can
be configured from entries in its /etc/fstab. For this to work, the client
must have enough available RAM to boot to the point when the swapon
command is executed.
Swap entries for local disks or file systems are processed early in the boot
process, but NFS-based swap entries are processed at the end of the boot
process.
This means that primary swap for a client must be either the default
swap to /paging, or swap to a local device or file system. HP does not
support primary swap to a remote file system other than /paging. Use
other remote file systems only for auxiliary swap.
Question: I notice that the /.rhosts files on my server and clients allow for root
equivalence throughout the cluster. Can I remove these entries?
Answer: No. Single-point administration via SAM depends on root equivalency
throughout the cluster. If you remove client or server entries from the
/.rhosts files you will not be able to use SAM to administer the cluster.
Question: How do I “clusterize” my system?
Answer: An NFS server does not need to be “clusterized”.