Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7 383
Creating the Package Control Script
For legacy packages, the package control script contains all the
information necessary to run all the services in the package, monitor
them during operation, react to a failure, and halt the package when
necessary. You can use Serviceguard Manager, HP-UX commands, or a
combination of both, to create or modify the package control script.
Each package must have a separate control script, which must be
executable.
For security reasons, the control script must reside in a directory with
the string cmcluster in the path. The control script is placed in the
package directory and is given the same name as specified in the
RUN_SCRIPT and HALT_SCRIPT parameters in the package configuration
file. The package control script template contains both the run
instructions and the halt instructions for the package. You can use a
single script for both run and halt operations, or, if you wish, you can
create separate scripts.
IMPORTANT Serviceguard automatically creates the necessary control scripts when
you create the CFS/CVM (4.1 and later) multi-node or system multi-node
package. HP strongly recommends that you never edit the configuration
or control script files for these packages, although Serviceguard does not
forbid it. Create and modify the information using cfs admin
commands only.
Use cmmakepkg to create the control script, then edit the control script.
Use the following procedure to create the template for the sample
failover package pkg1.
First, generate a control script template, for example:
cmmakepkg -s /etc/cmcluster/pkg1/pkg1.sh
Next, customize the script; see “Customizing the Package Control
Script”.
Customizing the Package Control Script
You need to customize as follows. See the entries for the corresponding
modular-package parameters under “Package Parameter Explanations”
on page 287 for more discussion.