User's Manual
Table Of Contents
- HP Process Resource Manager User Guide
- Contents
- Preface
- 1 Overview
- 2 Understanding how PRM manages resources
- 3 PRM configuration planning
- 4 Setting up PRM
- 5 Using PRM with HP System Management Homepage (SMH)
- 6 Using PRM with HP Systems Insight Manager (SIM)
- 7 Configuring and enabling PRM on the command line
- Quick start to using PRM’s command-line interface
- Configuring PRM
- The PRM configuration file
- Configuration tips and requirements
- Specifying PRM groups/controlling CPU resource use
- Controlling memory use
- Controlling applications
- Specifying PRM users
- Assigning secure compartments to PRM groups
- Assigning Unix groups to PRM groups
- Checking the configuration file
- Loading the PRM configuration
- Enabling resource managers
- Updating the configuration
- 8 Fine-tuning your PRM configuration
- 9 Administering PRM
- Moving processes between PRM groups
- Displaying application filename matches
- Displaying netgroup expansions
- Displaying accessible PRM groups
- Displaying state and configuration information
- Displaying application and configuration information
- Setting the memory manager’s polling interval
- Setting the application manager’s polling interval
- Disabling PRM
- Resetting PRM
- Monitoring PRM groups
- Logging PRM memory messages
- Logging PRM application messages
- Displaying groups’ allocated and used resources
- Displaying user information
- Displaying available memory to determine number of shares
- Displaying number of cores to determine number of shares
- Displaying past process information
- Displaying current process information
- Monitoring PRM with GlancePlus
- Monitoring PRM with OpenView Performance Agent (OVPA) / OpenView Performance Manager (OVPM)
- Automating PRM administration with scripts
- Protecting the PRM configuration from reboots
- Reconstructing a configuration file
- Special case of interest: Client/server connections
- Online cell operations
- Backing up PRM files
- A Command reference
- B HP-UX command/system call support
- C Monitoring PRM through SNMP
- D Creating Secure Resource Partitions
- E Using PRM with Serviceguard
- F Using PRM with HP Integrity Virtual Machines
- G PRM error messages
- Glossary
- Index
6. Unix group records
If a record exists for the effective group ID of the process and the record indicates a PRM
group other than (NONE), move the process to the indicated PRM group.
7. Move the process to the OTHERS group.
To illustrate these rules, consider the following application records:
/bin/call_home::::GroupA
/bin/cal*::::GroupB
/bin/cal::::GroupC
/bin/c*::::GroupD
/bin/call_home::::GroupE,phone_home,tele*_home
/opt/foo/bin/bar::::GroupF
/opt/foo/bin/bar_none::::GroupG
/bin/call_home::::GroupZ,*home
Assume a user starts an application, my_favorite_app, without using prmrun:
% my_favorite_app
Because the application does not have an application record, it does not meet any of the criteria
above and starts in the invoking user’s PRM group.
Now assume the user starts the bar_none application, which has a record, but is started in a
group specified using prmrun.
% prmrun -g GroupA bar_none
In this case, the application manager determines that the application has been moved manually
and leaves it as is, in GroupA.
Next, assume the user launches the bar application, which also has an application record.
% bar
The application starts in the invoking user’s initial group. However, the application manager will
soon place the application in the group specified in the application record, GroupF.
The user then starts another program:
% phone_home
This application name is an exact match of an alternate name. If phone_home has the same file
ID as /bin/call_home, the phone_home process is placed in GroupE.
Another user on the system starts a program:
% telegraph_home
This application name matches two alternate names, both specified using regular expressions:
tele*_home and *home. Sorting based on the ASCII dictionary, the application matches *home
first. Assuming telegraph_home has the same file ID as /bin/call_home, it is placed in
GroupZ.
Starting one more program:
% call_home
The call_home command is matched by the first and eighth records. (The second and fourth
records do not match because PRM expands the regular expressions when the configuration is
loaded and finds call_home already has a record.) The eighth record takes precedence because
it has an alternate name, and the call_home process is placed in GroupZ.
NOTE: Be careful when constructing regular expressions: As shown with the eighth record above,
an expression that is not specific enough can override explicit application records.
Lastly, a user starts the following program:
% calendar
How PRM manages applications 35