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

# monitoring the application.
#
# Note: if Maintenance flag is set to "no" then the above feature would not be
# available.
#
# Legal values for tkit/toolbox/toolbox/TKIT_MAINTENANCE_FLAG: yes, no.
tkit/toolbox/toolbox/TKIT_MAINTENANCE_FLAG yes
#
# The interval (in seconds) between checking if application is are up and running.
# The default setting is 5 seconds.
#
#
# Legal values for tkit/toolbox/toolbox/TKIT_MONITOR_INTERVAL: <Any String>
tkit/toolbox/toolbox/TKIT_MONITOR_INTERVAL 5
# Legal values for tkit/toolbox/toolbox/TKIT_MONITORING_TYPE: <Any String>
tkit/toolbox/toolbox/TKIT_MONITORING_TYPE pid_file
# Legal values for tkit/toolbox/toolbox/TKIT_MONITORING_ELEMENT: <Any String>
tkit/toolbox/toolbox/TKIT_MONITORING_ELEMENT /var/run/mysqld/mysqld.pid
# Legal values for tkit/toolbox/toolbox/TKIT_APP_START: <Any String>
tkit/toolbox/toolbox/TKIT_APP_START /usr/local/cmcluster/mysql/start_app.sh
# Legal values for tkit/toolbox/toolbox/TKIT_APP_STOP: <Any String>
tkit/toolbox/toolbox/TKIT_APP_STOP /usr/local/cmcluster/mysql/stop_app.sh
# Legal values for tkit/toolbox/toolbox/APP_SERVER_PROC: <Any String>
tkit/toolbox/toolbox/APP_SERVER_PROC mysqld
# Services: A service is an long lived (daemon) executable which
# Serviceguard will monitor while the package is up.
#
# "service_name", "service_cmd", "service_restart", "service_fail_fast_enabled"
# and "service_halt_timeout" specify a service for this package.
#
# "service_cmd" is the command line to be executed to start the service.
#
# The value for "service_restart" can be "unlimited", "none" or any
# positive integer value. If the value is "unlimited" the service will be
# restarted an infinite number of times. If the value is "none", the
# service will not be restarted. If the value is a positive integer,
# the service will be restarted the specified number of times
# before failing. If "service_restart" is not specified, the
# default will be "none".
#
# The value for "service_fail_fast_enabled" can be either "yes" or "no".
# The default is "no". If "service_fail_fast_enabled" is set to "yes",
# and the service fails, Serviceguard will halt the node on which the
# service is running.
#
# "service_halt_timeout" is a number of seconds.
# This timeout is used to determine the length of time
# Serviceguard will wait for the service to halt before a SIGKILL signal
# is sent to force the termination of the service. In the event of a
# service halt, Serviceguard will first send a SIGTERM signal to
# terminate the service. If the service does not halt, Serviceguard will
# wait for the specified "service_halt_timeout", then send
# the SIGKILL signal to force the service to terminate.
# This timeout value should be large enough to allow all cleanup
# processes associated with the service to complete. If the
# "service_halt_timeout" is not specified, a zero timeout will be
# assumed, meaning the cluster software will not wait at all # before sending the SIGKILL signal to halt the
service.
#
# Example:
# service_name service_1a
# service_cmd "/usr/bin/X11/xclock -display 192.10.25.54:0"
# service_restart none
# service_fail_fast_enabled no
# service_halt_timeout 300
#
# service_name service_1b
# service_cmd "/usr/bin/X11/xload -display 192.10.25.54:0"
# service_restart 2
# service_fail_fast_enabled no
# service_halt_timeout 300
#
# service_name service_1c
# service_cmd "/usr/sbin/ping node_a"
# service_restart unlimited
# service_fail_fast_enabled no
# service_halt_timeout 300
#
# Note: Default shell is /usr/bin/sh.
#
# Legal values for service_name:
# Any string that starts and ends with an alphanumeric character, and
19