Managing Serviceguard Seventeenth Edition, First Reprint December 2009

In addition to the standard package script, you use the special script that is provided
for the database. To set up these scripts, follow the instructions in the README
file provided with each toolkit.
• Configure the Access Control Policy for up to eight specific users or any_user.
The only user role you can configure in the package configuration file is
package_admin for the package in question. Cluster-wide roles are defined in
the cluster configuration file. See “Setting up Access-Control Policies” (page 230)
for more information.
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.conf
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.conf
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.
Verifying and Applying the Package Configuration 293