Managing HP Serviceguard A.11.20.20 for Linux, March 2014

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”
(page 113) for more information.
6.1.4.18 dependency_name
A unique identifier for a particular dependency (see dependency_condition) that must be met
in order for this package to run (or keep running). It must be unique among this package's
dependency_names. The length and formal restrictions for the name are the same as for
package_name (page 175).
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.
Configure this parameter, along with dependency_condition and dependency_location,
and optionally priority (page 179), if this package depends on another package; for example,
if this package depends on a package named pkg2:
dependency_name pkg2dep
dependency_condition pkg2 = UP
dependency_location same_node
For more information about package dependencies, see “About Package Dependencies” (page 113).
6.1.4.19 dependency_condition
The condition that must be met for this dependency to be satisfied. As of Serviceguard A.11.18,
the only condition that can be set is that another package must be running.
The syntax is: <package_name> = UP, where <package_name> is the name of the package
depended on. The type and characteristics of the current package (the one we are configuring)
impose the following restrictions on the type of package it can depend on:
• If the current package is a multi-node package, <package_name> must identify a multi-node
or system multi-node package.
• If the current package is a failover package and its failover_policy (page 178) is
min_package_node, <package_name> must identify a multi-node or system multi-node
package.
• If the current package is a failover package and configured_node is its
failover_policy, <package_name> must identify a multi-node or system multi-node
package, or a failover package whose failover_policy is configured_node.
See also “About Package Dependencies” (page 113).
6.1.4.20 dependency_location
Specifies where the dependency_condition must be met. The only legal value is same_node.
180 Configuring Packages and Their Services