The dupatch utility is provided as an interactive and command-line tool for working with Patch kits. The following sections provide an overview of dupatch and describe the procedure for installing the most current version.
If you are familiar with dupatch but have not installed one or more of the most recent patch kits, you may want to review the installation changes that were introduced in those kits as described in Appendix D “Prior Patch Installation Changes”t.
All Tru64 UNIX and TruCluster software Release Patch Kits are installed, removed, and managed using the setld-based dupatch utility, which provides you with menus that step you though the various tasks.
The dupatch utility is also used for installing many of the Customer-Specific Patch Kits (CSPs) , and Early Release Patch Kits (ERPs) . Although the examples and descriptions provided in this manual, in general, refer to Release Patch Kits, the information is similar for CSPs and ERPs that install using dupatch.
The dupatch utility is interactive, but you can also run it from the command line using command options. For information about using the command-line interface, see Appendix C “Using dupatch from the Command Line”, which includes the dupatch(8) reference page.
For clustered systems running TruCluster dupatch is run in conjunction with the rolling upgrade (see “Rolling Upgrade”) or no-roll (see “No-Roll Patching”) procedures.
With dupatch, you can perform the following actions:
Install and remove patches.
View patch tracking and management information.
Track current dupatch-installed patches and Customer-Specific patches.
Establish a baseline for systems that had manually installed system files placed on them.
Ensure the correct handling of customized system configuration files so that customizations are not lost (for example, conf.c). These files are also referred to as system-protected files (.new..).
Validate patch applicability to existing system files (collision detection).
View the patch-specific documentation.
Because dupatch manages patch interdependencies, direct setld installations (setld -l) and deinstallations (setld -d) are disabled.
Most dupatch operations generate log files that record the step-by-step procedures performed during the operation. For information about log files see Appendix A “Viewing Log files”.
Invoking dupatch and Installing New Patch Tools
After you have made the patch kits available to the system being patched, run dupatch from root or you can change directories to patch_kit, which contains the dupatch utility:
From the patch_kit directory:
# cd /patches/pk4/patch_kit
If new patch tools are available they will be loaded and you will see messages similar to the following:
* A new version of patch tools required for patch management
is now being installed on your system.
* Tools updated, invoking the updated Patch Utility...
The dupatch utility saves information on the tools that have been loaded to the log file /var/adm/patch/log/Dupatch_load_date.log. (See Appendix A “Viewing Log files” for information about log files.)
After the new tools have been loaded, dupatch prompts you for the path to the patch kit files. After you specify the path (or press Return if the patch kit is in your current directory) you will see the main menu. For example:
Enter path to the top of the patch distribution,
or enter "q" to get back to the menu : /patches/pk4/patch_kit
Tru64 UNIX Patch Utility (Rev. 48-00)
- This dupatch session is logged in /var/adm/patch/log/session.log
1) Patch Kit Installation
2) Patch Kit Deletion
3) Patch Kit Documentation
4) Patch Tracking
5) Patch Baseline Analysis/Adjustment
h) Help on Command Line Interface
Enter your choice: