Managing Serviceguard Seventeenth Edition, First Reprint December 2009

1. Halt the package if necessary:
cmhaltpkg pkg1
CAUTION: Make sure you read and understand the information and caveats
under“Allowable Package States During Reconfiguration ” (page 354) before you
decide to reconfigure a running package.
2. If it is not already available, obtain a copy of the package's configuration file by
using the cmgetconf command, specifying the package name.
cmgetconf -p pkg1 pkg1.conf
3. Edit the package configuration file.
IMPORTANT: Restrictions on package names, dependency names, and service
names have become more stringent as of A.11.18. Packages that have or contain
names that do not conform to the new rules (spelled out under package_name
(page 264)) will continue to run, but if you reconfigure these packages, you will
need to change the names that do not conform; cmcheckconf and cmapplyconf
will enforce the new rules.
4. Verify your changes as follows:
cmcheckconf -v -P pkg1.conf
5. Distribute your changes to all nodes:
cmapplyconf -v -P pkg1.ascii
6. If this is a legacy package, copy the package control script to all nodes that can run
the package.
Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in package configuration while the cluster is
not running. Use the same steps as in “Reconfiguring a Package on a Running Cluster
” (page 351).
Adding a Package to a Running Cluster
You can create a new package and add it to the cluster configuration while the cluster
is up and while other packages are running. The number of packages you can add is
subject to the value of MAX_CONFIGURED_PACKAGES in the cluster configuration
file.
To create the package, follow the steps in the chapter “Configuring Packages and Their
Services ” (page 255). Use a commands such as the following to verify the configuration
of a newly created pkg1 and distribute the configuration to all nodes in the cluster:
cmcheckconf -P /etc/cmcluster/pkg1/pkg1conf.ascii
352 Cluster and Package Maintenance