Patch Name: PHCO_19549 Patch Description: s700_800 10.X patch cleanup utility Creation Date: 99/12/29 Post Date: 99/12/30 Warning: 00/01/05 - This Non-Critical Warning has been issued by HP. - PHCO_19549 introduced a problem with the cleanup utility that can result in non-superseded patch backup files being removed from /var/adm/sw/patch. If cleanup is invoked with no options and is allowed to trim the Software Distributor (SD) log files, it may report that the backup files for non-superseded patches are candidates for removal. If the user acknowledges these non-superseded patch backup files can be removed, they will be removed from the /var/adm/sw/patch directory and these patches will not be able to be removed from the system in the future. - Please note that no patches are removed from the system. It is only the backup files saved to the /var/adm/sw/patch directory that are removed by the cleanup utility. - HP recommends that PHCO_19549 be removed from systems on which it is installed. If you choose not to remove PHCO_19549, do not use cleanup to trim the SD log files. - The previous patch for the cleanup utility, PHCO_12140, does not exhibit these same problems. PHCO_12140 will be re-released until a replacement patch is available. The replacement patch, PHCO_20824, should be released by the end of January. Hardware Platforms - OS Releases: s700: 10.00 10.01 10.09 10.10 10.16 10.20 10.24 10.30 s800: 10.00 10.01 10.09 10.10 10.16 10.20 10.24 10.30 Products: N/A Filesets: SW-DIST.SD-CMDS Automatic Reboot?: No Status: General Superseded With Warnings Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHCO_19549 Symptoms: PHCO_19549: - The 'cleanup' command lists patches to be removed from /var/adm/sw/patch when they have already been removed. SR: 5003422576 / CR: JAGaa61124 - The 'cleanup -F' command removes necessary IPD information for non-superseded patches from the /var/adm/sw/patch directory. SR: 8606103359 / CR: JAGab15340 PHCO_12140: - Patches applicable to previous software releases still show up in swlist(1M) output after software is updated. - Patches can be installed in the incorrect order if both superseded patches and their replacements are available from the source depot. Also, both the superseded and replacement patches will be displayed in the output of the swlist(1M) command after the installation completes. PHCO_5400: Old patches take up disk space unnecessarily. Defect Description: PHCO_19549: - The 'cleanup' command reported any patch directory that started with a percent sign (%) as a candidate for removal, even if the backup files in the directory hade already been removed. SR: 5003422576 / CR: JAGaa61124 Resolution: - Before reporting a patch directory as a candidate for removal, check to see if the backup files have already been removed. - The 'cleanup -F' command removed the entire contents of all patch directories under /var/adm/sw/patch. It should preserve the IPD information for non-superseded patches so that it can be restored if a superseding patch is installed and removed in the future. SR: 8606103359 / CR: JAGab15340 Resolution: - Create a semaphore in the patch directories under /var/adm/sw/patch for all non-superseded patches so that the IPD information is not removed along with the backup files. PHCO_12140: - The software product installation process does not have any knowledge of which patches should be removed from the SD-UX Installed Product Database (IPD) when a product is updated. The cleanup utility now has an option to update the patch information in the IPD. This cleanup function should be executed whenever software is installed, reloaded, or updated on a system. - If superseded patches and their replacements are installed from a common source during the same swinstall(1M) session all the patches will be installed. The control functions implemented in the control script embedded in the patch depot can not function correctly if the patches are installed concurrently. The cleanup utility now has an option to remove superseded patches from a software depot if the replacement patches are also available in the same depot. PHCO_5400: The cleanup tool is being provided to cleanup patches on customer systems as well as truncate SD log files. SR: 5003422576 8606103359 Patch Files: /usr/sbin/cleanup /usr/share/man/man1m.Z/cleanup.1m what(1) Output: /usr/sbin/cleanup: $Revision: 3.0 (PHCO_19549)$ $Date: 99/08/23$ /usr/share/man/man1m.Z/cleanup.1m: None cksum(1) Output: 2751684984 30906 /usr/sbin/cleanup 1692333969 2088 /usr/share/man/man1m.Z/cleanup.1m Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_5400 PHCO_12140 Equivalent Patches: None Patch Package Size: 90 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 PHCO_19549 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_19549.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHCO_19549. 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 PHCO_19549.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/PHCO_19549.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: This patch is intended for standalone systems only. The cleanup script included in this patch has not been modified to work correctly on NFS diskless cluster servers.