HP Process Resource Manager User's Guide

Configuring and enabling PRM on the command line
Configuring PRM
Chapter 7 127
For example, in the records below, the two applications /usr/bin/mv and
/bin/mv have the same underlying file ID, but are assigned to two
different PRM groups. Because of the ambiguity, it is impossible to
accurately predict which PRM group would get the application.
/usr/bin/mv::::GroupA
/bin/mv::::GroupB # duplicate record
In the next example, the application is now /usr/bin/mv in both records.
However, the alternate names cp and mv have been added to the records.
These two records would be fine in the same configuration file if the first
record had only mv as an alternate name. In that case, /usr/bin/mv
would be placed in GroupA when invoked with the mv command and in
GroupB when invoked with the cp command. However, with cp as an
alternate name in both records, we have another ambiguity.
/usr/bin/mv::::GroupA,cp,mv
/usr/bin/mv::::GroupB,cp # duplicate record
It is possible to add duplicate application records when editing a
configuration file. This happens most often when working with large
configuration files.
PRM checks for duplicate records when you load a configuration. If there
are any duplicate records in a configuration file, trying to load the file
produces errors. In this case, remove the duplicate records and load the
configuration file again.
Missing applications are ignored
PRM ignores the application records for missing applications.
This functionality, as opposed to generating errors, is desirable when
using a single configuration for multiple systems that have different
applications installed.
Applications records are also ignored if they reference applications on
filesystems that are not mounted at the time PRM is configured. Reload
the PRM configuration with prmconfig when the filesystem is present
for the application records to take effect.