Managing HP Serviceguard for Linux Ninth Edition, April 2009

The following are example locations for a SUSE distribution:
############################## cmcluster.conf ###########################
#
# Highly Available Cluster file locations
#
# This file must not be edited
#########################################################################
SGROOT=/opt/cmcluster # SG root directory
SGCONF=/opt/cmcluster/conf # configuration files
SGSBIN=/opt/cmcluster/bin # binaries
SGLBIN=/opt/cmcluster/bin # binaries
SGLIB=/opt/cmcluster/lib # libraries
SGRUN=/opt/cmcluster/run # location of core dumps from daemons
SGAUTOSTART=/opt/cmcluster/conf/cmcluster.rc # SG Autostart file
Throughout this document, system filenames are usually given with one of these
location prefixes. Thus, references to $SGCONF/<FileName> can be resolved by
supplying the definition of the prefix that is found in this file. For example, if SGCONF
is /usr/local/cmcluster/conf, then the complete pathname for file
$SGCONF/cmclconfig would be /usr/local/cmcluster/conf/cmclconfig.
Enabling Serviceguard Command Access
To allow the creation of a Serviceguard configuration, you should complete the following
steps on all cluster nodes before running any Serviceguard commands:
1. Make sure the root user’s path includes the Serviceguard executables. This can be
done by adding the following environment variable definition to the root user’s
profile for Red Hat:
PATH=$PATH:/usr/local/cmcluster/bin
For SUSE:
PATH=$PATH:/opt/cmcluster/bin
2. Edit the /etc/man.config file to include the following line for Red Hat:
MANPATH /usr/local/cmcluster/doc/man
For SUSE:
MANPATH /opt/cmcluster/doc/man
This will allow use of the Serviceguard man pages.
3. Enable use of Serviceguard variables.
If the Serviceguard variables are not defined on your system, then include the file
/etc/cmcluster.conf in your login profile for user root:
. /etc/cmcluster.conf
You can confirm the access to the one of the variables as follows:
cd $SGCONF
148 Building an HA Cluster Configuration