Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7 271
Verifying the Package Configuration
Serviceguard checks the configuration you create and reports any errors.
For legacy packages, you can do this in Serviceguard Manager: click
Check to verify the package configuration you have done under any
package configuration tab, or to check changes you have made to the
control script. Click Apply to verify the package as a whole. See the local
Help for more details.
If you are using the command line, use the following command to verify
the content of the package configuration you have created:
cmcheckconf -v -P $SGCONF/pkg1/pkg1.config
Errors are displayed on the standard output. If necessary, edit the file to
correct any errors, then run the command again until it completes
without errors.
The following items are checked (whether you use Serviceguard Manager
or cmcheckconf command):
Package name is valid, and at least one NODE_NAME entry is included.
There are no duplicate parameter entries.
Values for parameters are within permitted ranges.
Run and halt scripts exist on all nodes in the cluster and are
executable.
Run and halt script timeouts are less than 4294 seconds.
Configured resources are available on cluster nodes.
If a dependency is configured, the dependency package must already
be configured in the cluster.
Distributing the Configuration
You can use Serviceguard Manager or Linux commands to distribute the
binary cluster configuration file among the nodes of the cluster.