Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 203
For failover packages, yes allows Serviceguard to start the package (on
the first available node listed under node_name) on cluster start-up, and
to automatically restart it on an adoptive node if it fails. no prevents
Serviceguard from automatically starting the package, and from
restarting it on another node.
This is also referred to as package switching, and can be enabled or
disabled while the package is running, bemoans of the cmmodpkg
command.
For system multi-node packages, auto_run must be set to yes.
node_fail_fast_enabled
Can be set to yes or no. The default is no.
yes means the node on which the package is running will be halted
(reboot) if the package fails; no means Serviceguard will not halt the
system.
Setting node_fail_fast_enabled to yes prevents Serviceguard from
repeatedly trying (and failing) to start the package on the same node.
For system multi-node packages, node_fail_fast_enabled must be set
to yes.
run_script_timeout
The amount of time, in seconds, allowed for the package to start; or
no_timeout. The default is no_timeout. The maximum is 4294.
If the package does not complete its startup in the time specified by
run_script_timeout, Serviceguard will terminate it and prevent it
from switching to another node. In this case, if
node_fail_fast_enabled is set to yes, the node will be halted (reboot).
If no timeout is specified (no_timeout), Serviceguard will wait
indefinitely for the package to start.
If a timeout occurs:
• Switching will be disabled.
• The current node will be disabled from running the package.
halt_script_timeout
The amount of time, in seconds, allowed for the package to halt; or
no_timeout. The default is no_timeout. The maximum is 4294.