Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7274
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 201) 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 the package configuration
while the cluster is not running. Use the same steps as in “Reconfiguring
a Package on a Running Cluster” on page 273.
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 Chapter 6,
“Configuring Packages and Their Services,” on page 191. Then use a
command such as the following to verify the configuration of the newly
created pkg1 on a running cluster:
cmcheckconf -P $SGCONF/pkg1/pkg1conf.ascii
Use a command such as the following to distribute the new package
configuration to all nodes in the cluster: