Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Configuring Packages and Their Services
Editing the Configuration File
Chapter 6232
Use the following bullet points as a checklist, referring to the “Package
Parameter Explanations” on page 209, and the comments in the
configuration file itself, for detailed specifications for each parameter.
NOTE Optional parameters are commented out in the configuration file (with a
# at the beginning of the line). In some cases these parameters have
default values that will take effect unless you uncomment the parameter
(remove the #) and enter a valid value different from the default. Read
the surrounding comments in the file, and the explanations in this
chapter, to make sure you understand the implications both of accepting
and of changing a given default.
In all cases, be careful to uncomment each parameter you intend to use
and assign it the value you want it to have.
• package_name. Enter a unique name for this package. Note that
there are stricter formal requirements for the name as of A.11.18.
• package_type. Enter failover or multi_node.
(system_multi_node is reserved for special-purpose packages
supplied by HP.) Note that there are restrictions if another package
depends on this package; see “About Package Dependencies” on
page 123.
See “Types of Package: Failover, Multi-Node, System Multi-Node” on
page 201 for more information.
• node_name. Enter the name of each cluster node on which this
package can run, with a separate entry on a separate line for each
node.
• auto_run. For failover packages, enter yes to allow Serviceguard to
start the package on the first available node specified by node_name,
and to automatically restart it later if it fails. Enter no to keep
Serviceguard from automatically starting the package.
• node_fail_fast_enabled. Enter yes to cause the node to be halted
(system halt) if the package fails; otherwise enter no.
• run_script_timeout and halt_script_timeout. Enter the number
of seconds Serviceguard should wait for package startup or
shutdown, respectively, to complete; or leave the default,
no_timeout. See page 212.