Managing HP Serviceguard A.11.20.20 for Linux, May 2013

• If the package will run an external script, use the external_script parameter (see
(page 190)) to specify the full pathname of the script, for example, $SGCONF/pkg1/script1.
See “About External Scripts” (page 127), and the comments in the configuration file, for more
information.
• 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 160) for more information.
6.4 Adding or Removing a Module from an Existing Package
To add a module to an existing package, use the cmmakepkg command to generate a new
configuration file. Then, include the parameters of the new module to the existing package
configuration file and re-apply the package configuration.
For example, to add an external_script module to an existing package, say pkg1:
1. Obtain a copy of the package configuration file:
cmgetconf -p pkg1 pkg1.conf
2. Generate a new configuration file adding the external_script module to the existing
package pkg1:
cmmakepkg -i pkg1.conf -m sg/external_script pkg1_v2.conf
3. Edit the package configuration file and specify the external_script parameter.
4. Re-apply the package configuration:
cmapplyconf -P pkg1_v2.conf
To remove a module from an existing package, use the cmmakepkg command to generate a new
configuration file excluding the module that you want to remove. Then, copy the remaining package
attributes from the old configuration file to the new configuration file and re-apply the package
configuration.
6.5 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.
196 Configuring Packages and Their Services