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

# "package_type" is the type of package.
#
# The package_type attribute specifies the behavior for this
# package. Legal values and their meanings are:
#
# failover package
runs on one node at a time and if a failure
# occurs it can switch to an alternate node.
#
# multi_node package
runs on multiple nodes at the same time and
# can be independently started and halted on
# individual nodes. Failures of package components such
# as services, EMS resources or subnets, will cause
# the package to be halted only on the node on which the
# failure occurred. Relocatable IP addresses cannot be
# assigned to "multi_node" packages.
#
# system_multi_node
# package runs on all cluster nodes at the same time.
# It cannot be started and halted on individual nodes.
# Both "node_fail_fast_enabled" and "auto_run"
# must be set to "yes" for this type of package. All
# "services" must have "service_fail_fast_enabled" set
# to "yes". system_multi_node packages are only
# supported for use by applications provided by
# Hewlett-Packard.
#
#
# Since "multi_node" and "system_multi_node" packages can run on more
# than one node at a time and do not failover in the event of a
# package failure, the following parameters cannot be
# specified when configuring packages of these types:
#
# failover_policy
# failback_policy
#
# Since an IP address cannot be assigned to more than one node at a
# time, relocatable IP addresses cannot be assigned to "multi_node"
# packages. If volume groups are used in a "multi_node" package,
# they must be activated in a shared mode, leaving the application
# responsible for data integrity.
#
# Shared access requires a shared volume manager.
#
# The default value for "package_type" is "failover".
#
# Legal values for package_type: failover, multi_node, system_multi_node.
package_type failover
# "node_name" specified which nodes this package can run on.
#
# Enter the names of the nodes configured to run this package, repeat
# this line for each cluster member node configured to run this package.
#
# NOTE: The order in which the nodes are specified here determines the
# order of priority when Serviceguard is deciding where to run the
# package.
#
# Example : node_name first_priority_node
# node_name second_priority_node
#
# If all nodes in the cluster can run the package, and order is not
# important, specify "node_name *".
#
# Example : node_name *
#
# Legal values for node_name:
# "*", or any node name in the cluster.
# "node name" is any string that starts and ends with an alphanumeric
# character, and contains only alphanumeric characters, dot(.), dash(-),
# or underscore(_) in between.
# Maximum name length is 39 characters.
# node_name *
# "auto_run" defines whether the package is to be started when the
# cluster is started, and if it will fail over automatically.
#
# Possible values are "yes" and "no".
# The default for "auto_run" is "yes", meaning that the package will be
# automatically started when the cluster is started, and that, in the
# event of a failure the package will be started on an adoptive node.
# If "auto_run is "no", the package is not started when the cluster
# is started, and must be started with the cmrunpkg command.
#
# "auto_run" replaces "pkg_switching_enabled".
#
# Legal values for auto_run: yes, no. auto_run yes
# "node_fail_fast_enabled" will cause the node to fail if the package fails.
#
# Possible values are "yes" and "no". The default for
# "node_fail_fast_enabled" is "no". In the event of failure, if
# "node_fail_fast_enabled" is set to "yes", Serviceguard will halt the
# node on which the package is running. All system multi-node packages
16 MySQL Toolkit scripts