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
Verifying Your Installation (swverify)
The swverify command verifies depot, installed, or configured software products on the specified
host.
Features and Limitations
• Determines whether installed or configured software is compatible with the host on which that
software is installed.
• Makes sure that all dependencies (prerequisites, corequisites) are being met (for installed
software) or can be met (for copied software).
• Executes verification scripts that check the correctness of the product’s configuration (that is,
scripts verify that the installed state of the software is configured).
• Executes fix scripts to correct or report problems with installed software:
Corrects and reports on problems in installed software. Typical uses are to create
missing directories, correct file modifications (mode, owner, group, major, minor),
and to recreate missing symbolic links.
Fix
Verify Verifies the configuration of filesets or products, in addition to the standard swverify
checks.
(See Chapter 11: “Using Control Scripts ” (page 201) for more information.)
• Reports missing files, checks all file attributes including permissions, file types, size, checksum,
mtime, link source and major/minor attributes.
• Uses dependencies to automatically select software on which to operate (in addition to any
software you specify directly). See “Software Dependencies ” (page 22) for more information.
The Verification Process
The software verification process has only two phases: selection and analysis.
Phase I: Selection
This phase consist of swverify resolving all information on the command line, including all necessary
host, software, dependency, and product information.
The swverify behavior can be controlled by the enforce_selections option. If set to false
(default), swverify proceeds even when only one software selection is available in the source.
If set to true, swverify proceeds only if all of the software selections are available.
Phase II: Analysis
The analysis phase for swverify takes place on the host. The host’s environment is not modified.
The sequential analysis tasks on each host are:
1. Initiate analysis
2. Process software selections. The system accesses the Installed Products Database (IPD) or depot
catalog to get the product information for the selected software:
For installed software, the system checks that all products are compatible with its uname
attributes. This check is controlled by the default option allow_incompatible:
• If allow_incompatible is set to false, the system produces an error stating that the
product is not compatible with the host.
• If allow_incompatible is set to true, a warning is issued stating that the product is
not compatible.
Verifying Your Installation (swverify) 57