HP Serviceguard Developer's Toolbox Version B.12.00.00 For HP-UX and Linux

# the same node.
#
# "all_nodes" means the package depended on must be down on
# all nodes in the cluster.
#
# NOTE:
# Within a package, you cannot specifiy more than one dependency on the
# same package. For example, pkg1 cannot have one same_node and one
# any_node dependency on pkg2.
#
# When a package requires that another package be up and the
# dependency_location is any_node or different_node, the priority of the
# the package depended on must be higher or equal to the dependent
# package and its dependents. For example, if pkg1 has a same_node
# dependency on pkg2 and pkg2 has an any_node dependency on pkg3,
# the priority of pkg3 must be higher or equal to the priority of
# pkg1 and pkg2.
#
# In a CFS cluster, the dependencies among the mount point, disk group,
# and system multi-node packages are automatically created by the commands
# that construct those packages.
#
# Example 1 : To specify a "same_node" dependency between pkg1 and pkg2:
# pkg1's ascii configuration file:
#
# dependency_name pkg2_dep
#
dependency_condition pkg2 = up
#
dependency_location same_node
#
# Example 2 : To specify a "same_node" exclusion dependency between
# pkg1 and pkg2:
#
# pkg1's ascii configuration file:
#
# dependency_name pkg2_dep
# dependency_condition pkg2 = down
# dependency_location same_node
#
# pkg2's ascii configuration file:
#
# dependency_name pkg1_dep
# dependency_condition pkg1 = down
# dependency_location same_node
#
#
# Note that pkg1 and pkg2 must be applied at the same time.
#
# Legal values for dependency_name:
# Any string that starts and ends with an alphanumeric character, and
# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in the middle.
# Maximum string length is 39 characters.
#
# Legal values for dependency_condition: <Any String>
# Legal values for dependency_location: same_node, any_node, different_node, all_nodes.
#dependency_name
#dependency_condition
#dependency_location
# The package weight parameters are the "weight_name" and "weight_value".
#
#
# These optional attributes provide additional data which the
# Serviceguard package manager uses when selecting a node on which to
# place the package. As with all attribute names, they are case
# insensitive.
#
# A package can use this mechanism to define up to four arbitrary
# weight names with corresponding values that are meant to represent
# the runtime resource consumption of the package. In the cluster
# configuration file, you configure capacity limits for the named
# weights on the cluster nodes. During package placement,
# the package manager will ensure the total value of any given named
# weight does not exceed the capacity limit configured for the node.
#
# The "weight_name" is string of up to 39 characters.
# The "weight_value" specifies a value for the named weight that
# precedes it. This is an unsigned floating point value between 0 and
# 1000000 with at most three digits after the decimal point.
#
# If "weight_name" is specified, "weight_value" must also be specified
# and "weight_name" must come first. To specifiy more than one weight,
# repeat this process.
#
# You can define weights either individually within each package
# configuration file, or by means of a default value in the
# cluster configuration file that applies to all configured
# packages (except system multi-node packages). If a particular
# weight name is defined in both the cluster and package
# configuration files, the value specified in the package
21