Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6204
If the package’s halt process does not complete in the time specified by
halt_script_timeout, Serviceguard will terminate the package and
prevent it from switching to another node. In this case, if
node_fail_fast_enabled (see page 203) is set to yes, the node will be
halted (reboot).
If a timeout occurs:
Switching will be disabled.
The current node will be disabled from running the package.
If a halt_script_timeout is specified, it should be greater than the sum
of all the values set for service_halt_timeout (see page 211) for this
package.
If a halt-script timeout occurs, you may need to perform manual cleanup.
See Chapter 8, “Troubleshooting Your Cluster,” on page 283.
successor_halt_timeout
Specifies how long, in seconds, Serviceguard will wait for packages that
depend on this package to halt, before halting this package. Can be 0
through 4294, or no_timeout. The default is no_timeout.
no_timeout means that Serviceguard will wait indefinitely for the
dependent packages to halt.
0 means Serviceguard will not wait for the dependent packages to
halt before halting this package.
New as of A.11.18 (for both modular and legacy packages). See also
About Package Dependencies” on page 115.
script_log_file
The full pathname of the package’s log file. The default is
$SGRUN/log/<package_name>.log. (See “Understanding the Location of
Serviceguard Files” on page 140 for more information about
Serviceguard pathnames.)
operation_sequence
Defines the order in which the scripts defined by the package’s
component modules will start up. See the package configuration file for
details.