Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 215
• manual means the package will continue to run on the current 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 215) to
move.
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” on page 123.
priority
Assigns a priority to a failover package whose failover_policy (see
page 214) is configured_node. Valid values are 1 through 3000, or
no_priority. The default is no_priority. See also the dependency_
parameter descriptions, starting on page 215.
priority can be used to satisfy dependencies when a package starts, or
needs to fail over or fail back: a package with a higher priority than the
packages it depends on can force those packages to start or restart on the
node it chooses, so that its dependencies are met.
If you assign a priority, it must be unique in this cluster. A lower number
indicates a higher priority, and a numerical priority is higher than
no_priority. HP recommends assigning values in increments of 20 so
as to leave gaps in the sequence; otherwise you may have to shuffle all
the existing priorities when assigning priority to a new package.
IMPORTANT Because priority is a matter of ranking, a lower number indicates a
higher priority (20 is a higher priority than 40). A numerical priority is
higher than no_priority.
New as of A.11.18 (for both modular and legacy packages). See “About
Package Dependencies” on page 123 for more information.
dependency_name
A unique identifier for a particular dependency (see
dependency_condition on page 216) that must be met in order for
this package to run (or keep running). The length and formal restrictions
for the name are the same as for package_name (see page 209).