Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7376
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 on page 282) 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.ascii
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” on page 375.
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” on page 271. 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
cmapplyconf -P /etc/cmcluster/pkg1/pkg1conf.ascii