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
When run_as_superuser is set to false and the invoking user is local and is not super-user,
nonprivileged mode is invoked:
• Permissions for operations are based on the user’s file system permissions.
• SD ACLs are ignored.
• Files created by SD have the uid and gid of the invoking user, and the mode of created files
is set according to the invoking user’s umask.
Default Configuration
The default configuration of nonprivileged mode is to have a central location for user-installed
software catalogs.
When the run_as_superuser option is false and the admin_directory option is not set,
SD-UX logfiles and installed software catalogs are stored in user-specific directories at /var/home/
USER_NAME/sw (where USER_NAME is replaced by the invoking user name).
Putting logfiles and installed software catalog in a central location avoids problems when users
install software on the system outside of their home directories and user home directories are NFS
mounted across many systems.
You can enable nonprivileged mode for all users by setting the run_as_superuser option to
false in /var/adm/sw/defaults.
Individual users can override the default chosen by the system administrator, by setting the
run_as_superuser option to true or false in their $HOME/.swdefaults file or on the command
line.
Alternative Configuration
An alternative configuration of nonprivileged mode sets up user-installed software catalogs in each
user’s home directory. You can use the admin_directory option in /var/adm/sw/defaults
to indicate a path beginning with HOME or /HOME, so that the default administration directory used
by SD-UX during nonprivileged mode is in each user’s home directory. (A value of HOME/.sw
works well for this purpose.)
Individual users can override this in their $HOME/.swdefaults file or on the command line.
Setting the Admin Directory Option
This option lets you specify the location for logfiles and the default parent directory for the installed
software catalog. Values are as follows:
admin_directory=/var/adm/sw (for normal mode)
admin_directory=/var/home/LOGNAME/sw (for nonprivileged mode)
The default value is /var/adm/sw for normal operations. For nonprivileged mode (that is, when
the run_as_superuser option is set to true):
• The default value is forced to /var/home/LOGNAME/sw.
• The path element LOGNAME is replaced with the name of the invoking user, which SD-UX reads
from the system password file.
• If you set the value of this option to HOME/path, SD-UX replaces HOME with the invoking
user’s home directory (from the system password file) and resolves path relative to that directory.
For example, if you specified HOME/my_admin for this options, the location would resolve
to the my_admin directory in your home directory.
This option applies to swinstall, swcopy, swremove, swconfig, swverify, swlist,
swreg, swacl, swpackage, swmodify.
226 Nonprivileged SD