Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7 341
Managing Packages and Services
Managing packages and services involves the following tasks:
• Starting a Package
• Halting a Package
• Moving a Package (halt, then start)
• Changing Package Switching Behavior
Non-root users can perform these tasks, as regulated by access policies in
the cluster’s configuration files. See “Editing Security Files” on page 201
for more information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to
perform these tasks.
Starting a Package
Ordinarily, when a cluster starts up, the packages configured as part of
the cluster will start up on their configured nodes. You may need to start
a package manually after it has been halted manually. You can do this
either in Serviceguard Manager or on the Serviceguard command line.
If any package has a configured dependency on another package,
Serviceguard will start them in order, ensuring that a package will not
start until its dependency is met.
You can use Serviceguard Manager, or Serviceguard commands as shown
below, to start a package.
The cluster must be running, and if the package is dependent on other
packages, those packages must be either already running, or started by
the same command that starts this package (see the section that follows,
and “About Package Dependencies” on page 171.)
Starting a Package that Has Dependencies
Before starting a package, it is a good idea to use the cmviewcl command
to check for package dependencies.