Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7266
• ACCESS_CONTROL_POLICY. You can grant a non-root user
PACKAGE_ADMIN privileges for this package.
See the entries for user_name, user_host, and user_role on
page 216, and “Access Roles” on page 145, for more information.
• If the package will depend on another package, enter values for
DEPENDENCY_NAME, DEPENDENCY_CONDITION, and
DEPENDENCY_LOCATION.
For more information, see the corresponding parameter descriptions
starting on page 206, and “About Package Dependencies” on
page 115.
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, Serviceguard 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.
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
$SGCONF/pkg1/pkg1.sh
Next, customize the script; see ““Customizing the Package Control
Script” on page 267.