Verifying and Applying the Package Configuration

Serviceguard checks the configuration you enter and reports any errors.

Use a command such as the following to verify the content of the package configuration file you have created, for example:

cmcheckconf -v -P $SGCONF/pkg1/pkg1.config

Errors are displayed on the standard output. If necessary, re-edit the file to correct any errors, then run cmcheckconf again until it completes without errors.

The following items are checked:

Package name is valid, and at least one node_name entry is included.
There are no duplicate parameter entries (except as permitted for multiple volume groups, etc).
Values for all parameters are within permitted ranges.
Configured resources are available on cluster nodes.
File systems and volume groups are valid.
Services are executable.
Any package that this package depends on is already be part of the cluster configuration.

When cmcheckconf has completed without errors, apply the package configuration, for example:

cmapplyconf -P $SGCONF/pkg1/pkg1.config

This adds the package configuration information to the binary cluster configuration file in the $SGCONF directory (normally /etc/cmcluster) and distributes it to all the cluster nodes.




	NOTE: For modular packages, you now need to distribute any external scripts identified by the `external_pre_script` and `external_script` parameters. But if you are accustomed to configuring legacy packages, note that you do not have to create a separate package control script for a modular package, or distribute it manually. (You do still have to do this for legacy packages; see “Configuring a Legacy Package”.)

Verifying and Applying the Package Configuration

Technical documentation

» Table of Contents

» Index