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

# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in between.
# Maximum string length is 39 characters.
#
# Legal values for service_cmd: <Any String>
# Legal values for service_restart: none, unlimited, (value > 0).
# Legal values for service_fail_fast_enabled: yes, no.
# Legal values for service_halt_timeout: (value >= 0).
service_name app.monitor
service_cmd "/usr/local/cmcluster/conf/scripts/tkit/toolbox/tkit_module.sh toolbox_monitor"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
# The package dependency parameters are "dependency_name",
# "dependency_condition" and "dependency_location".
#
# Dependencies are used to describe the relationship between two packages.
# To define a dependency, "dependency_name" and "dependency_condition"
# are required and "dependency_location is optional.
#
# "dependency_name" must be a unique identifier for the dependency.
#
# "dependency_condition" describes what must be true for
# the dependency to be satisfied.
#
# The syntax is: <package name> = <package status>
#
# The valid values for <package status> are "up" or "down".
#
# "up" means that this package requires the package identified
# by "package_name" to be up (status reported by cmviewcl is "up").
#
# If "up" is specified, the dependency rules are as follows:
#
# * A multi-node package can depend only on another multi-
# node or system multi-node package.
#
# * A failover package whose failover_policy is
# min_package_node can depend only on a multi-node or
# system multi-node package.
#
# * A failover package whose failover_policy is
# configured_node can depend on a multi-node or system
# multi-node package, or another failover package whose
# failover_policy is configured_node.
#
# "down" means that this package requires the package
# identified by "package name" to be down (status reported by
# cmviewcl is "down"). This is known as an exclusion dependency.
#
# This means that only one of these packages can be running at
# any given time.
#
# If the "down" value is specified, the exclusion dependency must be
# mutual; that is, if pkgA depends on pkgB to be down, pkgB must
# also depend on pkgA to be down.
#
# This means that in order to create an exclusion dependency
# between two packages, you must apply both packages to the
# cluster configuration at the same time.
#
# An exclusion dependency is allowed only between failover
# packages with configured_node as failover policy, and at least one
# of the packages must specify a priority.
#
# "dependency_location"
# This describes where the condition must be satisfied.
#
# This parameter is optional. If it is not specified, the default
# value "same_node" will be used.
#
# The possible values for this attribute depend on the
# dependency condition.
#
# If an "up" dependency is specified, the possible values
# are "same_node", "any_node", and "different_node".
#
# "same_node" means the dependency must be satisifed on
# the same node.
#
# "any_node" means the dependency can be satisified on
# any node in the cluster.
#
# "different_node" means the dependency must be satisfied
# on a node other than the dependent package's node.
#
# If a "down" dependency is specified, the possible values
# are "same_node" and "all_nodes".
#
# "same_node" means the package depended on must be down on
20 MySQL Toolkit scripts