Managing Serviceguard Seventeenth Edition, First Reprint December 2009

NOTE: VxVM disk groups are imported at package run time and exported at
package halt time. If a package uses a large number of VxVM disk, the timeout
value must be large enough to allow all of them to finish the import or export.
NOTE: If (no_timeout is specified, and the script hangs, or takes a very long time
to complete, during the validation step (cmcheckconf (1m)), cmcheckconf will
wait 20 minutes to allow the validation to complete before giving up.
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.
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 (page 266) 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 (page 277) 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 (page 266).
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” (page 168).
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
Choosing Package Modules 267