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
Target Selections
Target selections follow software and source depot selections. If no target selection is named, the
target on which the operation will be performed is assumed to be the root (/) directory on your
local host. So, you do not have to use the @ sign and [host][:][/directory] designation
(described below) if you are operating on the local host or default depot directory.
Syntax
The target_selections syntax is identical for all SD-UX commands that require it:
@ [host][:][/directory] | [./relative_path] | [../relative_path]
• The @ character is optional if you are using the local host and default directory. If it is used,
it acts as a separator between operands and the destination.
• Only one @ character is needed.
• You can specify the host by its host name, domain name, or internet address. A directory can
either be an absolute pathname, 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 internet address can be 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 ].
• 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 \@.
Target Files
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 current working directory) contains a list
of target selections for the swinstall command.
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]
Using Command Options
You can control many SD-UX command policies and behaviors by setting the appropriate command
options. You can change the default values of options using predefined files or values you specify
directly on the command-line. Altering default values with files can help when you don’t want to
specify command behavior every time you invoke the command.
These rules govern the way the defaults work:
1. Options in /var/adm/sw/defaults affect all SD-UX commands on that system. This file
can change the default behavior for all commands to which an option applies or for specific
commands only.
2. Options in your personal $HOME/.swdefaults file affect only you and not the entire system.
Working from the Command Line 37