Managing Serviceguard 14th Edition, June 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 171
Serviceguard will start up resource monitoring for automatic resources
automatically when the Serviceguard cluster daemon starts up on the
node.
Serviceguard will not attempt to start deferred resource monitoring
during node startup, but will start monitoring these resources when the
package runs.
The following is an example of how to configure deferred and
automatic resources.
resource_name /net/interfaces/lan/status/lan0
resource_polling_interval 60
resource_start deferred
resource_up_value = up
resource_name /net/interfaces/lan/status/lan1
resource_polling_interval 60
resource_start deferred
resource_up_value = up
resource_name /net/interfaces/lan/status/lan0
resource_polling_interval 60
resource_start automatic
resource_up_value = up
NOTE For a legacy package, specify the deferred resources again in the package
control script, using the DEFERRED_RESOURCE_NAME parameter:
DEFERRED_RESOURCE_NAME[0]="/net/interfaces/lan/status/lan0"
DEFERRED_RESOURCE_NAME[1]="/net/interfaces/lan/status/lan1"
If a resource is configured to be AUTOMATIC in a legacy configuration file,
you do not need to define DEFERRED_RESOURCE_NAME in the package
control script.
About Package Dependencies
Starting in Serviceguard A.11.17, a package can have dependencies on
other packages, meaning the package will not start on a node unless the
packages it depends on are running on that node.