Patch Name: PHSS_21604 Patch Description: s700_800 10.20 PRM C.01.07 Cumulative Patch Creation Date: 00/05/04 Post Date: 00/05/10 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: PRM C.01.07 Filesets: Proc-Resrc-Mgr.PRM-RUN,C.01.07 PRM-Sw-Lib.PRM-LIB,C.01.07 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_21604 Symptoms: PHSS_21604: 1) Application record with wildcard causes system daemons, such as vhand, to be moved into the PRM group specified by the application record. 2) prmmonitor prints garbage if the PRM disk resource manager is not enabled and at least one other PRM resource manager is enabled. PHSS_20672: 1) Writing to mmap files causes PRM to think the system is paging. 2) prmmonitor -s doesn't display PRM_SYS group. 3) prmconfig and xprm will core dump if application record wildcard matches a zero-length file which has execute permission. Defect Description: PHSS_21604: 1) prmconfig was treating the wildcard pathname itself as a filename. Since the wildcard pathname doesn't exist, it maps to file id -1. Since system daemons like vhand have no path or backing file, their file id is also -1. 2) prmmonitor tried to print resource management statistics for a device even if resource management for the device was not enabled. Now, statistics are gathered only if resource management for the device is enabled. PHSS_20672: 1) The kernel variable that PRM uses to monitor page-outs is incremented when processes write to mmap files. This can fool PRM into thinking that the system is out of free memory and paging. 2) prmmonitor -s was not displaying the PRM_SYS group. 3) prmconfig and xprm use the same library, libprmext, to process application records. The libprmext library contained code which would dereference a null pointer if an application record wildcard matched a zero-length file which had execute permission. SR: 8606114108 Patch Files: /opt/prm/bin/prm0d /opt/prm/bin/prm1d /opt/prm/bin/prmmonitor /opt/prm/lib/libprmext.1 what(1) Output: /opt/prm/bin/prm0d: C.01.07 PHSS_21604 HP PRM 05/03/00 prm0d /opt/prm/bin/prm1d: C.01.07 PHSS_21604 HP PRM 05/03/00 prm1d /opt/prm/bin/prmmonitor: C.01.07 PHSS_21604 HP PRM 05/03/00 prmmonitor /opt/prm/lib/libprmext.1: C.01.07 PHSS_21604 HP PRM 05/03/00 prmext for HP-UX 10.20 cksum(1) Output: 3103942550 24576 /opt/prm/bin/prm0d 1011856438 36864 /opt/prm/bin/prm1d 1460740987 36864 /opt/prm/bin/prmmonitor 1246058343 471040 /opt/prm/lib/libprmext.1 Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_20672 Equivalent Patches: PHSS_21605: s700: 11.00 s800: 11.00 Patch Package Size: 620 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_21604 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_21604.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_21604. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_21604.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_21604.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None