HP Serviceguard Version A.11.18 Release Notes, September 2008

NOTE: The default form for parameter names in the modular package configuration
file is lower case; for legacy packages the default is upper case. There are no
compatibility issues; Serviceguard is case-insensitive as far as the parameter names are
concerned. These release notes use lower case, unless the parameter in question is used
only in legacy packages, or the context refers exclusively to such a package.
New Parameters
The following parameters are new as of A.11.18. They can all be used for modular
packages, and some (explicitly noted below) can also be used for legacy packages. With
the exception of “vxvm_dg_retry ”, none have direct equivalents in the configuration
file or package control file for previous Serviceguard versions.
NOTE: For more information, see the comments in the editable configuration file
output by the cmmakepkg command, and the cmmakepkg manpage. See also Managing
Serviceguard: “Package Configuration Planning” in Chapter 4, and Chapter 6
“Configuring Packages and Their Services”
module_name
The module name (for example, failover, service, etc.) Do not change it. Used in
the form of a relative path (for example sg/failover) as a parameter to cmmakepkg
to specify modules to be used in configuring the package. (The files reside in the
$SGCONF/modules directory; see “Understanding Where Files Are Located” in Chapter
5 of Managing Serviceguard for an explanation of Serviceguard directories.)
module_version
The module version. Do not change it.
successor_halt_timeout
Specifies how long, in seconds, Serviceguard will wait for packages that depend on
this package to halt, before halting this package. Can be 0 through 4294, or
no_timeout. The default is no_timeout. Can be used in both modular and legacy
packages.
• no_timeout means that Serviceguard will wait indefinitely for the dependent
packages to halt.
• 0 means Serviceguard will not wait for the dependent packages to halt before
halting this package.
See “About Package Dependencies” in Chapter 4 of Managing Serviceguard for more
information.
What’s in this Release 31