Managing HP Serviceguard A.11.20.10 for Linux, December 2012

Table 12 Types of Changes to Packages (continued)
Required Package StateChange to the Package
Package should not be running (unless you are only changing fs_umount_opt).
Changing file-system options other than fs_umount_opt may cause problems
because the file system must be unmounted (using the existing fs_umount_opt)
and remounted with the new options; the CAUTION under “Remove a file system:
modular package” applies in this case as well.
If only fs_umount_opt is being changed, the file system will not be unmounted;
the new option will take effect when the package is halted or the file system is
unmounted for some other reason.
Change a file system: modular
package
Package can be running.Add a file system: modular package
Package must not be running.Add or change a file system: legacy
package
Package should not be running.
CAUTION: Removing a file system may cause problems if the file system cannot
be unmounted because it's in use by a running process. In this case Serviceguard
kills the process; this could cause the package to fail.
Remove a file system: modular
package
Package must not be running.Remove a file system: legacy
package
Package can be running.
These changes in themselves will not cause any file system to be unmounted.
Change
concurrent_fsck_operations,
, fs_mount_retry_count,
fs_umount_retry_count:
modular package
Package must not be running.Change
concurrent_fsck_operations,
, fs_mount_retry_count,
fs_umount_retry_count:
legacy package
Package can be running.
Changes take effect when applied, whether or not the package is running. If you
add a script, Serviceguard validates it and then (if there are no errors) runs it
when you apply the change. If you delete a script, Serviceguard stops it when
you apply the change.
Add, change, or delete external
scripts and pre-scripts: modular
package
Package can be either running or halted.
See “Choosing Switching and Failover Behavior” (page 103).
Change package auto_run
Both packages can be either running or halted.
Special rules apply to packages in maintenance mode; see “Dependency Rules
for a Package in Maintenance Mode or Partial-Startup Maintenance Mode ”
(page 214).
For dependency purposes, a package being reconfigured is considered to be
UP. This means that if pkgA depends on pkgB, and pkgA is down and pkgB is
being reconfigured, pkgA will run if it becomes eligible to do so, even if pkgB's
reconfiguration is not yet complete.
HP recommends that you separate package dependency changes from changes
that affect resources and services that the newly dependent package will also
depend on; reconfigure the resources and services first and apply the changes,
then configure the package dependency.
For more information see “About Package Dependencies” (page 107).
Add or delete a configured
dependency
Package can be running provided the status of the generic resource is not 'down'.
For information on online changes to generic resources, see “Online
Reconfiguration of Generic Resources” (page 107).
Add a generic resource of
evaluation type
during_package_start
7.8 Reconfiguring a Package 237