Checking the configuration file

Use prmconfig -sto perform validation without changing the current PRM configuration. This can be helpful to validate a configuration file that will be activated by a script at a later time. To specify a configuration file other than /etc/prmconf, use prmconfig -s-fconfigfile.

Validation checks for:•Duplicate group names•Duplicate user names•Undefined groups in user access lists

•Mismatches between the users listed in the configuration file and the logins in the password files accessible by the C function getpwnam

The checks are made when you save or load a configuration file.

Warnings reported in the check may indicate an invalid configuration. These warnings do not prevent you from loading the configuration and enabling PRM. For example, you may not specify all users in the PRM configuration file and mismatches may exist, but the file is still valid. Users not specified in the PRM configuration file use the user default group OTHERS (PRMID 1) as their initial group, and they have no alternate groups.

Loading the PRM configuration

Once you plan your configuration, install PRM, and create your custom configuration file, you are ready to load your configuration.

Neither the prmconfig options for loading a configuration nor the GUI equivalents start PRM management of resources; they only load your specific configuration. All existing and newly spawned processes are stamped with their PRM group identifiers. However, standard HP-UX is still managing resource allocation. prmconfig and the corresponding GUI menu items can be executed regardless of whether PRM or the standard HP-UX resource management is currently being used.

When you load a configuration with prmconfig -i, prmconfig -k, or the GUI equivalents, the configuration file is checked for errors. If errors are found, PRM issues error messages, and does not change the configuration. Errors in the configuration file must be corrected before PRM can be configured and enabled.

When the prmconfig -i, prmconfig -k, or GUI equivalents complete without finding errors, an internal copy of the configuration file is made. This copy is used by the PRM commands as well as the PRM-aware HP-UX commands while PRM is configured. (For information on these PRM-aware commands, see “HP-UX command/system call support” (page 116).) Thus, the original configuration file can be edited without disrupting PRM. However, to be safe, you should create a work copy to make modifications to the configuration file.

If a PRM configuration is not already loaded, using either prmconfig -ior prmconfig -k(or the GUI equivalents) moves all currently running processes, not owned by any root user, to their owners’ initial groups. However, if a user’s initial group is not defined in the configuration file or there is no record for the user, the processes are placed in OTHERS (PRMID 1), the user default group. This occurs even if the PRM scheduler has not been enabled. Any configured application is moved to the group assigned in the PRM configuration file.

If a PRM configuration is already loaded and some processes have been moved to alternate groups, the two types of configuration loads have different results, as shown in Table 14.

Configuring PRM 79