Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Understanding Serviceguard Software Components
How Package Control Scripts Work
Chapter 3 63
When a Service or Subnet Fails
What happens when something goes wrong? If a service fails and there
are no more restarts, or if the control script fails, then the package will
halt on its current node and, depending on the setting of the package
switching flags, may be restarted on another node. Package halting
normally means that the package halt script executes (see the next
section). However, if SERVICE_FAILFAST_ENABLED is set to yes for the
service that fails, then the node will halt as soon as the failure is
detected. If this flag is not set, the loss of a service will result in halting
the package gracefully by running the halt script.
If AUTO_RUN is set to YES, the package will start up on another eligible
node, if it meets all the requirements for startup. If AUTO_RUN is set to NO,
then the package simply halts without starting up anywhere else.
When a Package is Halted with a Command
The Serviceguard cmhaltpkg command has the effect of executing the
package halt script, which halts the services that are running for a
specific package. This provides a graceful shutdown of the package that
is followed by disabling automatic package startup (AUTO_RUN).
NOTE If the cmhaltpkg command is issued with the -n <nodename> option,
then the package is halted only if it is running on that node.
The cmmodpkg command cannot be used to halt a package, but it can
disable switching either on particular nodes or on all nodes. A package
can continue running when its switching has been disabled, but it will
not be able to start on other nodes if it stops running on its current node.