HP Process Resource Manager User's Guide

Understanding how PRM manages resources
How PRM manages applications
Chapter 2 65
should be within single quotes. Other records can still have non-ERE
alternate names for the same application. Note that while non-ERE
alternate names are matched against non-dash command-line
arguments, Extended Regular Expression alternate names are matched
against the entire available command line. Note that commas within an
ERE are not separators for alternate names; they must match commas in
the command line.
NOTE You cannot use colons in an ERE, as PRM uses colons for field
separators.
If an ERE alternate name and a non-ERE alternate name both exist for
the same application, the non-ERE alternate name takes priority. If
multiple ERE alternate names match, the “first” record to match takes
precedence. For example, the application abb matches both of the
following application records:
/opt/foo/bin/bar::::GroupA,’a.*’
/opt/foo/bin/bar::::GroupB,’.*b’
Because the ’.*b’ record is first (based on ASCII dictionary order), the
application abb would be assigned to the PRM group GroupB.
Knowing the names of all the processes spawned and renamed by the
applications can help in creating pattern matching that is only as
general as it needs to be. Eliminate redundant name resolutions
whenever possible, and make sure pattern matching does not cause
unwarranted moves.
For information on how alternate name pattern matching affects
precedence, see the next section, “Precedence of PRM group
assignments.”
Precedence of PRM group assignments
The PRM application manager checks that applications are running in
the correct PRM groups every interval seconds. The default interval
is 30 seconds; however, you can change it as explained in the section
“Setting the application manager’s polling interval” on page 181.