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_directory
See distribution_target_directory.
• target_tape
See distribution_target_serial.
• target_type
See media_type.
• uncompress_cmd=
This is the command called by the source agent to uncompress files when installing, copying
or packaging.
This command processes files that were stored on the media in compressed format. If the
compression_type of the file is gzip, the internal compression (funzip) is used instead
of the external uncompress command.
Applies to swagent and swpackage.
• uncompress_files=false
When set to true, files are uncompressed using the current uncompress_cmd before storing
them on the target depot.
Only one of the uncompress_files and compress_files options may be set to true
during a swpackage session.
The uncompress_files option may not be set to true if package_in_place is set to true
or if the media_type is set to tape.
Applies to swcopy and swpackage.
• use_alternate_source=false
At the default value of false, swinstall or swcopy begins an analysis or task with a request
that includes information describing the source binding and depot path for the local host to
use as the software source.
If true, the local host uses its own configured value. On the local host, the agent’s configured
value for alternate_source is specified in host:/path format. If this value contains only
a path component (for example, alternate_source=:/path), the agent applies this path
to the file system of its own local host.
If only the host component exists (for example, alternate_source=host), the agent applies
the controller-supplied path to this host. If there is no configured value at all for the
alternate_source, the agent applies the controller-supplied path to its own local host.
Applies to swcopy and swinstall.
• verbose=
By default, the command sends output to stdout for task summary messages. Alternatively,
the verbose option can be set to 0 for session level messages (no output to stdout) or (for
swpackage and swmodify) to 2 for file level messages.
Error and warning messages are always written to stderr.
For the swlist command, a verbose listing includes all attributes that have been defined for
the appropriate level of each software_selection operand. The attributes are listed one
per line, prefaced by the attribute keyword.
The -v option overrides this default, if it is set to 0.
Applies to all commands.
• verify_signatures=false
If set to true, swverify verifies the signatures as well as dependencies, missing files, file attributes,
permissions, timestamps, checksum, etc. This option is applicable only to directory depot
verification.
Options Listed Alphabetically 251