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
/usr/sbin/swagentd -k
You can also kill and restart a currently running daemon by typing:
/usr/sbin/swagentd -r
Cannot Read a Tape Depot
If you are trying to access a tape depot and see the following error message in the daemon logfile,
it means that the tape is either corrupt or is not in SD-UX format.
ERROR: The INDEX file on the source did not exist or could
not be read.
ERROR: The target <depot_path> could not be opened.
Resolution
Make sure that you have correctly specified the tape device and that the correct tape is in the
drive. SD-UX only reads tapes that are in SD-UX format. For example, SD-UX does not read update
format tapes.
Installation Fails
An installation may fail while only part way through the process.
Resolution
SD-UX gives you several restart options:
• Re-execute the same command from the command line.
• Recall the session file swinstall.last that was automatically saved for you. (See “Session
Files” (page 39).)
• Reset the checkpointing options.
By default, SD-UX checkpoints to the fileset level, meaning that the operation will start
transferring files with the last fileset to be attempted. By setting the reinstall_files option
to false, SD-UX restarts distribution and installation with the file that was last attempted. (SD-UX
does not support checkpointing below the file level.)
You can override all checkpointing by setting both the reinstall and reinstall_files
options to true. See Appendix A (page 227) for more information.
swinstall or swremove Fails With a Lock Error
swinstall or swremove fails with the following message:
Cannot lock “/” because another command holds a conflicting lock.
The process id of that command is ####.
Resolution
Another SD command is running that prevents the swinstall or swremove command from
running. Wait for that command to finish and try again.
Use of Square Brackets ([ and ]) Around an IPv6 Address Causes an Error
Commands such as swinstall, swlist, and so on used with IPv6 address enclosed in square
brackets, fail with an error.
For example:
swlist @ [2620:0:a07:e020:21a:4bff:fef3:90e8], fails with the following error:
# Initializing...
ERROR: Could not contact host "a". Make sure the hostname is correct
and an absolute pathname is specified (beginning with "/").
260 Troubleshooting