Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7 273
Reconfiguring a Package
You reconfigure a package in much the same way as you originally
configured it; for modular packages, see Chapter 6, “Configuring
Packages and Their Services,” on page 191; for older packages, see
“Configuring a Legacy Package” on page 262.
The cluster can be either halted or running during package
reconfiguration, but the types of change you can make and the times
when they take effect depend on whether the package is running or not.
If you reconfigure a package while it is running, it is possible that the
package could fail later, even if the cmapplyconf succeeded.
For example, consider a package with two volume groups. When this
package started, it activated both volume groups. While the package is
running, you could change its configuration to list only one of the volume
groups, and cmapplyconf would succeed. If you issue cmhaltpkg
command, however, the halt would fail. The modified package would not
deactivate both of the volume groups that it had activated at startup,
because it would only see the one volume group in its current
configuration file.
Reconfiguring a Package on a Running Cluster
You can reconfigure a package while the cluster is running, and in some
cases you can reconfigure the package while the package itself is
running. You can do this in Serviceguard Manager (for legacy packages),
or use Serviceguard commands.
To modify the package with Serviceguard commands, use the following
procedure (pkg1 is used as an example):
1. Halt the package if necessary:
cmhaltpkg pkg1
See Table 7-2 to determine whether this step is needed.
2. If it is not already available, you can obtain a copy of the package's
configuration file by using the cmgetconf command, specifying the
package name.
cmgetconf -p pkg1 pkg1.ascii