Managing Serviceguard Eighteenth Edition, September 2010

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 390) 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 288)) 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.
Renaming or Replacing an External Script Used by a Running Package
In most cases, you can rename an external_script (page 309) while the package that uses
it is running, but you need to be careful; follow the instructions below.
CAUTION: If any package services or processes are dependent on resources started
by the external script, those services or processes may fail when you run cmapplyconf
(see step 5 below). In this case, do not rename, replace, or modify the external script
while the package is online.
Make sure you read and understand the information and caveats under “Allowable
Package States During Reconfiguration ” (page 390) before you proceed.
1. Make a copy of the old script, save it with the new name, and edit the copy as
needed.
2. Edit the package configuration file to use the new name.
Reconfiguring a Package 387