Serviceguard NFS Toolkit A.11.31.02, A.11.11.06, and A.11.23.05 Administrator's Guide

adoptive nodes, or use NIS to manage the passwd and group databases. For
information on configuring NIS, see the NFS Services Administrator’s Guide.
10. Create an entry for the name of the package in the DNS or NIS name resolution
files, or in /etc/hosts, so that users will mount the exported file systems from
the correct node. This entry maps the package name to the package’s relocatable
IP address.
11. Decide whether to place executables locally on each client or on the NFS server.
There are a number of trade-offs to be aware of regarding the location of executables
with Serviceguard NFS.
The advantages of keeping executables local to each client are as follows:
• No failover time. If the executables are local to the client, there is no delay if
the NFS server fails.
• Faster access to the executables than accessing them through the network.
The advantage of putting the executables on the NFS server is as follows:
• Executable management. If the executables are located in one centralized
location, the administrator must update only one copy when changes are
made.
If executables are placed on the NFS server, you need to ensure that interrupts are
handled correctly in a Serviceguard environment. The client must mount the
filesystem using the nointr option. This mount option will ensure that the
executable continues running correctly on the client after a failover of the server
occurs. For example, enter the following command on the NFS client:
mount -o nointr relocatable_ip:/usr/src /usr/src
where relocatable_ip is the IP address of the package, and /usr/src
represents the mount points of the server and the client, respectively.
Without the nointr option, if an interrupt (or a SIGKILL, SIGHUP, SIGINT,
SIGQUIT, SIGTERM, or SIGALRM signal) is sent to an executable while the NFS
server is failing over, NFS will terminate the executable. This is a standard feature
of NFS that allows interrupts such as ^C to kill a “hung” client executable if the
NFS server is down. Specifying the nointr option resolves this problem. See the
mount_nfs(1M) man page for more information.
Configuring a Serviceguard NFS Package
To configure a Serviceguard NFS package, complete the following tasks, included in
this section:
• “Copying the Template Files”
• “Editing the Control Script (nfs.cntl)”
• “Editing the NFS Control Script (hanfs.sh) ”
• “Editing the File Lock Migration Script (nfs.flm)”
Configuring a Serviceguard NFS Package 27