Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Table 11 Optional Modules (continued)
CommentsParameters (page)Module Name
Use if you are creating a complex
package that requires most or all
all parametersall
of the optional parameters; or if
you want to see the specifications
and comments for all available
parameters.
Use if you are creating a
multi-node package that requires
all parameters that can be used by a multi-node
package; includes multi_node, dependency,
multi_node_all
most or all of the optional
monitor_subnet, service, resource,
parameters that are available for
this type of package.
volume_group, filesystem, pev,
external_pre, external, and acp modules.
A symbolic link to the all module;
used if you do not specify a base
(all parameters)default
module on the cmmakepkg
command line; see “cmmakepkg
Examples” (page 241).
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. This manual uses lower case,
unless the parameter in question is used only in legacy packages, or the context refers exclusively
to such a package.
Package Parameter Explanations
Brief descriptions of the package configuration parameters follow.
NOTE: For more information, see the comments in the editable configuration file output by the
cmmakepkg command, and the cmmakepkg manpage.
If you are going to browse these explanations deciding which parameters you need, you may
want to generate and print out a configuration file that has the comments for all of the parameters;
you can create such a file as follows:
cmmakepkg -m sg/all $SGCONF/sg-all
or simply
cmmakepkg $SGCONF/sg-all
This creates a file /etc/cmcluster/sg-all that contains all the parameters and comments.
More detailed instructions for running cmmakepkg are in the next section, “Generating the Package
Configuration File” (page 241). See also “Package Configuration Planning ” (page 120).
package_name
Any name, up to a maximum of 39 characters, that:
• starts and ends with an alphanumeric character
• otherwise contains only alphanumeric characters or dot (.), dash (-), or underscore (_)
• is unique among package names in this cluster
222 Configuring Packages and Their Services