Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Understanding Serviceguard Software Components
How Package Control Scripts Work
Chapter 362
NOTE If you set <n> restarts and also set SERVICE_FAILFAST_ENABLED to YES,
the failfast will take place after <n> restart attempts have failed. It does
not make sense to set SERVICE_RESTART to “-R” for a service and also set
SERVICE_FAILFAST_ENABLED to YES.
Disk Monitor Services
Services that launch resource monitors such as the disk monitor behave
just like any other service. The SERVICE_CMD that is used for disk
monitoring is the cmresserviced command, as in the following
example:
SERVICE_NAME[0]=”cmresserviced_Pkg1”
SERVICE_CMD[0]="cmresserviced /dev/sdd1 /dev/sde1”
SERVICE_RESTART[0]=""
The cmresserviced command communicates with the resource monitor
daemon, cmresmond, which is started via rc scripts at each reboot or
manually with the command cmresmond --start.
The process for configuring disk monitoring is described in “Creating a
Disk Monitor Configuration” on page 206.
While Services are Running
During the normal operation of cluster services, the package manager
continuously monitors the process IDs of configured services. If a service
fails but the RESTART parameter for that service is set to a value
greater than 0, the service will restart, up to the configured number of
restarts, without halting the package. During normal operation, while all
services are running, you can see the status of the services in the “Script
Parameters” section of the output of the cmviewcl command.