Managing HP Serviceguard for Linux, Tenth Edition, September 2012

restart it later if it fails. Enter no to keep Serviceguard from automatically starting
the package.
• node_fail_fast_enabled. Enter yes to cause the node to be halted (system
halt) if the package fails; otherwise enter no.
• run_script_timeout and halt_script_timeout. Enter the number of seconds
Serviceguard should wait for package startup or shutdown, respectively, to complete;
or leave the default, no_timeout. See (page 207).
• successor_halt_timeout. Used if other packages depend on this package;
see “About Package Dependencies” (page 130).
• script_log_file (page 208).
• log_level (page 209).
• failover_policy (page 209). Enter configured_node or
min_package_node. .
(This parameter can be set for failover packages only.)
• failback_policy (page 210) . Enter automatic or manual.
(This parameter can be set for failover packages only.)
• If this package will depend on another package or packages, enter values for
dependency_name, dependency_condition, dependency_location, and
optionally priority.
See “About Package Dependencies” (page 130) for more information.
NOTE: The package(s) this package depends on must already be part of the cluster
configuration by the time you validate this package (via cmcheckconf; see
“Verifying and Applying the Package Configuration” (page 230)); otherwise validation
will fail.
• To configure package weights, use the weight_name and weight_value
parameters (page 211). See “About Package Weights” (page 138) for more
information.
• Use monitored_subnet to specify a subnet to be monitored for this package. If
there are multiple subnets, repeat the parameter as many times as needed, on a
new line each time.
In a cross-subnet configuration, configure the additional
monitored_subnet_access parameter for each monitored_subnet as
necessary; see “About Cross-Subnet Failover” (page 151) for more information.
228 Configuring Packages and Their Services