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

#
# Another policy is "min_package_node". This policy means
# Serviceguard will select from the list of "node_name" entries the
# node, which is running fewest packages when this package needs to
# start.
#
#
# Legal values for failover_policy: configured_node, min_package_node, site_preferred. failover_policy
configured_node
# "failback_policy" is the action to take when a package is not running
# on its primary node.
#
# This policy will be used to determine what action to take when a
# package is not running on its primary node and its primary node is
# capable of running the package. The default policy is "manual". The
# "manual" policy means no attempt will be made to move the package back
# to its primary node when it is running on an adoptive node.
#
# The alternative policy is "automatic". This policy means Serviceguard
# will attempt to move the package back to its primary node as soon as
# the primary node is capable of running the package.
#
#
# Legal values for failback_policy: manual, automatic. failback_policy manual
# The "priority" parameter specifies the priority of the package.
#
# This is an optional parameter. Valid values are a number between
# 1 and 3000 or no_priority. Default is no_priority.
# A smaller number indicates higher priority. A package with a
# numerical priority has higher priority than a package with no_priority.
#
# If a number is specified, it must be unique in the cluster.
# To help assign unique priorities, HP recommends you use
# priorities in increments of 10. This will allow you
# to add new packages without having to reassign priorities.
#
# Multi-node and System multi-node package cannot be assigned a priority.
#
# This parameter is used only when a weight has been defined for a package,
# a package depends on other packages,
# or other packages depend on this package, but can be specified even
# when no weights or dependencies have yet been configured.
# If priority is not configured, the package is assigned the default
# priority value, no_priority.
#
# Serviceguard gives preference to running the higher priority package.
# This means that, if necessary, Serviceguard will halt a package (or
# halt and restart on anther node) in order to run a higher priority
# package. The reason may be:
# * the node's capacity would otherwise be exceeded
# * there is a direct or indirect dependency between the lower and
# higher priority packages.
#
# For example, suppose package pkg1 depends on package pkg2 to
# be up on the same node, both have package switching enabled
# and both are currently up on node node1. If pkg1 needs to
# fail over to node2, it will also need pkg2 to move to node2.
# If pkg1 has higher priority than pkg2, it can force pkg2 to
# move to node2. Otherwise, pkg1 cannot fail over because pkg2 is
# running on node1.
# The following is are examples of package priorities and failover results:
#
# pkg1 priority pkg2 priority results
# 10 20 pkg1 is higher; fails over
# 20 10 pkg1 is lower; will not fail over
# any number no_priority pkg1 is higher; fails over
# no_priority no_priority equal priority; will not fail over
# no_priority any number pkg1 is lower; will not fail over
#
# Legal values for priority: no_priority, ( (value >= 1) && (value <= 3000) ).
priority no_priority
# ***********************APP TOOLKIT PARAMETERS******************
#
# This directory holds the toolkit configuration file.To put toolkit into
# maintenance mode, create toolbox.debug under this directory.
#
# Legal values for tkit/toolbox/toolbox/TKIT_CONF_DIR:<Any String>
tkit/toolbox/toolbox/TKIT_CONF_DIR /usr/local/cmcluster/mysql
# Maintenance flag is used to bring this toolkit into maintenance mode.If set to
# "yes" then this will enable maintenance feature in the toolkit. App Toolkit will
# look out for a file "toolbox.debug" in the TKIT_CONF_DIR directory where all the
# application toolkit files reside.If the file exists, monitoring is paused.
#
# Application can be brought down for maintenance and package would not be failed
# over to the adoptive node eventhough application instance has been brought down
# for maintenance.
#
# After the maintenance work, it is the user's responsibility
# to make sure that Application is brought up properly.You should delete the file
# "toolbox.debug" in the package directory. This would enable toolkit to restart
18 MySQL Toolkit scripts