Managing HP Serviceguard for Linux Ninth Edition, April 2009

NOTE: For modular packages, the default form for parameter names and literal
values in the package configuration file is lower case; for legacy packages the
default is upper case. There are no compatibility issues; Serviceguard is
case-insensitive as far as the parameter names are concerned.
Because this section is intended to be used primarily when you reconfiguring an
existing legacy package, we are using the legacy parameter names (in upper case)
for sake of continuity. But if you generate the configuration file using cmmakepkg
or cmgetconf, you will see the parameter names as they appear in modular
packages; see the notes below and the “Package Parameter Explanations” (page 196)
for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the failover_policy (page 201).
• FAILBACK_POLICY. For failover packages, enter the failback_policy (page 201).
• NODE_NAME. Enter the node or nodes on which the package can run; as described
under node_name (page 197).
• AUTO_RUN. Configure the package to start up automatically or manually; as
described under auto_run (page 198).
• NODE_FAIL_FAST_ENABLED. Enter the policy as described under
node_fail_fast_enabled (page 198).
• 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 199) and halt_script_timeout
(page 199).
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 204).
254 Cluster and Package Maintenance