Managing Serviceguard 14th Edition, June 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 287
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, 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” on page 171.
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 min_package_node
is its failover_policy (see page 285), <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” on page 171.
dependency_location Specifies where the dependency_condition
(see page 287) must be met. The only legal value is same_node.