HP-UX Software Assistant Administration Guide (5900-3003, March 2013)

As each patch is downloaded into the swcache, a notice is displayed on standard output.
.
.
.
* Downloading Software from HP to Local Cache
NOTE: Estimated total download size: x bytes.
* Downloading PHCO_n (1 of x)
.
.
.
Once the patches have been downloaded to the swcache directory, they are processed into the
depot. SWA automatically uses MD5 cryptographic hash to verify patch integrity before unpacking
downloaded patches. For more information on the location of the swcache directory, see
Appendix A (page 43).
Read the readBeforeInstall.txt file and take appropriate actions
The readBeforeInstall.txt is located in the target depot directory.
This file lists special installation instructions and dependencies to take under consideration for all
the patches downloaded from HP. Review this file before installing the depot.
Install the depot
The recommended method to install HP-UX patches and patch bundles from a depot is with the
command:
# swinstall -s depot -x patch_match_target=true -x autoreboot=true
Note that this command should only be used within a maintenance window as the system might
require a reboot. Any reboot will be performed automatically when required.
Generate a second report
It is useful to compare a post-SWA report with the initial report to see the issues that have been
resolved and those still requiring resolution. Make sure you save the original report before running
the following command:
# swa report -x inventory_max_age=0 -X <my_conf_file>
The inventory_max_age=0 is a special value that forces an inventory file update.
Put appropriate actions in the ignore file
It might make sense for you to ignore the following types of issues:
• Manual actions — SWA can't detect if security bulletin manual actions (other than installing
specific versions of patches or software) have been taken, so after applying a manual action,
add it to the ignore file to track that the action has been taken.
• Deferred actions — If you've made a decision to defer addressing a particular issue for some
period of time, after taking into account the risk of not addressing it, you might wish to add
it to the ignore file until the issue is revisited or fixed. Be careful not to forget about these types
of issues, since SWA will stop warning about them.
HP advises you include comments in the ignore file explaining who added an issue, why, and
when. Auditors are likely to want this information documented and traceable.
The ignore file, $HOME/.swa/ignore, includes comments with instructions regarding syntax and
how to add an issue. You must use the Issue ID given in the Detail report to identify issues in an
ignore file.
It is possible to use more than one ignore file with the following syntax:
# swa report -x ignore_file="file1 file2"
Read the readBeforeInstall.txt file and take appropriate actions 13