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
Recursive File Specification
The file * keyword directs swpackage to include every file (and directory) within the current
source directory in the fileset. swpackage attempts to include the entire, recursive contents of the
source directory in the fileset. (Partial wildcarding is not supported, e.g. file dm* to indicate all
files starting with “dm”.)
All attributes for the destination file object are taken from the source file, unless a
file_permission keyword is active (this keyword is described below).
The user can specify multiple
directory source[=destination]
file *
pairs to gather all files from different source directories into a single fileset.
If you do not want to recursively include all files and directories, use the explicit file specification.
The directory keyword must have been previously specified before the file * specification
can be used. If not, swpackage generates an error.
Error Messages
When processing the directory recursively, swpackage encounters the following errors:
• Cannot search directory (permission denied)
• Cannot read the file (permission denied)
• Unsupported file type encountered
PSF Extensions
A PSF can contain extended file definitions. SD currently supports exclude and include files.
Exclude files let you explicitly exclude files that would otherwise be included in the PSF. The syntax
is:
exclude filename
An exclude file can only be specified after a file definition. The file listed after the exclude keyword
is excluded from the current context (for example, from a recursive file definition or wildcard).
If the filename specifies a directory, then all files below that directory are excluded.
Include files let you include file definitions from a separate file. The syntax is:
file < filename
The include file must be separated from the file keyword by a less than sign (<).
Re-Specifying Files
In addition to being able to specify files as a group (with file *) for general attributes, the PSF
also allows you to “re-specify” files within that definition to modify individual attributes.
For example, suppose you wanted to specify all the files in a fileset which contained 100 files. All
these files were to be recursively “discovered” and packaged into the fileset. Most of them would
have the same owner, group, and mode (and other file attributes).
Out of those 100 files, there might be five that are volatile (that is, you don’t care if they get
modified or deleted). So, instead of listing all 100 files individually, and using the -v option for
the five, you could specify all 100 with file * and then modify the five individually in their own
way. For example, with files 1, 2, 3, 4, and 5:
directory source = /product file *
file -v 1
file -v 2
file -v 3
188 Creating Software Packages