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
See Also
“Using Command Options” (page 37) for examples.
Options Listed Alphabetically
• admin_directory=/var/adm/sw (for normal mode) admin_directory=/var/home/LOGNAME/sw
(for nonprivileged mode)
The location for logfiles and the default parent directory for the installed software catalog.
The default value is /var/adm/sw for normal operations.
For nonprivileged mode (that is, when the run_as_superuser default option is set to true):
◦ The default value is /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, HOME/my_admin resolves to the my_admin directory in your
home directory.
◦ If you set the value of the installed_software_catalog option to a relative path,
that path is resolved relative to the value of this option.
Nonprivileged mode is intended only for managing applications that are specially designed
and packaged. This mode cannot be used to manage the HP-UX operating system or patches
to it. For a full explanation of nonprivileged SD-UX, see Chapter 12: “Nonprivileged SD ”
(page 224).
See also the installed_software_catalog and run_as_superuser options.
Applies to all commands except swagent, swagentd, and install-sd.
• agent=/usr/lbin/swagent
This is the default location of the executable invoked to perform agent tasks.
Applies to swagentd.
• agent_auto_exit=true
Causes the target agent to automatically exit after execute phase, or after a failed analysis
phase. This is forced to false when the controller is using an interactive UI, or when -p (preview)
is used.
Enhances network reliability and performance.
The default is true. The target agent automatically exits when appropriate.
If set to false, the target agent does not exit until the controller explicitly ends the session.
Applies to swconfig, swcopy, swinstall, swremove, and swverify.
• agent_timeout_minutes=10000
Causes a target agent to exit if it has been inactive for the specified time.
You can use this default value to make target agents more quickly detect lost network
connections. RPC typically detects lost connections very quickly, but it can take as long 130
minutes to detect a lost connection. The recommended value is the longest period of inactivity
expected in your environment.
For command line invocation, a value between 10 and 60 minutes is suitable. More than 60
minutes is recommended when you use the GUI.
The default is 10,000 minutes, slightly less than seven days.
Applies to swcopy, swinstall, swlist, swremove, and swverify.
228 Command Options