Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Configuring Packages and Their Services
Writing the Package Control Script
Chapter 6198
# performance for starting up or halting a package. The maximum value for
# each concurrent operation parameter is 1024. Set these values carefully.
# The performance could actually decrease if the values are set too high
# for the system resources available on your cluster nodes. Some examples
# of system resources that can affect the optimum number of concurrent
# operations are: number of CPUs, amount of available memory, the kernel
# configuration for nfile and nproc. In some cases, if you set the number
# of concurrent operations too high, the package may not be able to start
# or to halt. It is suggested that the number of concurrent operations be
# tuned carefully, increasing the values a little at a time and observing
# the effect on the performance, and the values should never be set to a
# value where the performance levels off or declines. Additionally, the
# values used should take into account the node with the least resources
# in the cluster, and how many other packages may be running on the node.
# For instance, if you tune the concurrent operations for a package so
# that it provides optimum performance for the package on a node while
# no other packages are running on that node, the package performance
# may be significantly reduced, or may even fail when other packages are
# already running on that node.
# CONCURRENT FSCK OPERATIONS
# Specify the number of concurrent fsck processes to allow during package
# startup. Setting this value to an appropriate number may improve the
# performance while checking a large number of file systems in the package.
# If the specified value is less than 1, the script defaults it to 1 and
# proceeds with a warning message in the package control script logfile.
CONCURRENT_FSCK_OPERATIONS=1
# CONCURRENT MOUNT AND UMOUNT OPERATIONS
# Specify the number of concurrent mounts and umounts to allow during