Managing Serviceguard Seventeenth Edition, First Reprint December 2009

— RESOURCE_UP_VALUE
— RESOURCE_START
For more information, see “Parameters for Configuring EMS Resources” (page 167),
and the resource_ parameter descriptions (page 278).
NOTE: For legacy packages, DEFERRED resources must be specified in the package
control script.
• 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 (page 285), and “Controlling
Access to the Cluster” (page 227), 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 (page 269),
and “About Package Dependencies” (page 168).
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.
Configuring a Legacy Package 343