Managing HP Serviceguard A.12.00.00 for Linux, June 2014

• 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 Chapter 10:
“Troubleshooting Your Cluster” (page 269).
6.1.4.11 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.
This parameter is new as of A.11.18. See also “About Package Dependencies” (page 111).
6.1.4.12 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” (page 143) for more information about
Serviceguard pathnames.) See also log_level.
6.1.4.13 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.
6.1.4.14 log_level
Determines the amount of information printed to stdout when the package is validated, and to
the script_log_file when the package is started and halted. Valid values are 0 through 5,
but you should normally use only the first two (0 or 1); the remainder (2 through 5) are intended
for use by HP Support.
• 0 - informative messages
• 1 - informative messages with slightly more detail
• 2 - messages showing logic flow
• 3 - messages showing detailed data structure information
• 4 - detailed debugging information
• 5 - function call flow
New for modular packages.
6.1.4.15 failover_policy
Specifies how Serviceguard decides where to start the package, or restart it if it fails. Can be set
to configured_node, min_package_node, site_preferred, or
site_preferred_manual. The default is configured_node.
• configured_node means Serviceguard will attempt to start the package on the first available
node in the list you provide under node_name (page 186).
• min_package_node means Serviceguard will start the package on whichever node in the
node_name list has the fewest packages running at the time.
188 Configuring Packages and Their Services