Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)
Table Of Contents
- Software Distributor Administration Guide
- Contents
- HP secure development lifecycle
- About This Document
- 1 Introduction to Software Distributor
- SD-UX Overview
- SD-UX Concepts
- Using the GUI and TUI Commands
- The Terminal User Interface
- Starting the GUI/TUI Commands
- Window Components
- Opening and closing items in the object list
- Marking Items in the Object List
- Preselecting Host Files
- Software Selection Window
- Session and File Management—The File Menu
- Changing Software Views—The View Menu
- Changing Options and Refreshing the Object List—The Options Menu
- Performing Actions—The Actions Menu
- Getting Help—The Help Menu
- XToolkit Options and Changing Display Fonts
- Working from the Command Line
- 2 Installing Software
- Installation with swinstall
- Features and Limitations
- Installing with the GUI
- Installing from the Command Line
- Installation Tasks and Examples
- Updating to HP-UX 11i
- Installing Patches
- Recovering Updated Files
- Installing Software That Requires a System Reboot
- Using Software Codewords and Customer IDs
- Re-installing Software Distributor
- Installing Multiple Versions
- Installing to an Alternate Root
- Compatibility Filtering and Checking
- Software Selection Checking
- Configuring Your Installation (swconfig)
- Verifying Your Installation (swverify)
- Installation with swinstall
- 3 Managing Installed Software
- 4 Managing Software Depots
- Depot Management Commands and Concepts
- Copying Software Depots
- Registering and Unregistering Depots (swreg)
- Verifying Signed Software Signatures
- Additional Depot Management Tasks and Examples
- Combining Patch Depots
- Creating a Tape Depot for Distribution
- Setting Depot Attributes
- Creating a Network Depot
- Managing Multiple Versions of HP-UX
- Listing Registered Depots
- Listing the Contents of a Depot (swlist -d)
- Source Depot Auditing
- Verifying a Depot (swverify -d)
- Removing Software from Depots
- Removing a Depot
- 5 HP-UX Patching and Patch Management
- 6 Using Jobs and the Job Browser
- 7 Remote Operations Overview
- 8 Reliability and Performance
- 9 SD-UX Security
- 10 Creating Software Packages
- Overview of the Packaging Process
- Identifying the Products to Package
- Adding Control Scripts
- Creating a Product Specification File (PSF)
- Product Specification File Examples
- PSF Syntax
- PSF Object Syntax
- Selecting the PSF Layout Version
- PSF Value Types
- Product Specification File Semantics
- Re-Specifying Files
- Packaging the Software (swpackage)
- Packaging Tasks and Examples
- Registering Depots Created by swpackage
- Creating and Mastering a CD-ROM Depot
- Compressing Files to Increase Performance
- Packaging Security
- Repackaging or Modifying a Software Package
- Packaging In Place
- Following Symbolic Links in the Source
- Generating File Revisions
- Depots on Remote File Systems
- Verifying the Software Package
- Packaging Patch Software
- Writing to Multiple Tapes
- Making Tapes from an Existing Depot
- 11 Using Control Scripts
- Introduction to Control Scripts
- General Script Guidelines
- Packaging Control Scripts
- Using Environment Variables
- Execution of Control Scripts
- Execution of Other Commands by Control Scripts
- Control Script Input and Output
- File Management by Control Scripts
- Testing Control Scripts
- Requesting User Responses (swask)
- Request Script Tasks and Examples
- 12 Nonprivileged SD
- A Command Options
- B Troubleshooting
- Error Logging
- Common Problems
- Cannot Contact Target Host’s Daemon or Agent
- GUI Won’t Start or Missing Support Files
- Access To An Object Is Denied
- Slow Network Performance
- Connection Timeouts and Other WAN Problems
- Disk Space Analysis Is Incorrect
- Packager Fails
- Command Logfile Grows Too Large
- Daemon Logfile Is Too Long
- Cannot Read a Tape Depot
- Installation Fails
- swinstall or swremove Fails With a Lock Error
- Use of Square Brackets ([ and ]) Around an IPv6 Address Causes an Error
- Some SD commands do not work after network configuration changes
- C Replacing or Updating SD-UX
- D Software Distributor Files and File System Structure
- Glossary
- Index
To preview the remove of the C and Pascal products installed at the local host:
swremove -p cc pascal
To remove a particular version of HP Omniback:
swremove Omniback,l=/opt/Omniback_v2.0
To remove the entire contents of a local depot:
swremove -d * @ /var/spool/sw
Removing Bundles
Removing a bundle does not always remove all filesets in that bundle. Because of SD-UX’s
dependency management features, a fileset that is required by another bundle will not be removed.
For example, if the bundles Pascal and FORTRAN both use the fileset Debugger.Run and you
try to remove FORTRAN, the fileset Debugger.Run will not be removed because it is also used
by the bundle Pascal. This prevents the removal of one bundle from inadvertently causing the
removal of a fileset needed by another bundle.
Removing Patches
You cannot remove patch software unless:
• Rollback files corresponding to the patch are available for re-installation.
— or —
• The base software modified by the patch is removed at the same time. (Removing the base
software also removes the patches associated with that software.)
For more information on removing patches, see Chapter 5: “HP-UX Patching and Patch
Management” (page 102).
Removing Multiple Versions
The swremove GUI can help simplify removal of multiple versions of a product.
Each separate version of a product along with its location directory is listed in the object list.
Selecting a multiple version implies a product:/location directory pair. By default, the
location is not displayed in the Software Selection Window. It can be displayed using the GUI
Columns Editor View→Columns... menu item and enabling the Product Directory menu item.
You can select more than one version of a product during the selection phase. During analysis, a
warning is generated if the version of the product exists on the target but at a different location. If
the product exists on the target, it will be removed. If it does not exist on the target, the product is
simply skipped. The Product Summary... button in the Remove Analysis Window gives a
product-by-product summary of what will be removed if the remove phase is started.
(Multiple versions of products are inherently possible in a depot. No special handling or checks
are required when removing from depots.)
Removing Software from an Alternate Root
Software can be removed relative to the primary root directory (/) or relative to an alternate root
directory. An alternate root is a non-root location that can function as the root of a stand-alone
system; that is, a system that can be unmounted and function as a self-contained system. Any
information files used in software removal are retrieved from the Installed Product Database (see
“Installed Products Database ” (page 21)) beneath this alternate root, not the IPD on the root
volume.
82 Managing Installed Software