Managing HP Serviceguard A.11.20.00 for Linux, June 2012

• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the package control script
(described in the next section). No default is provided. Permissions on the file and directory
should be set to rwxr-xr-x or r-xr-xr-x (755 or 555).
(Script timeouts): Enter the run_script_timeout (page 160) and halt_script_timeout
(page 161).
SCRIPT_LOG_FILE. (optional). Specify the full pathname of the file where the RUN_SCRIPT
and HALT_SCRIPT will log messages. If you do not specify a path, Serviceguard will create
a file with “.log” appended to each script path, and put the messages in that file.
• If your package has relocatable IP addresses, enter the SUBNET if you want it to be monitored
(this means the package will stop if the subnet fails).
This must be a subnet that is already specified in the cluster configuration, and it can be either
an IPv4 or an IPv6 subnet. It must not be a link-local subnet (link-local package IPs are not
allowed). See monitored_subnet (page 164).
IMPORTANT: Each subnet specified here must already be specified in the cluster configuration
file via the NETWORK_INTERFACE parameter and either the HEARTBEAT_IP or
STATIONARY_IP parameter. See “Cluster Configuration Parameters ” (page 80) for more
information.
See also “Stationary and Relocatable IP Addresses and Monitored Subnets” (page 54) and
monitored_subnet (page 164).
IMPORTANT: For cross-subnet configurations, see “Configuring Cross-Subnet Failover”
(page 216).
• If your package runs services, enter the SERVICE_NAME as described under service_name
(page 166) and values for SERVICE_FAIL_FAST_ENABLED as described under
service_fail_fast_enabled (page 167) and SERVICE_HALT_TIMEOUT as described
under service_halt_timeout (page 167). Enter a group of these three for each service.
IMPORTANT: Note that the rules for valid SERVICE_NAMEs are more restrictive as of
Serviceguard A.11.18.
• 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 user_name (page 173), and
“Controlling Access to the Cluster” (page 143), 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 163),
and “About Package Dependencies” (page 100).
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.
212 Cluster and Package Maintenance