Managing Serviceguard 14th Edition, June 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 285
New as of A.11.18 (for both modular and legacy packages). See also
About Package Dependencies” on page 171.
script_log_file The full pathname of the package’s log file. The
default is $SGRUN/log/<package_name>.log. (See “Understanding
Where Files Are Located” on page 200 for more information about
Serviceguard pathnames.)
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 (see page
285) when the package is started and halted. Valid values are 0 through
5:
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 282).
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.