Managing Serviceguard Seventeenth Edition, First Reprint December 2009

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 287). See also “Package Configuration Planning
” (page 162).
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
IMPORTANT: Restrictions on package names in previous Serviceguard releases
were less stringent. Packages whose names do not conform to the above rules will
continue to run, but if you reconfigure them, you will need to change the name;
cmcheckconf and cmapplyconf will enforce the new rules.
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 “Learning Where Serviceguard Files Are Kept”
(page 196) for an explanation of Serviceguard directories.)
New for modular packages.
module_version
The module version. Do not change it.
New for modular packages.
264 Configuring Packages and Their Services