Managing HP Serviceguard for Linux Ninth Edition, April 2009

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 121) for more information.
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 196).
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 201), 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 121).
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:
202 Configuring Packages and Their Services