Managing Serviceguard Seventeenth Edition, First Reprint December 2009

Kept” (page 196) for more information about Serviceguard pathnames.) See also log_level
(page 268).
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 (page 267) 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, min_package_node, or site_preferred. 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 (page 265).
• 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.
• site_preferred means Serviceguard will try all the eligible nodes on the local
SITE before failing the package over to a node on another SITE. This policy can
be configured only in a site-aware disaster-tolerant cluster, which requires
Metrocluster (additional HP software); see the documents listed under
“Cross-Subnet Configurations” (page 41) for more information.
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” (page 168).
268 Configuring Packages and Their Services