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

-C session_file Run the command and save the current option and operand values
to a session_file for re-use in another session. See “Session Files”
(page 39).
-f software_file Read a list of software selections from a separate file instead of (or
in addition to) the command line. See “Software Files” (page 36).
-S session_file Run the command based on values saved from a previous installation
session, as defined in session_file. See “Session Files”
(page 39).
-s source Use the software source specified by source instead of the default,
/var/spool/sw. The syntax is: [host:][/directory] |
[./relative_path] | [../relative_path]
host may be a host name, domain name, or internet address (for
example, 15.1.48.23). directory is 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.
-x option=value Sets a command option to value and overrides default values
or a values in options files. See “Changing Command Options ”
(page 222).
-X option_file Read session options and behaviors from option_file. See
“Changing Command Options ” (page 222).
software_selections The software objects for which the request script will be executed.
See “Software Selections” (page 35).
target_selections The target of the command. See “Target Selections” (page 37).
Changing Command Options
You can change the behavior of this command by specifying additional command-line options
when you invoke the command (using the -x option) or by reading predefined values from a file.
The following table shows the options and default values that apply to swask.
Table 52 swask Command Options and Default Values
• log_msgid=0• admin_directory=/var/adm/sw
• •ask=true logdetail=false
•• logfile=/var/adm/sw/swask.logautoselect_dependencies=true
• •autoselect_minimum_dependencies=false loglevel=1
•• lookupcache_timeout_minutes=10autoselect_patches=true
• •enforce_scripts=true patch_filter=*.*
•• run_as_superuser=trueinstalled_software_catalog=products
• verbose=1
For More Information
See Appendix A (page 227) for complete descriptions of each default.
Request Script Tasks and Examples
You can run request scripts from the swinstall or swconfig commands by setting the ask
option to true. This tells the commands to run request scripts (if any exist) in addition to performing
install or configuration tasks. (Note that the value of the ask option if false for both swinstall
and swconfig but is true for swask.)
222 Using Control Scripts