Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4112
This run script contains package run instructions and
the halt script contains package halt instructions. It is
recommended that you use the same script as both the
run and halt script. If you wish to separate the package
run instructions and package halt instructions into
separate scripts, the package configuration file allows
you to do this by naming two separate scripts.
However, under most conditions, it is simpler to use the
name of a single control script as the name of the
RUN_SCRIPT and the HALT_SCRIPT. When the package
starts, its run script is executed and passed the
parameter ‘start’; similarly, at package halt time, the
halt script is executed and passed the parameter ‘stop’
Enter the full pathname of the package control script.
(The script must reside in a directory that contains the
string “cmcluster.”) Ensure that this script is
executable.
If you choose to write separate package run and halt
scripts, be sure to include identical configuration
information (such as node names, IP addresses, etc.) in
both scripts.
RUN_SCRIPT_TIMEOUT and HALT_SCRIPT_TIMEOUT
If the script has not completed by the specified timeout
value, Serviceguard will terminate the script. Enter a
value in seconds.
The default is 0, or no timeout. The minimum is 10
seconds, but the minimum HALT_SCRIPT_TIMEOUT
value must be greater than the sum of all the Service
Halt Timeout values. The absolute maximum value is
restricted only by the UNIX parameter ULONG_MAX, for
an absolute limit of 4,294 seconds.
If the timeout is exceeded:
• Control of the package will not be transferred.
• The run or halt instructions will not be run.
• Global switching will be disabled.
• The current node will be disabled from running the
package.