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

Syntax
Software and source depot selections are followed by target selections. These operands are
separated by the “@” (at) character. This syntax implies that the command operates on selections
at targets.
The target_selections syntax is identical for all Software Distributor commands that require
it:
@ [host][:][/directory] | [./relative_path] | [../relative_path]
• Only one @ character is needed.
• You can specify the host by its host name, domain name, or internet address. A directory must
be specified by an absolute path or a relative pathname. If a host is specified, the directory
must be an absolute path. To specify a relative_path when no host is specified, the
relative_path must start with ./ or ../; otherwise, the specified name is considered as
a host.
• The : (colon) is required if you specify both a host and directory.
• On some systems, the @ character is used as the kill function. Type stty on your system to
see if the @ character is mapped to any other function on your system. If it is, remove the
mapping, change the mapping, or use \@.
NOTE: On HP-UX 11i v3, the internet address can also be specified in the IPv6 format. When
IPv6 internet address is specified, it can be optionally enclosed within square brackets [ and ].
Target Files
You can also use an input file to specify targets. To keep the command line shorter, target selection
input files let you specify long lists of targets. With a target selection file, you only have to specify
the single file name.
The -t command-line option lets you specify a target file. For example:
swinstall -f mysoft -s /mnt/cd -t mytargs
In this example, the file mytargs (which resides in the default directory) contains a list of target
selections for the depot /mnt/cd.
In the target file, blank lines and comments (lines beginning with #) are ignored. Each target
selection must be specified on a separate line and must consist of a host name or network address,
optionally followed by a colon and a full path:
host[:/directory]
NOTE: The host can be an internet address either in IPv4 format with dot notation or in IPv6
format. When IPv6 internet address is specified, it can be optionally enclosed within square brackets
[ and ].
Examples
swacl
To list the global product template ACL on remote host gemini:
# swacl -l global_product_template @ gemini
If 3ffe:ffff:101::230:6eff:fe04:d9ff is the IPv6 address of gemini, then the global
product template ACL on the remote host gemini can also be listed with the following command:
# swacl -l global_product_template @ 3ffe:ffff:101::230:6eff:fe04:d9ff
130 Remote Operations Overview