Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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.
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.
failover_policy
Specifies how Serviceguard decides where to start the package, or restart it 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 start the package on the
first available node in the list you provide under node_name (page 206).
• 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.
This parameter can be set for failover packages only. If this package will depend on
another package or vice versa, see also “About Package Dependencies” (page 130).
Choosing Package Modules 209