Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7318
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
In Serviceguard A.11.16 and later, these commands can be done by
non-root users, according to access policies in the cluster’s configuration
files. See “Editing Security Files” on page 189, 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.
Using Serviceguard Commands to Start a Package
Use the cmrunpkg command to run the package on a particular node,
then use the cmmodpkg command to enable switching for the package.
Example, for a failover package:
# cmrunpkg -n ftsys9 pkg1
# cmmodpkg -e pkg1