sd.5 (2011 03)

s
sd(5) sd(5)
SD also has a nonprivileged mode that replaces ACL authorizations with user file permissions. See the
run_as_superuser
default option and the Software Distributor Administration Guide for more infor-
mation.
Flexible Policy Control
You can control many policies and behaviors for the SD commands by using the command default options .
You can define these options in system-wide or user-specific SD defaults files, specify them on the
command-line when you invoke a command, or specify selected options in the GUI. See the Default
Options heading below for more information.
Preview, Diagnostics and Logging
All commands except
swlist and swjob log major events on the controller host and detailed events on
the target hosts.
If both source and target machine are running HP-UX version 11.00 or later, the system administrator at
the source depot machine can track which user pulls which software from a depot on the source machine
and when the software is pulled. Refer to the swagent (1M)
source_depot_audit
option for more
information.
You can use the SD interactive interface (invoked using the
sd command) and the swjob command line
interface to monitor job progress and to view controller and target log files.
The
swconfig, swcopy, swinstall, swmodify, swpackage, and swremove commands support a
preview mode, where the commands will proceed through the analysis phase, then exit.
Software Products
Software products are organized in a multi-level hierarchy: bundles , products , subproducts , and filesets .
The actual files that make up a product are packaged into filesets. The software_selections for an SD
command can specify bundles, products, individual subproducts, and/or individual filesets.
Compatible Software
Software products specify what machine types and operating systems they support (that is, are compati-
ble with). The
swconfig, swinstall, and swverify commands can detect and/or enforce the use of
compatible software.
Vendor-Defined Attributes
You can create your own software attributes when packaging software. Keywords in a product
specification file that are not recognized by SD are preserved, along with their associated values, by being
transferred to the resulting INDEX or INFO files created by
swpackage or swcopy. (Refer to swpack-
age(4) for more information on INDEX and INFO files.)
Vendor-defined attributes are noted during packaging or when modified with
swmodify. These attri-
butes can be listed with
swlist.
Dependencies Between Software
The
swask, swconfig, swcopy, swinstall, swremove, and swverify commands support depen-
dencies , which is software that must be present or absent before or during the installation of another
piece of software. Dependencies apply between filesets and other filesets and products. SD supports
three types of dependencies: prerequisites that must be installed and configured before the dependent
fileset is installed and configured (respectively); corequisites that must be installed and configured before
the dependent is usable. exrequisites that prevent a dependent fileset from being installed or configured
when they are present.
If a software_selection specifies a dependency on other filesets and/or products, the commands will
automatically select that software. An exception is
swremove, which can automatically select dependent
software (filesets and/or products that depend on the software_selections).
By default, all dependencies must be resolved before a command will proceed.
Note that if you specify a dependency for a fileset and the fileset is superseded by another fileset as part
of a patch, SD still recognizes the dependency.
Product Location and Multiple Versions
The
swinstall command can install a software product to an alternate product location instead of the
default product directory specified by the vendor. (This directory location is the root directory of all the
product’s files.)
HP-UX 11i Version 3: March 2011 − 3 − Hewlett-Packard Company 3