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
An explicit file specification uses this form:
file [-v] [-m mode] [-o [owner[,]][uid]] [-g [group[,]][gid]]
[-t type] [source] [destination]
file This keyword specifies an existing file (usually within the currently
active source directory) to include in the fileset.
source This value defines the path to a file you want to include in the
package.
If this is a relative path, swpackage will search for it relative to the
source directory set by the directory keyword. If no source
directory is active, swpackage will search for it relative to the current
working directory in which the command was invoked.
All attributes for the destination file object are taken from the source
file, unless a file_permission keyword is active, or the -m, -o,
or -g options are also included in the file specification.
destination This value defines the destination path at which the file will be
installed. If destination is a relative path, the active destination
directory set by the directory keyword will be prefixed to it. If it is a
relative path, and no destination directory is active, swpackage
generates an error. If the destination is not specified, then the source
path is used as the destination, with the appropriate mapping done
with the active destination directory (if any).
-m mode This option defines the (octal) mode for a file or directory at its
destination.
-o [owner[,]][uid] This option defines the file’s owner name and/or uid at its destination.
If only the owner is specified, then the owner and uid attributes are
set for the destination file based on the packaging host’s /etc/
owner. If only the uid is specified, it is set as the destination’s uid
attribute and no owner name is assigned. If both are specified, each
sets the corresponding attribute for the file object.
On systems that support numeric usernames, to specify a numeric
username for owner, both the numeric username and the uid must
be supplied. If a numeric username alone is specified, it is interpreted
as a uid.
During an installation, the owner attribute is used to set the owner
name and uid, unless the owner name is not specified or is not
defined in the target system’s /etc/passwd file. In this case, the
uid attribute is used to set the uid.
-g [group[,]][gid] This option defines the file’s group name and/or gid at its destination.
If only the group is specified, then the group and gid attributes are
set for the destination file based on the packaging host’s /etc/
group. If only the gid specified, it is set as the destination’s gid
attribute and no group name is assigned. If both are specified, each
sets the corresponding attribute for the file object.
On systems that support numeric groupnames, to specify a numeric
groupname, both the numeric groupname and the gid must be
supplied. If a numeric groupname alone is specified, it is interpreted
as a gid.
During an installation, the group attribute is used to set the group
name and gid, unless the group name is not specified or is not defined
186 Creating Software Packages