HP Process Resource Manager (PRM) manual Updating the configuration

NOTE: Before or after enabling PRM, you can fine-tune your configuration. See the chapter “Fine-tuning your PRM configuration ” (page 83) for details.

Enabling resource managers with prmconfig

To start all PRM resource managers (CPU, memory, and application), enter the following command:

#prmconfig -e

If there are no memory records, the memory manager is not started. However, even if there are no application records, the application manager does start.

The prmconfig -ecommand controls only whether the PRM resource management is being used and does not change the configuration. However, PRM must be configured (have a configuration loaded) for this option to be valid.

When PRM is enabled, it takes precedence over standard HP-UX resource management when the system is at peak load.

If you wish to enable PRM for one type of resource only, specify the appropriate keyword as shown in Table 15.

Table 15 Enabling specific resource management on the command line

To enable PRM for	Enter
CPU management only	#prmconfig -e CPU
Memory management only	#prmconfig -e MEM
Application management only	#prmconfig -e APPL
CPU capping for all FSS PRM groups (For information on	#prmconfig -e CPU -M CPUCAPON
per-group capping, see “Group/CPU record syntax” (page
55).)

NOTE: You must enable the application manager to enforce application records, user records, compartment records, and Unix group records.

Updating the configuration

To update your configuration, simply change your configuration file and load it. You do not need to disable or reset PRM to make changes to your PRM configuration.

For small changes you can bring the configuration file into a text editor or a GUI, make the changes, save the file, and then load the configuration with prmconfig or a GUI.

If you are adding a large number of new users to the configuration file, you can use prmloadconf to add the users for you. For each user in the password file not already specified in the configuration file, prmloadconf appends a PRM user record to the configuration file. The added record specifies the user’s login name from the password file and the placeholder (NONE) instead of a PRM group. After using prmloadconf, you may want to modify the user’s initial group and add alternate groups. After changing the configuration file, you must still load the configuration using either prmconfig or a GUI.

When using prmloadconf, if the configuration file already exists, elements of the existing file are checked for suitability (such as the presence of the user default group). Use the -foption to specify a configuration file other than /etc/prmconf.

If the new configuration deletes a group, then all currently running processes that were associated with that group are moved to the owner’s initial group, and to the assigned groups for configured applications. If a process owner does not have an initial group or its group does not exist in the new configuration, the process is moved to the user default group OTHERS (PRMID 1). If the owner of a process running in a group that is deleted is a root user, the process is moved to the system

Updating the configuration 81