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

mode, and (depending on the umask of other users) can read local source depots created by
other users in nonprivileged mode.
Setting Up Nonprivileged Mode
Nonprivileged SD is controlled by two options:
• admin_directory
• run_as_superuser
The run_as_superuser option turns nonprivileged mode on or off and is all that is necessary
to run the default configuration. (See “Turning On Nonprivileged Mode” (page 225) and “Default
Configuration” (page 226).)
The admin_directory option lets you set up an alternative configuration. (See “Alternative
Configuration” (page 226).)
Packaging Software for Use in Nonprivileged Mode
In addition to these options, software applications to be used under nonprivileged mode have
special packaging requirements.
For nonprivileged mode to function:
• You must package applications and install them so that the files are installed in locations
writable by the user who will install the applications. This can be done by:
◦ Using the directory keyword in the PSF during packaging
◦ By appending a location to the software specifications when you invoke a command
from the command line. (See “Software Selections” (page 35).)
• Scripts packaged into the application must be designed not to require super-user privilege.
Turning On Nonprivileged Mode
SD functions in nonprivileged mode only when the run_as_superuser option is set to false and
the invoking user is not super-user.
This option applies to all SD-UX commands except swagent, swagentd, swjob, and install-sd. When
you set this option to false, any command to which it applies will run in nonprivileged mode. For
example:
• Including -x run_as_superuser=false on the command line invokes nonprivileged
mode for that command only.
• Including -x run_as_superuser=false in your $HOME/.swdefaults directory invokes
nonprivileged mode for any or all SD-UX commands that you run.
• Including -x run_as_superuser=false in /var/adm/sw/defaults invokes
nonprivileged mode for all SD-UX commands on the system.
See Appendix A (page 227) for complete information on using these options.
NOTE: This option is ignored (treated as true) when the invoking user is super-user.
How Nonprivileged Mode Changes SD-UX Behavior
When the run_as_superuser option is set to the default value of true, SD-UX operations are
performed normally, with permissions for operations either granted to a local super-user or set by
SD ACLs. (See Chapter 9: “SD-UX Security ” (page 141) for details on ACLs.)
Setting Up Nonprivileged Mode 225