Managing HP Serviceguard A.11.20.10 for Linux, December 2012

NOTE: Be careful when defining service run commands. Each run command is executed in the
following way:
• The cmrunserv command executes the run command.
• Serviceguard monitors the process ID (PID) of the process the run command creates.
• When the command exits, Serviceguard determines that a failure has occurred and takes
appropriate action, which may include transferring the package to an adoptive node.
• If a run command is a shell script that runs some other command and then exits, Serviceguard
will consider this normal exit as a failure.
Make sure that each run command is the name of an actual service and that its process remains
alive until the actual service stops. One way to manage this is to configure a package such that
the service is actually a monitoring program that checks the health of the application that constitutes
the main function of the package, and exits if it finds the application has failed. The application
itself can be started by an external_script (page 184).
This parameter is in the package control script for legacy packages.
6.1.4.29 service_restart
The number of times Serviceguard will attempt to re-run the service_cmd. Valid values are
unlimited, none or any positive integer value. Default is none.
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.
This parameter is in the package control script for legacy packages.
6.1.4.30 service_fail_fast_enabled
Specifies whether or not Serviceguard will halt the node (reboot) on which the package is running
if the service identified by service_name fails. Valid values are yes and no. Default is no,
meaning that failure of this service will not cause the node to halt.
6.1.4.31 service_halt_timeout
The length of time, in seconds, Serviceguard will wait for the service to halt before forcing
termination of the service’s process. The maximum value is 4294.
The value should be large enough to allow any cleanup required by the service to complete.
If no value is specified, a zero timeout will be assumed, meaning that Serviceguard will not wait
any time before terminating the process.
6.1.4.32 generic_resource_name
Defines the logical name used to identify a generic resource in a package. This name corresponds
to the generic resource name used by the cmgetresource(1m) and cmsetresource(1m)
commands.
Multiple generic_resource_name entries can be specified in a package.
The length and formal restrictions for the name are the same as for package_name (page 169).
Each name must be unique within a package, but a single resource can be specified across multiple
packages.
You can configure a maximum of 100 generic resources per cluster.
Each generic resource is defined by three parameters:
178 Configuring Packages and Their Services