Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6206
• 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 206) to
move.
This parameter can be set for failover packages only.
priority
Assigns a priority to a failover package whose failover_policy (see
page 205) 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 206.
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.
New as of A.11.18 (for both modular and legacy packages). See “About
Package Dependencies” on page 115 for more information.
dependency_name
A unique identifier for a particular dependency (see
dependency_condition on page 207) 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 201).
IMPORTANT Restrictions on dependency names in previous Serviceguard releases
were less stringent. Packages that specify dependency_names that do not
conform to the above rules will continue to run, but if you reconfigure
them, you will need to change the dependency_name; cmcheckconf and
cmapplyconf will enforce the new rules.