Managing ServiceGuard NFS for Linux, June 2003

Installing and Configuring ServiceGuard NFS for Linux
Configuring a ServiceGuard NFS Package
Chapter 236
3. If you do not want to run the NFS monitor script:
Comment out the NFS_SERVICE_NAME and NFS_SERVICE_CMD
variables. For example:
# NFS_SERVICE_NAME[0]=nfs1.monitor
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables
are commented out, and the NFS monitor script is not run.
Creating the ServiceGuard Binary Configuration File
1. Use the cmapplyconf command to verify the content of your cluster
and package configuration and to copy the binary configuration file
to all the nodes in the cluster. In the following example, the cluster
configuration file is /usr/local/cmcluster/cluster.conf. On
your system, use the names of your own cluster configuration and
package configuration files.
# cmapplyconf -v -C /usr/local/cmcluster/cluster.conf \
-P /usr/local/cmcluster/pkg1/pkg1.conf
2. Use your favorite copy utility (for example, ftp or rcp) to copy the
package control, NFS control, and monitor scripts to the same path
names on all the nodes in the cluster. For example, to copy the files
from host thyme to host basil, issue the following command from
host thyme:
# rcp /usr/local/cmcluster/cluster.conf/pkg1/* \
basil:/usr/local/cmcluster/cluster.conf/pkg1
Housekeeping Suggestions
After the shell scripts are installed they are located in
/usr/local/cmcluster/nfstoolkit and the binary file is located in
/usr/bin on your Linux platforms. It is recommended that you set up
directories to keep your various package and script files grouped for
organization. Set up one directory for each package and keep the
associated control and monitoring scripts in that directory.