HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

The value of each of these parameters must now be: any name, up to a maximum of
39 characters, that:
• starts and ends with an alphanumeric character
• otherwise contains only alphanumeric characters or dot (.), dash (-), or underscore
(_)
• is unique among package names in this cluster
IMPORTANT: These rules apply to both legacy and modular packages. Restrictions
on the values of these parameters in previous Serviceguard releases were less
stringent. Packages that use values for these parameters that do not conform to
the new rules will continue to run, but if you reconfigure them, you will need to
change the values; cmcheckconf and cmapplyconf will enforce the new rules.
Migrating Legacy to Modular Packages
A new Serviceguard command, cmmigratepkg, provided with the patches listed
under “New Features for March 2008 Patches” (page 14), automates the process of
migrating legacy packages to modular packages as far as possible. Many, but not all,
packages can be migrated in this way; for details, see the white paper Migrating Packages
from Legacy to Modular Style at http://docs.hp.com ->High Availability
->Serviceguard ->White papers.
NOTE: The cmmigratepkg command requires Perl version 5.8.5 or higher on the
system on which you run the command. It should already be on the system as part of
the Linux distribution.
About Package Dependencies
A package can have dependencies on other packages, meaning the package will not
start on a node unless the packages it depends on are running on that node.
You can make a package dependent on any other package or packages running on the
same cluster node, subject to the restrictions spelled out in Chapter 6 of Managing
Serviceguard for Linux.
Make a package dependent on another package if the first package cannot (or should
not) function without the services provided by the second. For example, pkg1 might
run a real-time web interface to a database managed by pkg2. In this case it might
make sense to make pkg1 dependent on pkg2.
For more information, see “About Package Dependencies” in Chapter 4 of Managing
Serviceguard for Linux.
28 Serviceguard for Linux Version A.11.18 Release Notes