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

How the Control and Monitor Scripts Work
As with all Serviceguard packages, the control script starts and stops the NFS package
and determines how the package operates when it is available on a particular node.
The 11i v1 and 11i v2 control script (hanfs.sh) contains three sets of code that operate
depending on the parameter - start, stop, or file_lock_migration - with which
you call the script. On 11.0, there are two sets of code that you can call with the start
or stop parameter.
Starting the NFS Services
When called with the start parameter, the control script does the following:
• Activates the volume group or volume groups associated with the package.
• Mounts each file system associated with the package.
• Initiates the NFS monitor script to check periodically on the health of NFS services,
if you have configured your NFS package to use the monitor script.
• Exports each file system associated with the package so that it can later be
NFS-mounted by clients.
• Assigns a package IP address to the LAN card on the current node.
After this sequence, the NFS server is active, and clients can NFS-mount the exported
file systems associated with the package.
Starting File Lock Migration
If you call the control script with the file_lock_migration parameter after enabling
the File Lock Migration feature, the control script does the following:
• Populates the /var/statmon/sm directory with the Status Monitor entries from
the configured holding directory of the package, and subsequently removes the
entries from the holding directory.
• Kills any running copy of the NFS File Lock Recovery synchronization script.
• Halts the rpc.statd and rpc.lockd daemons to release file locks so that file
systems can be unmounted. If the server is also an NFS client, it loses the NFS file
locks obtained by client-side processes when these daemons are killed.
• Restarts the rpc.statd and rpc.lockd daemons so that these daemons can
manage file locks for other NFS packages running on the server. Restarting these
daemons also triggers a crash recovery notification event, whereby rpc.statd
sends crash notification messages to all clients listed in the /var/statmon/sm
directory.
• Starts the File Lock Migration synchronization script, which periodically copies
the /var/statmon/sm directory entries to the holding directory.
How the Control and Monitor Scripts Work 19