Managing Serviceguard Eighteenth Edition, September 2010

to match that of modular packages as far as possible; these cases are shown in the table.
For more information about legacy and modular packages, see Chapter 6 (page 279).
NOTE: If neither legacy nor modular is called out under “Change to the Package”, the
“Required Package State” applies to both types of package. Changes that are allowed,
but which HP does not recommend, are labeled “should not be running”.
IMPORTANT: Actions not listed in the table can be performed for both types of package
while the package is running.
In all cases the cluster can be running, and packages other than the one being
reconfigured can be running. And remember too that you can make changes to package
configuration files at any time; but do not apply them (using cmapplyconf or
Serviceguard Manager) to a running package in the cases indicated in the table.
NOTE: All the nodes in the cluster must be powered up and accessible when you
make package configuration changes.
Table 7-3 Types of Changes to Packages
Required Package StateChange to the Package
Package must not be running.
NOTE: You cannot delete a package if another package has a
dependency on it.
Delete a package or change
package name
Package must not be running.Change package type
Package can be running.Add or delete a module:
modular package
Package can be running, but should not be starting.
Timing problems may occur if the script is changed while the package
is starting.
Change run script contents:
legacy package
Package can be running, but should not be halting.
Timing problems may occur if the script is changed while the package
is halting.
Change halt script contents:
legacy package
Package can be running.
Serviceguard treats any change to service_name or service_cmd as deleting
the existing service and adding a new one, meaning that the existing
service is halted.
Add or delete a service: modular
package
Package must not be running.Add or delete a service: legacy
package
Reconfiguring a Package 391