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

A Command Options
This appendix reviews the basics of altering SD-UX command options and provides an alphabetic
list of all options and their default values.
Table 54 Chapter Topics
Topics:
“Changing Command Options” (page 227)
“Options Listed Alphabetically” (page 228)
Changing Command Options
Changing the option values lets you change command behavior and tailor SD-UX policies to your
needs. You can change options using predefined files, values you specify directly on the
command-line, or the GUI Options Editor from the Options menu. Altering option values using files
can help when you don’t want to specify command behavior every time you invoke the command.
These rules govern the way the options work:
• Option values specified in /var/adm/sw/defaults affect all SD-UX commands on that
system. This file can change options for all commands to which an option applies or for specific
commands only.
• Option values in your personal $HOME/.swdefaults file affect only you and not the entire
system.
• Option values read from a session file affect only that session.
• Options changed on the command line by the -X option_file or the -xoption=value
arguments override the system-wide and personal defaults files but affect only that invocation
of the command.
For system-wide policy setting, use the /var/adm/sw/defaults files. Keep in mind, however,
that users may override these values with their own $HOME/.swdefaults file, session files, or
command line changes.
The template file /usr/lib/sw/sys.defaults provides documentation for all options, and
contains instructions for an easy way to change system-wide or personal default files.
The template file documents as comments all SD-UX command options, the commands to which
they apply, their possible values, and the resulting system behavior. You can copy values from this
file into the system defaults file (/var/adm/sw/defaults), your personal defaults file ($HOME/
.swdefaults), or an input file and uncomment them to affect your system behavior.
Option files use the syntax:
[command.]option=value
• The optional command is the name of a SD-UX command. Specifying a command name
changes the default behavior for that command only. A period must follow a command name.
• option is the name of the default option. An equals sign must follow the option name.
• value is one of the allowable values for that option.
NOTE: Use caution when changing default option values. They allow useful flexibility but can
produce harmful results if changed to a value that is inappropriate for your needs.
NOTE: Options in the defaults file are read as part of command initialization. Because the
daemon is already running, you must restart the daemon after changing daemon options for the
system to recognize those options. To restart the daemon, type:
/usr/sbin/swagentd -r
Changing Command Options 227