Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6292
log_level Determines the amount of information printed to stdout
when the package is validated, and to the script_log_file (see page
291) 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.
failover_policy Specifies how Serviceguard decides where to restart
the package if it fails. Can be set to configured_node or
min_package_node. The default is configured_node.
• configured_node means Serviceguard will attempt to restart the
package on the next available node in the list you provide under
node_name (see page 288).
• min_package_node means Serviceguard will restart a failed package
on whichever node in the node_name list has the fewest packages
running at the time.
This parameter can be set for failover packages only. For a package that
will depend on another package or vice versa, see also “About Package
Dependencies” on page 178.
failback_policy Specifies what action the package manager should
take when a failover package is not running on its primary node (the
first node on its node_name list) and the primary node is once again
available. Can be set to automatic or manual. The default is manual.
• manual means the package will continue to run on the current
(adoptive) node.
• automatic means Serviceguard will move the package to the
primary node as soon as that node becomes available, unless doing so
would also force a package with a higher priority (see page 293) to
move.