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

swcopy does not automatically notify you when multiple versions of a product exist. swcopy only
notifies you when an exact version exists and will be skipped (or recopied)
Registering and Unregistering Depots (swreg)
To make the software in a depot available for use across a network by other SD-UX commands,
you must register the depot. You can also unregister a depot if you do not want it to be available.
Depots are registered or unregistered in these ways:
• The swcopy command automatically registers newly created depots. (You can turn this function
on or off with the register_new_depot option.)
• The swremove command automatically unregisters a depot after removing all the software the
depot contains.
• The swreg command explicitly registers or unregisters depots.
The swreg command lets you explicitly register or unregister depots when the automatic registration
features of swcopy or swremove are not enough. For example, you can use swreg to:
• Make a CD-ROM or other media available as a registered depot.
• Register a depot that was created with swpackage.
• Unregister a depot to restrict network access without physically removing the depot from a
host.
Register Media or Create Network Depot?
When does it make sense to use your software media as a registered depot versus using the media
to create a network depot? In general, using media as a depot makes sense for small-scale use,
such as when only one or two other systems need to access the media. If more systems will need
to access the media, performance will be better if you create a network depot from the individual
media. See “Additional Depot Management Tasks and Examples” (page 97) for an example.
Registration and Security
Because SD-UX stores its objects in the file system, someone could build a “Trojan Horse” file system
image of a software depot. This could breech the security of any system that installed products
from the false depot. To protect systems from such a situation, SD-UX requires that depots be
registered before software may be installed or copied from it. This check is always performed
before granting access, except when swinstall is run by the local superuser.
NOTE: Registration of a depot does not enforce any access restrictions. Access enforcement is
left to SD security (see Chapter 9: “SD-UX Security ” (page 141)). Registration with swreg requires
insert permission in the host’s ACL.
Authorization
To register a new depot or to unregister an existing depot, swreg requires read permission on
the depot in question and insert permission on the host. To unregister a registered depot, the swreg
command requires write permission on the host. See Chapter 9: “SD-UX Security ” (page 141) for
more information on permissions.
Using swreg
swreg Syntax
swreg -l level [-u] [-v] [-C session_file] [-f object_file]
[-S session_file] [-t target_file] [-x option=value]
[-X option_file] [objects_to_register] [@ target_selections]
Registering and Unregistering Depots (swreg) 93