Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 291
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 289) is set to yes, the node will
be halted (HP-UX system reset).
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 299) for this
package.
If a timeout occurs:
• Switching will be disabled.
• The current node will be disabled from running the package.
If a halt-script timeout occurs, you may need to perform manual cleanup.
See “Package Control Script Hangs or Failures” in Chapter 8. See also
the note about VxVM under run_script_timeout on page 290.
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 178.
script_log_file The full pathname of the package’s log file. The
default is $SGRUN/log/<package_name>.log. (See “Learning Where
Serviceguard Files Are Kept” on page 199 for more information about
Serviceguard pathnames.) See also log_level on page 292.
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.
This parameter is not configurable; do not change the entries in the
configuration file.
New for modular packages.