Patch Management User Guide for HP-UX 11.x Systems (5900-3011, April 2013)
Table Of Contents
- Patch Management User Guide for HP-UX 11.x Systems
- Contents
- 1 HP-UX patches and patch management
- 2 Quick start guide for patching HP-UX systems
- 3 HP-UX patch overview
- 4 Patch management overview
- Patch management life cycle
- HP service contracts
- Patch management and software change management strategies
- Establishing a software change management strategy
- Recommendations for software change management
- Consideration of HP patch rating
- Patch management and software depots
- Proactive patching strategy
- Reactive patching strategy
- Advanced topic: security patching strategy
- Advanced topic: scanning for security patches
- Testing the patches to be installed
- 5 What are standard HP-UX patch bundles?
- 6 Using the HP Support Center
- Obtaining an HPSC user account
- Useful pages on the HPSC
- Find individual patches
- Advanced topic: checking for special installation instructions
- Advanced topic: checking for all patch dependencies
- Standard patch bundles
- Custom patch bundles - run a patch assessment
- Support information digests
- Ask your peers in the forums
- Search knowledge base
- 7 Using software depots for patch management
- Common software distributor commands for patching
- Depot types
- Using depots
- Viewing depots
- Creating and adding to a directory depot
- Registering and unregistering directory depots
- Verifying directory depots
- Removing software from a directory depot
- Removing a directory depot
- Installing patches from a depot
- Custom patch bundles
- 8 Using HP-UX Software Assistant for patch management
- 9 Using Dynamic Root Disk for patch management
- 10 The Patch Assessment Tool
- 11 Support and other resources
- A Patch usage models
- Glossary
- Index
Patch state
A patch that has been installed on a target system is assigned an attribute called patch_state
that provides information about a patch. For example, the patch_state tells you whether the
patch has been committed or superseded. For more information about attributes, see “Patch-related
attributes” (page 30).
There are four values for patch_state:
• applied
The patch is currently active on the system and is the most recent member of its supersession
chain to have been loaded.
• committed
The patch's rollback files have been deleted, or the patch was installed without saving rollback
files. The patch cannot be directly removed from the system. For more information about patch
rollback, see “Patch rollback and commitment” (page 34).
• superseded
The patch has been superseded by another patch that has been installed on the system. The
patch is no longer active. For more information about supersession, see “Ancestors and
supersession” (page 26).
• committed/superseded
The patch has been committed and superseded by another patch installed on the system.
IMPORTANT: For HP-UX 11.0 systems, you must install patch PHCO_22526 or a superseding
patch for proper functionality regarding the committed/superseded patch_state.
Use the following SD-UX commands to determine patch_state values:
• Show the patch_state value for patch patch_id by entering this command:
swlist -l fileset -a patch_state patch_id
• Show the patch_state values for all patches on the local system by entering this command:
swlist -l fileset -a patch_state *,c=patch
For more information regarding the swlist command, see “Which patches are on a system?”
(page 22).
State
Filesets (patch and nonpatch) have an attribute called state that indicates the current installation
state of a fileset. During installation, software is transitioned through the following states:
transient, installed, and configured. During removal, software is transitioned through
these states: configured, installed, and transient.
An SD-UX operation leaves a fileset in one of the following states:
• installed
Software has been successfully installed but not yet configured.
• configured
Software has been successfully installed and configured. No further operations are required.
20 HP-UX patch overview