HP Serviceguard Extended Distance Cluster for Linux A.11.20.20 Deployment Guide, August 2013

ManualsBrandsHP ManualsSoftwareHP Serviceguard for Linux License Kit

# Specify the name of each volume group.

# For example, if this package uses your volume groups vg01 and vg02, enter:

# vg vg01

# vg vg02

# The volume group activation method is defined above. The filesystems

# associated with these volume groups are specified below.

# Legal values for vg: /^[0-9A-Za-z\/][0-9A-Za-z_.\/\-]*[0-9A-Za-z]$/, /^[0-9A-Za-z]$/.

#vg

# 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

# 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).

5.1 Creating a serviceguard-xdc Modular Package 33