Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 299
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.
resource_name The name of a resource to be monitored.
resource_name, in conjunction with resource_polling_interval,
resource_start and resource_up_value, defines an Event Monitoring
Service (EMS) dependency.
In legacy packages, RESOURCE_NAME in the package configuration file
requires a corresponding DEFERRED_RESOURCE_NAME in the package
control script.
You can find a list of resources in Serviceguard Manager
(Configuration -> Create Package -> Monitored Resources ->
Available EMS resources), or in the documentation supplied with the
resource monitor.
A maximum of 60 EMS resources can be defined per cluster. Note also
the limit on resource_up_value (see below).
The maximum length of the resource_name string is 1024 characters.
See “Parameters for Configuring EMS Resources” on page 176 for more
information and example.
resource_polling_interval How often, in seconds, the resource
identified by resource_name (see page 299) is to be monitored. Default
is 60 seconds. The minimum value is 1. (There is no practical maximum.)
resource_start Specifies when Serviceguard will begin monitoring the
resource identified by resource_name. Valid values are automatic and
deferred.
automatic means Serviceguard will begin monitoring the resource as
soon as the node joins the cluster. deferred means Serviceguard will
begin monitoring the resource when the package starts.
resource_up_value Defines a criterion used to determine whether the
resource identified by resource_name is up.