|
» |
|
|
|
NAMEsd — Software Distributor, commands to create, distribute, install, monitor, and manage software SYNOPSISsw<command>
[XToolkit Options]
[-r|-d]
[-i]
[-l]
[-p]
[-R]
[-u]
[-v]
[-V]
[-a
attribute]
[-c
catalog]
[-C
session_file]
[-D
acl_entry]
[-f
software_file]
[-F
acl_file]
[-J
jobid]
[-l
level]
[-M
acl_entry]
[-Q
date]
[-s
source]
[-S
session_file]
[-t
target_file]
[-x
option=value]
[-X
option_file]
[software_selections]
[@
target_selections] RemarksYou can enable Software Distributor (SD) for software management
on remote systems. See the
Remote Operation
section below for details. Type
man 4 sd
to view the
sd(4)
manual entry for descriptions of all SD objects, attributes and data
formats. Type
man 4 swpackage
to view the
swpackage(4)
manual entry for description of the Product Specification File (PSF)
used as input to the
swpackage
command.
DESCRIPTIONSee the
Software Distributor Administration Guide,
available at
http://docs.hp.com
for a complete description of SD. The SD command and related programs:
sd
- Lets you interactively create, schedule, and monitors software jobs
and log files. Also lets you launch the install, copy, and remove
commands. swacl
- Modifies Access Control Lists (ACLs), which control SD security. swagentd
- Daemon that serves local or remote SD software management tasks and
starts the SD agent. swask
- Runs scripts that request user responses to be used in software
installation or configuration. swcluster
- Configures diskless clients (HP-UX 10.X only). swconfig
- Configures, unconfigures, or reconfigures installed software. swcopy
- Copies software products into depots for subsequent installation or
distribution. swinstall
- Installs and configures software products. swjob
- Creates and monitors software jobs and log files. swlist
- Displays information about software products. swmodify
- Modifies software product information in a target root or depot. swpackage
- Packages software products into a distribution directory or
serial-format depot. swreg
- Registers or unregisters software depots or roots. swremove
- Removes and unconfigures software products. swverify
- Verifies software products. install-sd
- Retrieves and installs the SD product (and any related patches) from
new media.
The following sections highlight the features that these commands
support. Remote OperationYou can enable Software Distributor (SD) to manage software on remote
systems. To let the root user from a central SD
controller
(also called the
central management server or manager node)
perform operations on a remote
target
(also called the
host or agent):
- 1)
Set up the root, host, and template Access Control Lists (ACLs) on the
remote machines to permit root access from the controller system. To do
this, run the following command on each remote system: /usr/lib/sw/mx/setaccess controller NOTES:
controller
is the name of the central management server. If remote system is 11.00, make sure SD patch PHCO_22526 or a
superseding patch is installed on remote system before running
setaccess. If remote system is older than 11.00 or for some other
reason does not have
setaccess
in place, copy the
setaccess
script from an
11.11 or higher system to the remote system.
- 2)
swinstall,
swcopy, and
swremove
have enhanced GUI interfaces for remote operations. Enable
the enhanced GUIs by creating the
.sdkey
file on the controller. Use this command: touch /var/adm/sw/.sdkey
NOTE: You can also set up remote access by using the
swacl
command directly on the remote machines to grant root or non-root
access to users from the controller system. Interactive OperationBy default, all SD commands except
sd
and
swask
operate in a non-interactive mode. The
swcopy,
swinstall,
swlist,
and
swremove
commands also support a graphical user interface (GUI). (If your
terminal or display cannot support the GUI, these commands also
provide a terminal user interface, in which screen navigation is done
with the keyboard and no mouse.) To invoke the GUI, enter the command without any command-line options
or add the
-i
option with other command-line options when you invoke the
command. You
must
specify the
-i
option to invoke the
swlist
GUI. The
swconfig
and
the command-line version of
swinstall
work interactively when the
ask
option is set to
true.
This option executes an interactive
request script. The
sd
command is an interactive interface for monitoring and scheduling
software jobs. It provides the same functionality as the
swjob
command. You can also use
sd
to invoke the
swinstall,
copy,
and
swremove
GUIs. If you have enabled SD's remote operations features,
swinstall,
swcopy, and
swremove
provide enhanced GUIs to support operations on remote targets. See
Remote Operation
above for details about enabling remote operations and the enhanced GUIs. Distributed OperationAll SD commands except
swask,
swpackage,
and
swmodify
use a distributed model of operation. The commands act as the
controller for distributed operations, managing the specific software
management tasks. For each
target_selection,
an SD agent process performs the task:
swagent
- perform software management tasks as the agent of an SD command.
Communication between the command and each agent, plus other target
host activities are facilitated by an SD daemon process:
swagentd
- serve local or remote software management tasks.
Software Job ManagementThe
swinstall, copy, and remove
commands create job information that records the job definition (in a
session file), status, and log information for the job. You can
execute jobs immediately, or schedule them for later execution. You
can browse the scheduled, active, and completed jobs using either the
swjob
command or the
sd
interactive interface. Secure OperationSD uses Access Control Lists (ACLs) to authorize users attempting to
create, modify, or read software products in a depot or installed to a
root file system. The superuser can grant specific local and remote
users specific access permissions to a target host, a target depot,
and/or a target root file system. (Note that SD does not use ACLs for
tasks invoked by a local root user.) Because files are loaded and scripts are run as superuser, granting
write permission (to install software) on a root file system or insert
permission (to create a new root) on a host, effectively gives the
user superuser privileges. SD uses a method based on credentials and passwords to authenticate
the user and the SD command performing a given operation. 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 information. Flexible Policy ControlYou 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 LoggingAll 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 ProductsSoftware 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 SoftwareSoftware products specify what machine types and operating systems
they support (i.e. are compatible with). The
swconfig,
swinstall,
and
swverify
commands can detect and/or enforce the use of compatible software. Vendor-Defined AttributesYou 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
swpackageor
swcopy.
(Refer to
swpackage(4)
for more information on INDEX and INFO files.) Vendor-defined attributes are noted during packaging or when modified
with
swmodify.
These attributes can be listed with
swlist. Dependencies Between SoftwareThe
swask,
swconfig,
swcopy,
swinstall,
swremove,
and
swverify
commands support
dependencies,
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 VersionsThe
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.) The
swinstall
command can also install multiple versions of
a software product to a single target system, each in a unique
product location. The software management commands,
swconfig,
swlist,
swremove,
and
swverify
let you select a specific product from the multiple installed versions
by specifying the product location as part of the
software_selection. Alternate Root Directory and Depot DirectoryBy default, the
swinstall,
swlist,
swmodify,
swremove,
and
swverify
commands operate on the primary root file system of a target host,
(/").
These commands let you specify an alternate root directory using
the
@ target_selection
syntax and the
-r
command-line option. (This option is not required and is maintained
primarily for backward compatibility.) NOTES:
Alternate root directories are root file systems other than the
default primary root
(/).
(The alternate root directory will eventually become the root of a
target host.) Operations on alternate root directories do not include
compatibility filtering. Configure, unconfigure, and verify scripts are not run for
operations on alternate root directories. You cannot use this option to relocate software during
installation. You must use the
l=location
syntax in the software selection component. Alternate root operations are not the equivalent of a
chroot
command.
Alternate roots provide advantages for some test environments (such as
building a test system by mounting its root file system). You can also
use them to quickly get files from a depot onto your system for
viewing or other purposes. When operating on a depot, the
swcopy,
swpackage,
swlist,
swverify,
swremove,
and
swverify
commands by default use the depot located at
/var/spool/sw.
You can also specify an alternate depot directory to these commands. Disk Space AnalysisThe
swcopy,
swinstall,
and
swpackage
commands perform a disk space analysis on the
target_selections
to ensure that enough free disk space is available to perform the
task. When packaging software, you can define
space files
for filesets to define additional space needed. (Space files are
accounted for in disk space analysis.) Before performing any disk space analysis,
swcopy,
swinstall,
and
swpackage
(also
swverify
and
swremove)
execute the
mount(1M)
command to mount all file systems listed in each target's file system
table
(/etc/fstab
or equivalent). This ensures that files are not loaded into a
directory below a future mount point. You can override this mounting
policy using the
mount_all_filesystems
option. Control ScriptsThe
swask,
swconfig,
swinstall,
swremove,
and
swverify
commands can execute vendor-defined control scripts to perform checks
or other tasks beyond those usually performed by the commands. In general, SD uses scripts with product or fileset objects. Scripts
usually do not accompany software that HP manufactures onto new
systems in the factory. SD supports these types of scripts:
Checkinstall
- (Applies to
swinstall.)
A check script that analyses each
target_selection
(target host) for an installation to determine if the installation and
configuration can take place. Preinstall
- (Applies to
swinstall.)
A script executed immediately before installation of software files to
perform additional file install operations (such as removing obsolete
files). Unpreinstall
- (Applies to
swinstall.)
An "undo" preinstall script in case SD must initiate recovery during
the install process. Postinstall
- (Applies to
swremove.)
A script executed immediately after a fileset or product has been
installed to perform additional remove operations (such as resetting
default files). Unpostinstall
- (Applies to
swremove.)
An "undo" postinstall script in case SD must initiate recovery during
the installation process. Configure
- (Applies to
swconfig,
swinstall,
and
swremove.)
A script that configures installed filesets or products. Unconfigure
- (Applies to
swconfig
and
swremove.)
A script to "undo" configurations performed by configure scripts. Verify
- (Applies to
swverify.)
A script that verifies the configuration of filesets or products.
(The script performs these checks in addition to the standard
swverify
checks for file consistency with SD database entries.) Checkremove
- (Applies to
swinstall.)
A check script that analyses each
target_selection
(target host) before removal to determine if the removal and
unconfiguration can take place. Preremove
- (Applies to
swremove.)
A script executed immediately before removal of software files to
perform additional file operations (such as removing files created by
a preinstall script). Postremove
- (Applies to
swremove.)
A script executed immediately after a fileset or product has been
removed to perform additional remove operations (such as restoring
"rollback" files). Request
- (Applies to
swask,
swconfig,
and
swinstall.)
An interactive script that requests a response from the user as part
of the installation or configuration process. Other scripts
- You can include other specialized scripts as subscripts to standard
SD control scripts.
See the
Software Distributor Administration Guide
for more information on using control scripts. Software StatesThe SD commands transition products and filesets through a number of
states. During installation, software is transitioned through the following
states:
During removal, software is transitioned through these states:
When packaging or copying software into a depot, the software is
transitioned through the following states:
When removing software from a depot, the software is transitioned
through these states:
If a task fails during any TRANSIENT state, the state is set to
CORRUPT. OptionsThe following options are supported by one or more of the SD
commands. Refer to the manual pages for each command for the options
specific to that command. - XToolKit Options
The interactive commands support a subset of the standard X Toolkit
options to control the appearance of the GUI. The supported options
are:
-bg,
-background,
-fg,
-foreground,
-display,
-name,
-xrm.
and
-synchronous.
See the
X(1)
manual page for a definition of these options. - -d
Causes the command to operate on
target_selections
which are software depots rather than root directories. - -r
Causes SD commands to operate on alternate root directories, which
must be specified in the
@ target_selections
option. (This option is not required for alternate root operations but
is maintained for backward compatibility. See the
Alternate Root Directory and Depot Directory
heading above for more information.) - -i
Runs the command in interactive mode (Graphical User Interface). See
the
Interactive Operation
and
Remote Operation
headings above for additional details. - -l
(HP-UX 10.X only)
Runs the command in
linkinstall
mode, which makes software installed under a server's
shared root
available to a diskless client's
private root. When run in
linkinstall
mode,
swinstall:
Creates NFS mounts to the software to make it accessible from the target.
This may involve delayed mounting for alternate roots. Modifies the target's
fstab
file. Modifies the source's
exports
file to add mount permission for the target.
Mounts are created by examining the
share_link
product attribute.
Not all products support
linkinstall.
Some products may be visible without creating a new mount if they
reside under an existing one. - -p
Previews the task by executing the session through the analysis phase
and exiting before the command begins to perform the actual task. - -R
For
swlist,
recursively includes all objects to the fileset level. For
swjob:
recursively includes all objects to the
end_target
level. - -u
Undo variation of the operation, unconfiguring software using
swconfig,
unregistering the specified objects using
swreg,
or removing the specified jobs using the
swjob
command. - -v
Turns on verbose output to stdout. (The command log file is not affected
by this option.) By default, verbose output is enabled for all the SD
commands. - -V
List the supported data model revisions. - -a attribute
Specifies particular attributes to display or modify using
swlist,
swmodify,
or the
swjob
command. - -c catalog
Specifies the pathname of the directory containing an exported
catalog. For
swask,
this catalog stores copies of the response files created by request
scripts. For
swlist
and
swmodify,
this catalog stores output or input for these commands. - -C session_file
Saves the current options and operands to
session_file.
(You can recall a session file with the
-S
session_file
option.) See the
Session File
heading in this manpage for more information. - -D acl_entry
Deletes an existing entry from the ACL associated with the
specified objects using
swacl. - -f software_file
Read the list of
selections
from
software_file
instead of (or in addition to) the command line operands. - -F acl_file
Assigns the ACL contained in
acl_file
to the specified object
using
swacl. - -J job_id
Executes the previously scheduled job. This option is used by the
swagentd
to initiate scheduled jobs. - -l level
List all objects at the specified
level
when using
swlist,
or define the level of the objects when using
swacl,
or
swreg. - -M acl_entry
Adds a new ACL entry or changes the permissions of an existing entry
using
swacl. - -Q date
Schedules the command for the specified date and time. - -s source
Specifies source depot, PSF file, or tape from which software will be
installed, copied, listed, or packaged. (SD can read both
tar
and
cpio
tape depots.) - -S session_file
Executes the command based on the options and operands saved from a
previous session in
session_file.
(You can save session information to a file with the
-C
session_file
option.) See the
Session File
heading in this manpage for more information. - -t target_file
Read the list of
target_selections
from
target_file
instead of (or in addition to) the command line operands. - -x option=value
Set the session
option
to
value
and override the default value (or a value in an alternate
option_file
specified with
the
-X
option).
Multiple
-x
options can be specified. - -X option_file
Read the session options and behaviors from
option_file.
These values defined in this file override the default values.
OperandsMost SD commands support two types of operands:
software selections
followed by
target selections.
These operands are separated by the "at"
(@)
character. This syntax implies that the command operates on
"selections at targets". Software SelectionsThe
selections
operands consist of
software_selections
for most SD commands.
For the
swjob
and
swreg
commands, the selections can be
job_ids
and
roots_or_depots
respectively. The SD commands support the following syntax for each
software_selection:
bundle[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
The
=
(equals) relational operator lets you specify selections
with the following
shell wildcard and pattern-matching notations:
For example, the following expression installs all bundles and
products with tags that end with "man":
swinstall -s sw_server *man
Bundles
and
subproducts
are recursive.
Bundles
can contain other
bundles
and
subproducts
can contain other
subproducts.
For example:
swinstall bun1.bun2.prod.sub1.sub2.fset,r=1.0
or (using expressions):
swinstall bun[12].bun?.prod.sub*,a=HP-UX
The
\*
software specification selects all products. Use this specification
with caution.
The
version
component has the form:
[,r <op> revision][,a <op> arch][,v <op> vendor]
[,c <op> category][,q=qualifier][,l=location]
[,fr <op> revision][,fa <op> arch]
location
applies only to installed software and refers to software installed to
a location other than the default product directory. fr
and
fa
apply only to filesets. r
,
a
,
v
,
c
, and
l
apply only to bundles and products. They are applied to the
leftmost bundle or product in a software specification. The
<op>
(relational operator) component can be of the form:
=,
==,
>=,
<=,
<,
>,
or
!=
which performs individual comparisons on dot-separated fields. For example,
r>=B.11.00
chooses all revisions greater than or equal to
B.11.00.
The system compares each dot-separated field to find
matches. Shell patterns are not allowed with these operators. The
=
(equals) relational operator lets you specify selections
with the following
shell wildcard and pattern-matching notations:
For example, the expression
r=1[01].*
returns any revision in version 10 or version 11. All version components are repeatable within a single specification (e.g.
r>=A.12,
r<A.20).
If multiple components are used, the selection must match all
components. Fully qualified software specs
include the
r=,
a=,
and
v=
version components even if they contain empty strings. For installed
software,
l=
is also included. No space or tab characters are allowed in a software selection. The software
instance_id
can take the place of the version component. It has the form:
within the context of an exported catalog, where
instance_id
is an integer that distinguishes versions of products and bundles with
the same tag.
Target SelectionsThe SD commands support this syntax for each
target_selection.
The colon
(:)
is required if both a host and directory are specified. EXTERNAL INPUTS AND INFLUENCESDefault OptionsIn addition to the standard options, several SD behaviors and policy options
can be changed by editing the default values found in:
- /var/adm/sw/defaults
the system-wide default values. - $HOME/.swdefaults
the user-specific default values.
Values must be specified in the defaults file using this syntax: [command_name.]option=value The optional
command_name
prefix denotes one of the SD commands. Using the prefix limits the
change in the default value to that command. If you leave the prefix
off, the change applies to all commands. You can also override default values from the command line with the
-x
or
-X
options: command -x option=value
command -X option_file The following section lists all of the keywords supported by the SD
commands. The keywords that are supported for individual commands are
also listed in each command's manual page. If a default value exists,
it is listed after the
=.
The commands that this option applies to
are also specified. - admin_directory=/var/adm/sw (for normal mode)
- admin_directory=/var/home/LOGNAME/sw (for nonprivileged mode)
The location for SD logfiles and the default parent directory for the
installed software catalog. The default value is
/var/adm/sw
for normal SD operations. When SD operates in nonprivileged mode
(that is, when the
run_as_superuser
default 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 reads from
the system password file. If you set the value of this option to
HOME/path,
SD 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
default option to a relative path, that path is resolved relative to
the value of this option.
SD's 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, see the
Software Distributor Administration Guide,
available at the
http://docs.hp.com
web site. See also the
installed_software_catalog
and
run_as_superuser
options. Applies to all SD commands except
swagent,
swagentd,
and
install-sd. - agent=/usr/lbin/swagent
The location of the agent program invoked by the daemon. 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. This enhances network reliability and performance.
The default value of
true
means the target agent automatically exits when appropriate. When set to
false,
the target agent will not exit until the controller ends the session. Applies to
swconfig,
swcopy,
swinstall,
swremove,
swverify. - agent_timeout_minutes=10000
Causes a target agent to exit if it has been inactive for the
specified time. This can be used to make target agents more quickly
detect lost network connections since RPC can take as long as 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 minutes and 60 minutes is
suitable. A value of 60 minutes or more is recommended when the GUI
will be used. The default of 10000 is slightly less than 7 days. Applies to
swcopy,
swinstall,
swjob,
swlist,
swremove,
swverify. - allow_downdate=false
Prevents the installation of an older revision of fileset that already
exists at the targets. (Many software products do not support
"downdating".) If set to
true,
the older revision can be installed. Applies to
swinstall. - allow_incompatible=false
Requires that the software products which are being installed be
"compatible" with the target selections. (All of the target selections
must match the list of supported systems defined for each selected
product.) If set to
true,
target compatibility is not enforced. Applies to
swconfig,
swinstall,
and
swverify. - allow_multiple_versions=false
Prevents the installation or configuration of another, independent
version of a product when a version already is already installed or configured
at the target. If set to
true,
another version of an existing product can be installed into a new
location, or can be configured in its new location. Multiple versions
can only be installed if a product is locatable. Multiple configured
versions will not work unless the product supports it. Applies to
swconfig,
swinstall,
and
swverify. - allow_split_patches=false
Permits the use of single patch filesets without "sibling" filesets.
In the default state of
false,
installation, copy, or removal of a single fileset from a
multi-fileset patch automatically includes any other fileset that are
part of the patch, based on the ancestor filesets of the target
fileset. (This behavior applies to filesets selected directly by the
user and to filesets automatically selected by SD to resolve software
dependencies.) When set to
true,
SD allows a single patch fileset to be installed, copied, or removed
without including the sibling filesets. This allows a target to
contain a patch that has been "split" into its component filesets.
WARNING: Splitting a patch can create a situation in which one fileset
in a sibling group would be updated or removed by a patch, while the
other filesets would remain at an earlier release or fail to be
removed. Applies to
swinstall, swcopy, and swremove. - alternate_source=
Defines the alternate source which the agent will use
when the
use_alternate_source
option is set to
true.
The alternate source is specified using the syntax:
If the host portion is not specified, then the local
host is used. If the path portion is not specified, then the path
sent by the command is used.
The protocol sequence and endpoint given by the option
swagent.rpc_binding_info
are used when the agent attempts to contact an alternate source depot. Applies to
swagent. - ask=true (swask only)
- ask=false (swconfig and swinstall)
Executes a
request script,
which asks for a user response. If
ask=as_needed,
swinstall
executes the request script only if a response file does not already
exist in the control directory. See
swask(1M)
for more information on request scripts. Applies to
swask,
swconfig,
and
swinstall. - auto_kernel_build=true
Normally set to true. Specifies whether the removal of a kernel
fileset should rebuild the kernel or not. If the kernel rebuild succeeds,
the system automatically reboots. If set to false, the system
continues to run the current kernel. If the
auto_kernel_build
option is set to
true,
the
autoreboot
option must also be set to
true.
If the
auto_kernel_build
option is set to
false,
the value of the
autoreboot
option does not matter. Applies to
swremove
only. - autoreboot=false
Prevents the installation or removal of software requiring a reboot
from the non-interactive interface. If set to
true,
then software can be installed or removed, after which the target
system(s) will automatically reboot. An interactive session always asks for confirmation before software requiring
a reboot is installed or removed. If the
auto_kernel_build
option is set to
true,
the
autoreboot
option must also be set to
true.
If the
auto_kernel_build
option is set to
false,
the value of the
autoreboot
option does not matter. Applies to
swinstall
and
swremove. - autorecover=false
This option permits automatic recovery of original filesets if an
installation error occurs. The cost is a temporary increase in disk
space and slower performance. The default value of
false
causes
swinstall
to remove the original files as a fileset is updated. If an error
occurs during the installation (e.g. network failure), then the
original files are lost, and you must reinstall the fileset. If set to
true,
all files are saved as backup copies until the current fileset
finishes loading. If an error occurs during installation, the
fileset's original files are replaced, and
swinstall
continues to the next fileset in the product or the product
postinstall
script. When set to
true,
this option also affects scripts. For example, if a
preinstall
script fails, this option causes the corresponding
unpreinstall
script to execute. See the
Software Distributor Administration Guide
for complete information. Applies only to
swinstall. - autorecover_product=false
This option permits automatic recovery of original product files if an
installation error occurs. The cost is a temporary increase in disk
space and slower performance. The default value of
false
causes
swinstall
to remove any existing product files as a product is updated. If an
error occurs during installation (e.g. network failure), then the
original files are lost, and you must reinstall the product. If set to
true,
all files for a product are saved as backup copies until the entire
product finishes loading. Then the files are removed. If an error
occurs during installation, the original product files are replaced,
and
swinstall
exits. When set to
true,
this option also affects scripts. For example, if a
preinstall
script fails, this option causes the corresponding
unpreinstall
script to execute. See
Software Distributor Administration Guide
for complete information. Applies only to
swinstall. - autoremove_job=false
Controls automatic job removal of completed jobs. If the job is
automatically removed, job information (job status or target log files)
cannot be queried with
swjob. - autoselect_dependencies=true
Controls the automatic selection of prerequisite, corequisite, and
exrequisite software that SD automatically selects.
When set to
true,
the requisite software is automatically selected for configuration.
When set to
false,
requisite software which is not explicitly selected is not
automatically selected for configuration.
When set to
as_needed,
autoselected dependencies are operated only if the dependency is not
already met on the target. Applies to
swconfig,
swcopy,
swinstall,
and
swverify. - autoselect_dependents=false
Controls whether or not SD automatically selects dependent software.
A dependent fileset has established either a prerequisite,
corequisite, or exrequisite on the selected fileset. Specifying
true
causes SD to automatically select dependent software. The default
value of
false
prevents SD from automatically selecting dependent software. Applies to
swconfig
and
swremove. - autoselect_patches=true
Automatically selects the latest patches (based on superseding
and ancestor attributes) for a software object that a user selects for a
swinstall
or
swcopy
operation. When set to
false,
the patches corresponding to the selected object will not be
automatically selected. The
patch_filter
option can be used in conjunction with
autoselect_patches. Applies to
swask,
swinstall,
and
swcopy. - autoselect_reference_bundles=true
If
true,
bundles that are
sticky
will be automatically installed, or copied, along with the software it is
made up of.
If
false,
the software can be installed, or copied, without automatically including
sticky
bundles that contain it. For
swremove,
if set to
true,
any bundle with the is_sticky attribute
set to true is removed automatically
when the last of its contents is removed.
If set to
false,
the sticky bundles will not be automatically removed. Applies to
swcopy,
swinstall,
and
swremove. - check_contents=true
Causes
swverify
to verify the time stamp, size, and checksum attributes of files.
If set to
false,
these attributes are not verified. Applies to
swverify. - check_contents_uncompressed=false
(This option is ignored if
check_contents
is set to
false.)
Controls whether or not
swverify
validates the size and checksum
for compressed files. In the default state of
false, swverify
checks only the mtime, size and cksum attributes of the compressed
file. If set to
true, swverify
uncompresses the file in memory and verifies the size and cksum
attributes of the uncompressed contents. Only files compressed with SD's internal compressor can be
uncompressed during a
swverify
operation. See the
compress_files
option of the
swpackage(1M)
command for more information. Applies to
swverify. - check_contents_use_cksum=true
(This option is ignored if
check_contents
is set to
false.)
Controls whether or not
swverify
computes a checksum on the contents of the file. In the default state
of
true,
swverify
checks all file attributes including the checksum. If set to
false,
swverify
checks only the file timestamp and size. Applies to
swverify. - check_permissions=true
Causes
swverify
to verify the mode, owner, UID, group, and GID attributes of
installed files.
If set to
false,
these attributes are not verified. Applies to
swverify. - check_requisites=true
Causes
swverify
to verify that the prerequisite, corequisite, and exrequisite
dependencies of the software selections are being met. If set to
false,
these checks are not performed. Applies to
swverify. - check_scripts=true
Causes
swverify
to run the fileset/product verify scripts for installed software.
If set to
false,
these scripts are not executed. Applies to
swverify. - check_volatile=false
Causes
swverify
to not verify those files marked as volatile (i.e. can be changed).
If set to
true,
volatile files are also checked (for installed software). Applies to
swverify. - codeword=
Provides the "codeword" needed to unlock protected HP CD-ROM software. Some HP software products are shipped on CD-ROM as "protected"
products. That is, they cannot be installed or copied unless a
"codeword" and "customer ID" are provided. The codeword is found on
the CD-ROM certificate which you received from HP. This option stores
the codeword for future reference; you needs to enter the codeword
only once. - compress_cmd=/usr/contrib/bin/gzip
Defines the command called to compress files
before installing, copying or packaging.
If the
compression_type
option is set to other than
gzip
or
compress,
this path must be changed. Applies to
swpackage
and
swagent. - compress_files=false
If set to
true,
uncompressed files are compressed before transfer from a source. This
enhances performance on slower networks for
swcopy
and
swinstall,
and results in smaller depots for
swcopy
and
swpackage,
unless the
uncompress_files
option is also set to
true. Applies to
swcopy,
swinstall,
and
swpackage. - compress_index=false
Determines whether SD commands create compressed INDEX and INFO
catalog files when writing to target depots or roots. The default of
false
does not create compressed files. When set to
true,
SD creates compressed and uncompressed INDEX and INFO files. The
compressed files are named
INDEX.gz
and
INFO.gz,
and reside in the
same directories as the uncompressed files. Compressed files can enhance performance on slower networks, although
they may increase disk space usage due to a larger Installed Products
Database and depot catalog. SD controllers and target agents for
HP-UX 11.01 and higher automatically load the compressed INDEX and
INFO files from the source agent when:
The source agent supports this feature. INDEX.gz
or
INFO.gz
exist on the source depot. INDEX.gz
or
INFO.gz
are not older than the corresponding uncompressed
INDEX or INFO files.
The uncompressed INDEX or INFO file is accessed by the source agent if
any problem occurs when accessing, transferring, or uncompressing the
INDEX.gz
or
INFO.gz
file. Applies to
swinstall, swcopy, swpackage,
swmodify, swconfig, and swremove. - compression_type=gzip
Defines the default compression type used by the agent when it compresses
files during or after transmission. If
uncompress_files
is set to false, the
compression_type
is recorded for each file compressed so that the
correct uncompression can later be applied during a
swinstall,
or a
swcopy
with
uncompress_files
set to true. The
compress_cmd
specified must produce
files with the
compression_type
specified. The
uncompress_cmd
must be able to process files of the
compression_type
specified unless the format is
gzip,
which is uncompressed by the internal uncompressor
(funzip). Applies to
swagent. - config_cleanup_cmd=/usr/lbin/sw/config_clean
Defines the script called by the agent to perform release-specific
configure cleanup steps. Applies to
swagent. Please Note: Transition links do not exist on 11.31 and newer
releases so there are no configure cleanup steps to perform therefore
the config_cleanup_cmd is never executed for these releases. - control_files=
When adding or deleting control file objects, this option lists the tags
of those control files. There is no supplied default.
If there is more than one tag, they must be separated by whitespace
and surrounded by quotes. Applies to
swmodify. - controller_source=
Specifies the location of a depot for the controller to access to
resolve selections. Setting this option can reduce network traffic
between the controller and the target. Use the target selection syntax
to specify the location:
This option has no effect on which sources the target uses and is
ignored when used with an Interactive User Interface. Applies to
swcopy,
swconfig,
swinstall,
swremove, and
swverify. - create_target_acls=true
If creating a target depot,
swpackage
will create Access Control Lists (ACLs) for the depot (if it is new)
and all products being packaged into it. If set to
false,
and if the user is the superuser,
swpackage
will not create ACLs. (The
swpackage
command never creates ACLs when software is packaged on to a
distribution tape.) Applies to
swpackage. - create_target_path=true
Causes the agent to create the target directory if it does not already
exist. If set to
false,
a new target directory will not be created. This option can prevent
the erroneous creation of new target depots. Applies to
swcopy
and
swinstall. - create_time_filter=0
For cumulative source depots, this option allows consistent software
selections over time by
swlist,
swcopy,
and
swinstall.
The default of zero includes all bundles, products, subproducts, and
filesets in the source depot as candidates for selection (and
autoselection of dependencies and patches), based on the software
selections and other options. When set to a time (specified as
seconds from epoch), only those bundles, products, and filesets (and
the subproducts in the product) with a create_time less than or equal
to the specified value are available for selection (or autoselection).
To list the create_time of bundles, products and filesets, use: swlist -a create_time -a create_date Applies to
swlist,
swcopy,
and
swinstall. - customer_id=
This number, printed on the Software Certificate, "unlocks" protected
software and restricts installation to a specific site or owner. You
can enter the number with the
-x
customer_id=
option or by using the Interactive User Interface. The
customer_id
can be used on any HP-UX 10.X or later system. Applies to
swinstall,
swcopy,
swlist. - defer_configure=false
Causes
swinstall
to automatically run configure scripts for the
software_selections
after they are installed. (Alternate root directories are not configured.) When set to true,
swinstall
does not run configure scripts. If you want to configure the software
later, you must run the
swconfig
command. NOTES:
Multiple versions of a product will not be automatically
configured if another version is already configured. Use the
swconfig
command to configure multiple versions separately. SD ignores this option when it installs software that causes a
system reboot.
Applies to
swinstall. - distribution_source_directory=/var/spool/sw
Defines the default location of the source depot (when the
source_type
is
directory).
You can also use the
host:path
syntax. The
-s
option overrides this default. Applies to
swcopy,
swinstall,
and
swpackage. - distribution_target_directory=/var/spool/sw
Defines the default distribution directory of the target depot.
The
target_selection
operand overrides this default. Applies to
swacl,
swcopy,
swlist,
swmodify,
swpackage,
swreg,
swremove,
and
swverify. - distribution_target_serial=/dev/rmt/0m
Defines the default location of the target tape device file.
The
target_selection
operand overrides this default. Applies to
swpackage. - enforce_dependencies=true
Requires that all dependencies specified by the
software_selections
be resolved either in the specified source, or at the
target_selections
themselves. The
swconfig,
swcopy,
and
swinstall
commands will not proceed unless the dependencies have also been
selected or already exist at the target in the correct state
(INSTALLED, CONFIGURED, or AVAILABLE). This prevents unusable
software from being installed on the system. It also ensures that
depots contain usable sets of software. For
swremove,
if a selected fileset has dependents (i.e. other software depends on
the fileset) and they are not selected, do not remove the selected
filesets. If set to
false,
dependencies are checked, but not enforced. Corequisite dependencies,
if not enforced, may keep the selected software from working
properly. Prerequisite or exrequisite dependencies, if not enforced,
may cause the installation or configuration to fail. Applies to
swconfig,
swcopy,
swinstall,
swremove,
and
swverify. - enforce_dsa=true
Prevents a command from proceeding past the analysis phase if the disk
space required is beyond the available free space of the impacted
file systems. If set to
false,
then the install, copy, or package operation will use the file systems'
minfree space and may fail
because it reaches the file system's absolute limit. Applies to
swcopy,
swinstall,
and
swpackage. - enforce_locatable=true
When set to the default value of
true,
this option generates an error if a command tries to relocate a
non-relocatable fileset. (Relocatable filesets are packaged with the
is_relocatable
attribute set to
true).
When set to
false,
the usual error handling process is overridden, and SD permits the
command to relocate the fileset. Note that although this option is defined for
swverify,
there is no behavior associated with the option. Applies to
swinstall
and
swverify. - enforce_kernbld_failure=true
The default value of true prevents
swinstall
from proceeding past the kernel build phase if the kernel build
processes fail. If set to
false,
the install operation continues despite failures or warnings in the
system preparation process or the kernel build process. Applies to
swinstall. - enforce_scripts=true
Controls the handling of errors generated by scripts. If
true,
and a script returns an error, the command halts, and an error message
appears reporting that the execution failed. If
false,
script-generated errors are treated as warnings, and the command
attempts to continue. A warning message appears and reports that the
command was successful. Where appropriate, the message identifies the
phase in which the error occurred (configure/unconfigure,
preinstall/postinstall, preremove/postremove, etc.). Applies to
swask,
swconfig,
swinstall
and
swremove. - files=
When adding or deleting file objects, this option lists the pathnames
of those file objects. There is no supplied default.
If there is more than one pathname, they must be separated by whitespace. Applies to
swmodify. - fix_explicit_directories=false
Controls the
swinstall
response to explicitly packaged software (software packaged with
explicit file specifications). The default value of
false
causes
swinstall
to set permissions (as specified in the product specification file) on
new directories but never on pre-existing directories. When set to
true, swinstall
also sets the permissions on pre-existing directories. Applies to
swinstall. - follow_symlinks=false
Do not follow symbolic links in the package source files, but include
the symbolic links in the packaged products. A value of
true
for this keyword causes
swpackage
to follow symbolic links in the package source files and include the
files they reference in the packaged products. Applies to
swpackage. - force_single_target=false
This option applies to HP-UX 10.X only.
This option applies only to the Interactive User Interface on a system
that is a diskless server. It causes
swremove
to run in a single target mode, even though a diskless server normally
causes
swremove
to run in multi-target mode. Applies to
swremove. - include_file_revisions=false
Do not include each source file's revision attribute in the products being packaged.
Because this operation is time consuming,
by default the revision attributes are not included.
If set to
true,
swpackage
will execute
what(1)
and possibly
ident(1)
(in that order) to try to determine a file's revision attribute. Applies to
swpackage. - install_cleanup_cmd=/usr/lbin/sw/install_clean
Defines the script called by the agent to perform release-specific install
cleanup steps immediately after the last postinstall script has been run.
For an OS update, this script should at least remove commands that were
saved by the
install_setup
script. This script is executed after all filesets have been
installed, just before the reboot to the new operating system. Applies to
swagent. Please Note: Transition links do not exist on 11.31 and newer
releases so there are no install cleanup steps to perform therefore
the install_cleanup_cmd is never executed for these releases. - installed_software_catalog=products
Defines the directory path where the Installed Products Database (IPD)
is stored. This information describes installed software. When set to
an absolute path, this option defines the location of the IPD. When
this option contains a relative path, the SD controller appends the
value to the value specified by the
admin_directory
option to determine the path to the IPD. For alternate roots, this
path is resolved relative to the location of the alternate root. This
option does not affect where software is installed, only the IPD
location. This option permits the simultaneous installation and removal of
multiple software applications by multiple users or multiple
processes, with each application or group of applications using a
different IPD. Caution: use a specific
installed_software_catalog
to manage a
specific application. SD does not support multiple descriptions of the
same application in multiple IPDs. See also the
admin_directory
and
run_as_superuser
options, which control SD's nonprivileged mode. (This 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,
see the
Software Distributor Administration Guide,
available at the
http://docs.hp.com
web site.) Applies to all SD commands except
swacl,
swask,
swconfig,
swinstall,
swlist,
swmodify,
swremove,
and
swverify. - install_setup_cmd=/usr/lbin/sw/install_setup
Defines the script called by the agent to perform release-specific install
preparation. For an OS update, this script should at least copy commands
needed for the checkinstall, preinstall, and postinstall scripts to a path
where they can be accessed while the real commands are being updated.
This script is executed before any kernel filesets are loaded. Applies to
swagent. Please Note: Transition links do not exist on 11.31 and newer
releases so there are no install setup steps to perform therefore
the install_setup_cmd is never executed for these releases. - job_title=
This is an ASCII string giving a title to a job. It is displayed
along with the job ID to provide additional identifying information
about a job when
swjob
is invoked. Applies to
swconfig,
swcopy,
swinstall,
swremove,
and
swverify. - kernel_build_cmd=/usr/sbin/mk_kernel
Defines the script called by the agent for kernel building. Applies to
swagent. - kernel_path=/stand/vmunix
Defines the path to the system's bootable kernel. This path is passed
to the
kernel_build_cmd
via the
SW_KERNEL_PATH
environment variable. Applies to
swagent. - layout_version=1.0
Specifies the POSIX
layout_version
to which the SD commands conform when writing distributions and
swlist
output. Supported values are "1.0" (default) and "0.8". SD for HP-UX
version 10.10 and later can read or write either layout version. SD object and attribute syntax conforms to the
layout_version 1.0
specification of the
IEEE POSIX 1387.2 Software Administration
standard. SD commands still accept the keyword names associated
with the older layout version, but you should use
layout_version=0.8
only to create distributions readable by older versions of SD. The version used by
swpackage
can be controlled by specifying the
layout_version
attribute in the product specification file (PSF). However, if the
layout_version
attribute in the PSF is 1.0, the
is_locatable
attribute defaults to true in all cases, and must be explicitly set to
false. (See
swpackage(4)
for more information on PSFs.) Layout version 1.0 adds significant functionality not recognized by
systems supporting only 0.8, including:
Category class objects (formerly the
category and category_title
attributes within the bundle or product class). Patch-handling attributes, including
applied_patches, is_patch, and patch_state. The fileset
architecture
attribute, which permits you to specify the architecture of the
target system on which the product will run.
In addition to adding new attributes and objects, layout_version 1.0
changes the following preexisting 0.8 objects and attributes as follows:
Replaces the depot
media_sequence_number
with the
media
object with a
sequence_number
attribute. Replaces the
vendor
definition within products and bundles with
a
vendor_tag
attribute and a corresponding
vendor
object defined outside the product or bundle. Pluralizes the
corequisite
and
prerequisite
fileset attributes (to
corequisites
and
prerequisites). Changes the
timestamp
attribute to
mod_time.
Applies to
swpackage,
swcopy,
swmodify,
and
swlist. - level=
Specifies a software
level
for
swlist,
swacl,
or
swreg. For
swlist: Lists all objects down to the specified
level.
Both the specified level(s) and the depth of the specified
software_selections
control the depth of the
swlist
output. The supported software levels are:
- bundle
Show all objects down to the bundle level. - product
Show all objects down to the product level. Also use
-l bundle -l product
to show bundles. - subproduct
Show all objects down to the subproduct level. - fileset
Show all objects down to the fileset level. Also use
-l fileset -l subproduct
to show subproducts and filesets. - file
Show all objects down to the file level (i.e. depots, products,
filesets, and files). - control_file
Show all objects down to the control_file level. - category
Show all categories of available software objects. - patch
Show all applied patches.
The supported depot and root levels are:
- depot
Show only the depot level (i.e. depots which exist at the specified target hosts). - root
List all alternate roots. - shroot
List all registered shared roots (HP-UX 10.X only). - prroot
List all registered private roots (HP-UX 10.X only).
For
swacl: The
level
option defines the level of ACLs to view or modify:
- host
View/modify the ACL protecting the host system(s) identified by the
target_selections. - depot
View/modify the ACL protecting the software depot(s) identified by the
target_selections. - root
View/modify the ACL protecting the root file system(s) identified by the
target_selections. - product
View/modify the ACL protecting the software product identified by the
software_selection.
Applies only to products in depots, not installed products in roots. - product_template
View/modify the template ACL used to initialize the ACL(s) of future
product(s) added to the software depot(s) identified by the
target_selections. - global_soc_template
View/modify the template ACL used to initialize the ACL(s) of future
software depot(s) or root file system(s) added to the host(s)
identified by the
target_selections. - global_product_template
View/modify the template ACL used to initialize the
product_template
ACL(s) of future software depot(s) added to the host(s) identified by
the
target_selections.
For
swreg: The
level
option defines the level of object to register or unregister:
- depot
Depots which exist at the specified target hosts. - root
All alternate roots. - shroot
All registered shared roots (HP-UX 10.X only). - prroot
All registered private roots (HP-UX 10.X only).
Applies to
swacl,
swlist,
and
swreg.
- log_msgid=0
Adds numeric identification numbers at the beginning of SD logfile
messages:
- 0
(default) No identifiers are attached to messages. - 1
Adds identifiers to ERROR messages only. - 2
Adds identifiers to ERROR and WARNING messages. - 3
Adds identifiers to ERROR, WARNING, and NOTE messages. - 4
Adds identifiers to ERROR, WARNING, NOTE, and certain other
informational messages.
Applies to
swconfig,
swcopy,
swinstall,
swmodify,
swpackage,
swreg,
swremove,
and
swverify. - logdetail=false
The
logdetail
option controls the amount of detail written to the log file. When set
to
true,
this option adds detailed task information (such as options specified,
progress statements, and additional summary information) to the
log file. This information is in addition to log information controlled
by the
loglevel
option. Here are the possible combinations of
loglevel
and
logdetail
options: Applies to
swconfig,
swcopy,
swinstall,
swreg,
swremove,
and
swverify. - logfile=/var/adm/sw/sw<command>.log
Defines the default log file for each SD command.
(The agent log files are always located relative to the target depot or
target root, e.g.
/var/spool/sw/swagent.log
and
/var/adm/sw/swagent.log.) Applies to all commands except
swacl,
swlist,
and
swjob. - loglevel=1
Controls the log level for the events logged to the command logfile,
the target agent logfile, and the source agent logfile by prepending
identification numbers to SD logfile messages. This information
is in addition to the detail controlled by the
logdetail
option. See
logdetail
for more information. A value of:
- 0
provides no information to the log files. - 1
enables verbose logging to the log files. - 2
enables very verbose logging to the log files.
Applies to
swconfig,
swcopy,
swinstall,
swmodify,
swpackage,
swremove,
and
swverify. - match_target=false
If set to
true,
software selection is done by locating filesets on the source that
match the target system's installed filesets. If multiple targets are
specified, the first in the list is used as the basis for selections. Applies to
swinstall. - max_agents=-1
The maximum number of agents that are permitted to run simultaneously.
The value of -1 means that there is no limit. Applies to
swagentd. - max_targets=25
When set to a positive integer, this option limits the number of
concurrent install or copy operations to the number specified. As each
copy or install operation completes, another target is selected and
started until all targets are completed. Server and network performance determines the optimal setting; a
recommended starting point is 25 (the default value). If you set this
option to a value of less than one, SD attempts to install or copy to
all targets at once. Applies to
swcopy
and
swinstall. - media_capacity=1330
If creating a distribution tape or multiple-directory media such as a
CD-ROM, this keyword specifies the capacity of the tape in one million
byte units (not Mbytes). This option is required if the media is not
a DDS tape or a disk file. Without this option,
swpackage
sets the size to the default of 1,330 Mbytes for tape or to the amount
of free space on the disk up to
minfree
for a disk file. SD uses the same format across multiple directory
media as it does for multiple serial media, including calculations of
the correct size based partitioning of filesets and setting of the
media_sequence_number
attributes. Applies to
swpackage. - media_type=directory
Defines the type of distribution to create. The recognized types are
directory
and
tape. Applies to
swpackage. - minimum_job_polling_interval=1
Defines in minutes how often the daemon wakes up to scan the job queue
for scheduled jobs that must start. If set to 0, no scheduled
jobs are initiated. Applies to
swagentd. - mount_all_filesystems=true
By default, the SD
commands attempt to mount all filesystems
in the
/etc/fstab
file at the beginning of the analysis phase,
to ensure that all listed filesystems are mounted before proceeding.
This policy helps to ensure that files are not loaded
into a directory that may be below a future mount point, and that
the expected files are available for a remove or verify operation. If set to
false,
the mount operation is not attempted, and no check of the current mounts
is performed. Applies to
swconfig,
swcopy,
swinstall,
swremove,
and
swverify. - mount_cmd=/sbin/mount
Defines the command called by the agent to mount all filesystems. Applies to
swagent. - objects_to_register=
Defines the default
objects to register or unregister.
There is no supplied default (see
select_local
above).
If there is more than one object, they must be separated by spaces. Applies to
swreg. - one_liner=
Defines the attributes which are listed in the non-verbose listing. Applies to
swlist
and
swjob. - os_name
This option can be used in conjunction with
os_release
to specify fileset selection for an HP-UX update.
os_name
should only be specified from the command line. Refer to the SD
readme
file for correct syntax. You can display the
readme
file by entering: swlist -d -a readme SW-DIST [@ host:/depot ] Applies to
swinstall. - os_release
This option can be used in conjunction with
os_name
to specify fileset selection for an HP-UX update.
os_release
should only be specified from the command line. Refer to the SD
readme
file for correct syntax. You can display the
readme
file by entering: swlist -d -a readme SW-DIST [@ host:/depot ] Applies to
swinstall. - package_in_place=false
If set to
true,
swpackage
will package the specified products such that the target depot will not
contain the files that make up a product. Instead,
swpackage
inserts references to the original source files used to build a product.
This behavior allows products to be packaged
without consuming the full disk space of copying all the
source files into the target depot. Applies to
swpackage. - patch_commit=false
Commits a patch by removing files saved for patch rollback. When set to
true,
and run with
swmodify,
you cannot roll back (remove) a patch unless you remove the associated
base software that the patch modified. Applies to
swmodify. - patch_filter=*.*
Specifies a
software_specification
for a patch filter. The default value is
*.*. This option can be used in conjunction with the
autoselect_patches
and
patch_match_target
options to filter the selected patches to meet the criteria specified by
software_specification. Applies to
swask,
swcopy,
and
swinstall, - patch_match_target=false
If set to
true,
this option selects the latest patches (software identified by the
is_patch
attribute) that correspond to software on the target root or depot. The
patch_filter=
option can be used in conjunction with
patch_match_target. Applies to
swcopy
and
swinstall. - patch_one_liner=title patch_state
Specifies the attributes displayed for each object listed when the
-l patch
option is invoked and when no
-a
or
-v
option is specified. The default display attributes are
title
and
patch_state. Applies to
swlist. - patch_save_files=true
Saves patched files, which permits future rollback of patches. When set to
false,
patches cannot be rolled back (removed) unless the base software
modified by the patch is removed at the same time. Applies to
swinstall. - polling_interval=2
Defines in seconds the polling interval used by interactive (GUI)
sessions. It specifies how often each target agent will be polled to
obtain status information about the task being performed. When
operating across wide-area networks, the polling interval can be
increased to reduce network overhead. Applies to
swcopy,
swinstall,
and
swremove. - preserve_create_time=false
Preserves the original create time when you copy depots, which
produces consistent results when you use the copies. The default of
false
sets the create_time of software bundles, products, and filesets
equal to the time the object was created in the depot. When set to
true,
the create_time of software bundles, products, and filesets is
set to that specified in the source depot. Note that using this
option when copying to a master depot can change the objects that are
visible when you use the
create_time_filter
option. Applies to
swcopy. - reboot_cmd=/sbin/reboot
Defines the command called by the agent to reboot the system. Applies to
swagent. - reconfigure=false
Prevents software which is already in the CONFIGURED state from being
reconfigured.
If set to
true,
CONFIGURED software can be reconfigured. Applies to
swconfig. - recopy=false
This option prevents SD from recopying (overwriting) an existing
revision of a fileset. If set to
true,
the fileset will be recopied. Applies to
swcopy. - register_new_depot=true
Causes
swcopy
to register a newly created depot with the local
swagentd.
This action allows other SD commands to automatically "see" this depot.
If set to
false,
a new depot will not be automatically registered.
(It can be registered later with the
swreg
command.) Applies to
swcopy. - register_new_root=true
Causes
swinstall
to register a newly created alternate root with the local
swagentd.
This action allows other SD commands to automatically "see" this root.
If set to
false,
a new root will not be automatically registered.
(It can be registered later with the
swreg
command.) Applies to
swinstall. - reinstall=false
This option prevents SD from re-installing (overwriting) an existing
revision of a fileset. If set to
true,
the fileset will be overwritten. Applies to
swinstall. - reinstall_files=false
Controls the overwriting of files, which may enhance performance on
slow networks or disks. At the default value of false, SD compares
each file in a source fileset to corresponding files on the target
system. SD compares the files based on size, timestamp, and
(optionally) the
checksum
(see
reinstall_files_use_cksum").
If the files are identical the files on the target system are not
overwritten. When set to true, SD does not compare files and overwrites any
identical files on the target. Applies to
swinstall,
swcopy,
and
swpackage. - reinstall_files_use_cksum=true
(For
swpackage,
the default value for this option is
false.)
Controls the use of checksum comparisons when the
reinstall_files
option is set to false. At the default value of true, this option
causes SD to compute and compare checksums to determine if a new file
should overwrite an old file. Use of checksums slows the comparison
but is a more robust check for equivalency than size and time stamp. If set to false, SD does not compute checksums and compares files only
by size and timestamp. Applies to
swcopy,
swinstall,
and
swpackage. - remove_empty_depot=true
Remove an empty depot when the last product is removed.
If set to
false,
an empty depot will not be removed, preserving any depot ACLs. Applies to
swremove. - remove_obsolete_filesets=false
Controls whether
swcopy
automatically removes obsolete filesets from target products in the
target depot. If set to
true,
swcopy
removes obsolete filesets from the target products that were written
to during the copy process. Removal occurs after the copy is
complete. Filesets are defined as obsolete if they were not part of
the most recent packaging of the product residing on the source depot. Applies to
swcopy. - remove_setup_cmd=/usr/lbin/sw/remove_setup
Defines the script called by the agent to perform release-specific
removal preparation. For an OS update, this script invokes the
tlink
command when a fileset is removed. Applies to
swagentd. Please Note: Transition links do not exist on 11.31 and newer
releases so there are no remove preparation steps to perform therefore
the remove_setup_cmd is never executed for these releases. - retry_rpc=1
Defines the number of times a lost (timed out) source connection will
be retried during file transfers. When used in conjunction with the
rpc_timeout
option, the success of installing over slow or busy networks can be
increased. If set to zero, any
rpc_timeout
to the source causes the task to abort. If set from 1 to 9, then
the install of each fileset will be attempted that number of times.
(You can use the
retry_rpc_interval
option to specify the length of the interval between each retry
attempt.) The
reinstall_files
option should also be set to false to avoid installing files within
the fileset that were successfully installed. This option also applies to the controller contacting the agent. If
the agent session fails to start for any reason, the controller tries
to recontact that agent for the number of times specified in
retry_rpc,
using the values from the
retry_rpc_interval
option to determine how long to wait between each attempt to recontact
the agent. Applies to
swcopy
and
swinstall. - retry_rpc_interval={0}
Specifies in minutes the length of the interval for repeated attempts
to make a connection to a target after an initial failure. Used in
conjunction with the
retry_rpc
option. If the number of values in this option equals the value of
retry_rpc,
SD tries reestablishing a source connection for the number of times
specified in
retry_rpc.
If the number of values in
retry_rpc_interval
is less than the value in
retry_rpc,
SD repeats the final interval value until the number of retries
matches
retry_rpc. For example, if an agent session failed to start and
retry_rpc
was set to 9 and
retry_rpc_interval
was set to {1 2 4 8 15} to allow long waits to handle transient
network failures, the SD controller
would attempt to recontact the agent after 1 minute for the first
retry, then 2 minutes for the second retry, 4 for the third, then 8,
then 15 for all additional retries until nine retries were
attempted. With these values, a file load failure could cause the
operation to pause for 90 minutes (1+2+4+8+15+15+15+15+15). If
retry_rpc
was set to 5 and
retry_rpc_interval
was set to {1 2 4 8 15}, the controller would try
to contact the target five times over a 30-minute period. Applies to
swcopy
and
swinstall. - rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
Defines the protocol sequence(s) and endpoint(s) on which the daemon
listens and on which the other commands use to contact the daemon. If
the connection fails for one protocol sequence, the next is attempted.
SD supports both the
tcp
(ncacn_ip_tcp:[2121])
and
udp
(ncadg_ip_udp:[2121])
protocol sequence on most platforms. The value
(or values for
swagentd)
can have
following form:
A DCE string binding containing a protocol sequence and an
endpoint. The syntax is:
protocol_sequence:[endpoint]. The name of a DCE protocol sequence with no endpoint specified. The
syntax is:
protocol_sequence,
for example
ncadg_ip_udp
or
ncacn_ip_tcp.
(A trailing
:
can be attached to the protocol sequence, it has no effect.)
Since no endpoint is specified, the DCE endpoint mapper
rpcd
must be running and will be used to find the endpoint registered by the
swagentd. The literal string
all.
This entry means to use (try) all protocol sequences supported by the DCE RPC.
It should be the only entry in the list.
The DCE endpoint mapper
rpcd
also must be running in order to use this option.
Applies to all commands except
swask,
swpackage,
and
swmodify. - rpc_binding_info_alt_source=ncadg_ip_udp:[2121]
Defines the protocol sequence(s) and endpoint(s) used when the agent
attempts to contact an alternate source depot specified by the
alternate_source
option.
SD supports both the
udp
(ncadg_ip_udp:[2121])
and
tcp
(ncacn_ip_tcp:[2121])
protocol sequence/endpoint. Applies to
swagent. - rpc_binding_info_source=
Defines the protocol sequence(s) and endpoint(s) used to contact the
daemon for source access. If set to no value (default) the value of
rpc_binding_info
is used. Applies to
swinstall
and
swcopy. - rpc_binding_info_target=
Defines the protocol sequence(s) and endpoint(s) used to contact the
daemon for target access. If set to no value (default) the value of
rpc_binding_info
is used. Applies to
swinstall
and
swcopy. - rpc_timeout=5
Relative length of the communications timeout. This is a value in the
range from 0 to 9 and is interpreted by the DCE RPC. Higher values
mean longer times; you may need a higher value for a slow or busy
network. Lower values will give faster recognition on attempts to
contact hosts that are not up, or are not running
swagentd.
Each value is approximately twice as long as the preceding value.
A value of 5 is about 30 seconds for the
ncadg_ip_udp
protocol sequence.
This option may not have any noticeable impact when using the
ncacn_ip_tcp
protocol sequence. Applies to all commands except
swpackage
and
swmodify. - run_as_superuser=true
This option controls SD's nonprivileged mode. This option is ignored
(treated as true) when the invoking user is super-user. When set to the default value of true, SD operations are performed
normally, with permissions for operations either granted to a local
super-user or set by SD ACLs. (See
swacl(1M)
for details on ACLs.) When 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. 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.
SD's 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, see the
Software Distributor Administration Guide,
available at the
http://docs.hp.com
web site. See also the
admin_directory
and
installed_software_catalog
options. Applies to all SD commands except
swagent,
swagentd,
and
install-sd. - show_superseded_patches=false
Displays or hides superseded patches in
swlist
output. In the default state of
false, swlist
will not display superseded patches even if you perform a
swlist
command on the superseded patch. Setting this option to
true
permits display of superseded patches. Applies to
swlist. - select_local=true
If no
target_selections
are specified,
select the default
target_directory
of the local host as the
target_selection
for the command. Applies to
swacl,
swconfig,
swcopy,
swinstall,
swlist,
swreg,
swremove,
and
swverify. - software=
Defines the default
software_selections.
There is no supplied default.
If there is more than one software selection, they must be separated by spaces.
Software is usually specified in a software input
file, as operands on the command line, or in the GUI. Applies to all commands except
swreg
and
swjob. - software_view=products
Indicates the software view to be used by the interactive interface of the
commands and by
swlist
for the default listing level.
It can be set to products, all_bundles, or a bundle
category tag (to indicate to show only bundles of that category). Applies to
swcopy,
swinstall,
swlist,
and
swremove. - source=
Specify a source to automatically bypass the GUI and CLI source
selection dialog box. This has the same effect as the
-ssource
command line option. Specify the source using the following syntax. [path] Applies to
swcopy
and
swinstall. - source_cdrom=/SD_CDROM
Defines the default location of the source CD-ROM using the syntax
[host]:
[path]. Applies to
swinstall. - source_depot_audit=true
If both source and target machine are updated to SD revision B.11.00
or later, the system administrator at the source depot machine
can set this option to track
which
user pulls
which
software from a depot on the source machine and
when
the software is pulled. (Note that a user running
swinstall/swcopy
from a target machine cannot set this option; only the administrator
of the source depot machine can set it.) When
source_depot_audit
is set to
true,
a
swaudit.log
file is created on the source depot (for writable directory depots)
or in
/var/tmp
(for
tar
images, CD-ROMs, or other non-writable depots). Users can invoke the
swlist
interactive user interface (using
swlist -i -d)
to view, print, or save the audit information on a remote or local
depot. Users can view audit information based on language preference,
as long as the system has the corresponding SD message catalog files
on it. For example, a user can view the source audit information in
Japanese during one invocation of
swlist,
then view the same information in English
at the next invocation. Applies to
swagent. - source_file=psf
Defines the default location of the source product specification file
(PSF). The
host:path
syntax is not allowed, only a valid
path
can be specified.
The
-s
option overrides this value. Applies to
swpackage
and
swmodify. - source_tape=/dev/rmt/0m
Defines the default location of the source tape, usually the
character-special file of a local tape device. You can also use the
host:path
syntax, but the host must match the local host.
The
-s
option overrides this value. (Note that SD can read both
tar
and
cpio
tape depots.) Applies to
swcopy
and
swinstall. - source_type=directory
Defines the default source type:
cdrom,
file,
directory,
or
tape.
The source type derived from the
-s
option overrides this value. (Note that SD
can read both
tar
and
cpio
tape depots.) Applies to
swcopy,
swinstall,
and
swpackage.
(The values
cdrom,
and
tape
apply to
swcopy
and
swinstall
only. The value
file
applies to
swpackage
only.) - system_file_path=/stand/system
Defines the path to the kernel's template file. This path is passed
to the
system_prep_cmd
via the
SW_SYSTEM_FILE_PATH
environment variable. Applies to
swagent. - system_prep_cmd=/usr/lbin/sysadm/system_prep
Defines the kernel build preparation script called by the agent.
This script must do any necessary preparation so that control
scripts can correctly configure the kernel about to be built. This
script is called before any kernel filesets have been loaded. Applies to
swagent.
- targets=
Defines the default
target_selections.
There is no supplied default (see
select_local
above).
If there is more than one target selection, they must be separated by spaces.
Targets are usually specified in a target input
file, as operands on the command line, or in the GUI. Applies to all commands. - uncompress_cmd=
Defines the command to uncompress files
when installing, copying, or packaging.
This command processes files which were stored on the
media in a compressed format. If the
compression_type
of the file is
gzip
then the internal uncompression
(funzip)
is used instead of the external
uncompress_cmd. Applies to
swpackage
and
swagent. - uncompress_files=false
If the files being transferred from a source are compressed, setting
this option will uncompress the files before storing them on the
target depot. Applies to
swcopy
and
swpackage. - use_alternate_source=false
Lets each target agent use its own configured alternate source,
instead of the one specified by the user. If
false,
each target agent will use the same source, namely the source specified by
the user and validated by the command.
If
true,
each target agent will instead use its own configured value for the source. Applies to
swcopy
and
swinstall. - verbose=
Controls the verbosity of a non-interactive command's output:
- 0
disables output to stdout. (Error and warning messages
are always written to stderr). - 1
enables verbose messaging to stdout. - 2
for
swpackage
and
swmodify,
enables very verbose messaging to stdout.
For the
swlist
command, a verbose listing includes all attributes that have been
defined for the appropriate
level of each
software_selection
operand. The attributes are listed, one per line, prefaced
by the attribute keyword. The
-v
option overrides this default if it is set to 0. Applies to all commands. - write_remote_files=false
Prevents file operations on remote (NFS) file systems. All files
destined for installation, copy, removal, or packaging on targets on a
remote (NFS) file systems are skipped. If set to true and if the superuser has write permission on the remote
file system, the remote files are not skipped, but are installed,
copied, packaged, or removed. Applies to
swconfig,
swcopy,
swinstall,
swpackage,
and
swremove.
Session FilesEach invocation of an SD command defines a
task session.
Most SD commands automatically save task session information (options,
source information, software selections, and target selections) before
the task actually commences. This lets you re-execute the command even
if the session ends before the task is complete. You can also save
session information from command-line and interactive sessions. From the command-line, you can save session information by executing
the command with the
-C session__file
option. You can specify a relative or absolute path for a session
file. If you do not specify a directory, the default location is
$HOME/.sw/sessions/. From an interactive session, you can save session information
into a file at any time by selecting the
Save Session
or
Save Session As
option from the
File
menu. Session information is saved to the file:
$HOME/.sw/sessions/command_name.last For example:
/home/my_user_name/.sw/sessions/swinstall.last This file is overwritten by each invocation of the command. Contents
of the session file use this syntax: [command_name.]option=value The
command_name
prefix denotes the name of the SD command that saved the session
information. For example:
To re-execute a session from a command-line, specify the session file
as the argument for the
-S
option. To re-execute a saved session from an interactive session, use the
Recall Session
option from the
File
menu. When you re-execute a session file, the values in the session file
take precedence over values in the system defaults file. Likewise,
any command-line options and parameters take precedence over the
values in the session file. Software and Target ListsMost SD commands support software and target selections from separate
input files (see the
-f
and
-t
command-line options). Software and targets specified in these files
will be selected for operation.
swinstall
and
swcopy
also support an interactive read and save of target and software
groups. Target and software groups can be saved in files (default
location
$HOME/.sw/targets/
and
$HOME/.sw/software/)
and then selected in subsequent
swinstall
and
swcopy
operations. Additionally, commands that support an interactive interface read
a list of possible hosts to operate on from the values found in:
- /var/adm/sw/defaults.hosts
the system-wide default list of hosts, - $HOME/.sw/defaults.hosts
the user-specific default list of hosts.
Hosts in this file are not marked for operation, but provide a default
list from which to choose. For each interactive command, target hosts
containing roots and depots are specified in separate lists (
hosts,
and
hosts_with_depots,
respectively). The list of hosts are enclosed in {} braces and
separated by white space (blank, tab and newline). For example:
swinstall.hosts={hostA hostB hostC hostD
hostE hostF}
swcopy.hosts_with_depots={hostS}
swremove.hosts={hostA hostB hostC hostD
hostE hostF}
swremove.hosts_with_depots={hostS} Most SD commands support patch filtering with the
-x patch_filter=software_specification
option. In addition, the interactive user interface commands,
swinstall
and
swcopy
read a list of possible patch filters. You can use the values
from this list for selection criteria. The lists are stored in:
- /var/adm/sw/defaults.patchfilters
the system-wide default list of patch filters. - $HOME/.sw/defaults.patchfilters
the user-specific default list of patch filters.
Filters in this file are not marked for selection use but provide a
default list from which you can choose. The list of patch filters
is enclosed in braces {} and separated by white space (blank, tab, or
newline). For example:
swinstall.patch_filter_choices={
*.*,c=enhancement
*.*,c=critical
}
swremove.patch_filter_choices={
Product.Fileset,c=halts_system
} Environment VariablesSD programs are affected by external environment variables, set
environment variables for use by the control scripts, and set
additional environment variables that affect scripts run by
swinstall
and
swremove. External environment variables that affect the SD commands: - LANG
Determines the language in which messages are displayed. If LANG is
not specified or is set to the empty string, a default value of
C
is used.
See
lang(5)
for more information. NOTE: The language in which the SD agent and daemon log messages
are displayed is set by the system configuration variable script,
/etc/rc.config.d/LANG.
For example,
/etc/rc.config.d/LANG,
must be set to
LANG=ja_JP.SJIS
or
LANG=ja_JP.eucJP
to make the agent and daemon log messages display in Japanese. This variable applies to all SD commands. - LC_ALL
Determines the locale to be used to override any values for locale
categories specified by the settings of
LANG
or any environment variables beginning with
LC_. - LC_CTYPE
Determines the interpretation of sequences of bytes of text data as
characters (e.g., single-versus multibyte characters in values for
vendor-defined attributes). - LC_MESSAGES
Determines the language in which messages should be written. - LC_TIME
Determines the format of dates
(create_date
and
mod_date)
when displayed by
swlist.
Used by all utilities when displaying dates and times in
stdout,
stderr,
and
logging. - TZ
Determines the time zone for use when displaying dates and times.
Environment variables that affect scripts: - SW_CATALOG
Holds the path to the Installed Products Database (IPD), relative to
the path in the
SW_ROOT_DIRECTORY
environment variable. Note that you
can specify a path for the IPD using the
installed_software_catalog
default option. - SW_CONTROL_DIRECTORY
Defines the current directory of the script being executed, either a
temporary catalog directory, or a directory within in the Installed
Products Database (IPD). This variable tells scripts where other
control scripts for the software are located (e.g. subscripts). - SW_CONTROL_TAG
Holds the tag name of the
control_file
being executed. When packaging
software, you can define a physical name and path for a control file
in a depot. This lets you define the
control_file
with a name other
than its tag and lets you use multiple control file definitions to
point to the same file. A
control_file
can query the
SW_CONTROL_TAG
variable to determine which tag is being executed. - SW_LOCATION
Defines the location of the product, which may have been changed from
the default product directory. When combined with the
SW_ROOT_DIRECTORY,
this variable tells scripts where the product files are located. - SW_PATH
A
PATH
variable which defines a minimum set of
commands available for use in a control script
(e.g.
/sbin:/usr/bin). - SW_ROOT_DIRECTORY
Defines the root directory in which the session is operating, either
/
or an alternate root directory.
This variable tells control scripts the root directory in which the
products are installed. A script must use this directory as a prefix
to
SW_LOCATION
to locate the product's installed files.
The configure script is only run when
SW_ROOT_DIRECTORY
is
/. - SW_SESSION_OPTIONS
Contains the pathname of a file containing the value of every option
for a particular command, including software and target
selections. This lets scripts retrieve any command
options and values other than the ones provided explicitly by
other environment variables. For example, when the file pointed to by
SW_SESSIONS_OPTIONS
is made available to a
request
script, the
targets
option contains a list of
software_collection_specs
for all targets specified for the command. When the file pointed to by
SW_SESSIONS_OPTIONS
is made available to other scripts, the
targets
option contains the single
software_collection_spec
for the targets on which the script is being executed. - SW_SOFTWARE_SPEC
This variable contains the fully qualified software specification of
the current product or fileset. The software specification allows the
product or fileset to be uniquely identified.
Additional environment variables that affect scripts run by
swinstall
and
swremove: - SW_CONFIG_AFTER_REBOOT
This variable should be read only by the
configure
script. If this is set to any value it indicates the
configure
script was invoked by the
swconfig
command during system startup. This variable is set by the
/sbin/init.d/swconfig
system startup script. - SW_DEFERRED_KERNBLD
Only applies to
swinstall.
This variable is normally unset. If it is
set, the actions necessary for preparing the
system file
/stand/system
cannot be
accomplished from within the
postinstall
scripts, but instead must be accomplished by
the
configurescripts.
This occurs whenever
software is installed to a directory other
than
/,
such as for a cluster client system.
This variable should be read only by the
configure
and
postinstall
scripts of a kernel fileset. The
swinstall
command sets these environment variables for use by the kernel
preparation and build scripts. - SW_INITIAL_INSTALL
Only applies to
swinstall.
This variable is normally unset. If it is
set, the
swinstall
session is being run as the
back end of an initial system software
installation ("cold" install). - SW_KERNEL_PATH
Only applies to
swinstall.
The path to the kernel. The default value is
/stand/vmunix,
defined by the
swagent
option or
kernel_path. - SW_SESSION_IS_KERNEL
Indicates whether a kernel build is scheduled for the current
install/remove session. A
TRUE
value indicates that the selected kernel fileset is scheduled for
a kernel build and that changes to
/stand/system
are required.
A null value indicates that a kernel build is not scheduled and that
changes to
/stand/system
are not required. The value of this variable is always equal to the value of
SW_SESSION_IS_REBOOT. - SW_SESSION_IS_REBOOT
Indicates whether a reboot is scheduled for a fileset selected for
removal. Because all HP-UX kernel filesets are also reboot filesets,
the values of this variables is always equal to the value of
SW_SESSION_IS_KERNEL. - SW_SESSION_IS_UPDATE
A value of
1
indicates the SD command was invoked by the
update-ux
command during an Operating System update.
This variable is set by the
update-ux
command. - SW_SYSTEM_FILE_PATH
Only applies to
swinstall.
The path to the kernel's system file. The
default value is
/stand/system.
SignalsThe SD commands catch the signals SIGQUIT, SIGINT, and SIGUSR1. If
these signals are received, the command prints a message, sends a
Remote Procedure Call (RPC) to the agents to wrap up after completion,
and then exits. The agent ignores SIGHUP, SIGINT, and SIGQUIT. It immediately exits
gracefully after receiving SIGTERM, SIGUSR1, or SIGUSR2. Killing the
agent may leave corrupt software on the system, and thus should only
be done if absolutely necessary. Note that when an SD command is
killed, the agent does not terminate until completing the task in
progress. The daemon ignores SIGHUP, SIGINT and SIGQUIT. It immediately exits
gracefully after receiving SIGTERM and SIGUSR2. After receiving
SIGUSR1, it waits for completion of a copy or remove from a depot
session before exiting, so that it can register or unregister depots
if necessary. Requests to start new sessions are refused during this wait.
The following paragraph applies only to swconfig, swcopy,
swinstall, swremove, and swverify.
For SIGUSR1, the command sends an RPC to the agents to quit
immediately, as if the agent had received a SIGTERM signal. When
SIGUSR1 is sent to the SD Controller, it shuts down target agents with
SD revision B.11.01 or later, then shuts itself down. When the target
agent receives the shutdown RPC, it invokes its handler for signal 15
(SIGTERM), which resembles what happens if a superuser on the target
machine used a
kill
command on the target agent process. LockingSD commands use a common locking mechanism for reading and modifying
both root directories and software depots. This mechanism
allows multiple readers but only one writer on a root or depot. The SD
commands which modify software in an (alternate) root directory are restricted from simultaneous
modification using
fcntl(2)
locking on the file
var/adm/sw/products/swlock relative to the root directory
(e.g.
/var/adm/sw/products/swlock). The SD
commands which modify software in a depot are restricted from
simultaneous modification using
fcntl(2)
locking on the file
relative to the depot directory (e.g.
/var/spool/sw/catalog/swlock). All commands set
fcntl(2)
read locks on roots and depots using the
swlock
file mentioned above.
When a read lock is set, it prevents other SD commands from performing
modifications (i.e. from setting write locks). If an SD process has died prematurely and no other SD agents are
running, you can remove the
swlock
file to unlock the root or depot. RETURN VALUESEach SD command invocation returns:
- 0
The sw<task> successfully completed. - 1
The sw<task> failed on all
target_selections. - 2
The sw<task> failed on some
target_selections.
DIAGNOSTICSThe
swconfig,
swcopy,
swinstall,
swmodify,
swpackage,
swremove,
and
swverify
commands support a preview mode, where operation
will proceed through the analysis
of each
target_selection,
then exit before the actual task is performed. You can use the
sd
interactive interface
or the
swjob
command to view the current status of any job or the controller and
target log files. Standard OutputWhen non-interactive, the commands write messages for significant
events. These events include:
a begin and end task message, a message for starting the task on each host, and a message for completing the task on each host.
When the
verbose
option is set, summary messages about the task are also sent to the standard output. Standard ErrorWhen non-interactive, the commands also write messages for the following
significant error events:
a message for each host failing analysis and a message for each host failing the actual task.
LoggingAll
commands log major events on the host where the command was invoked.
They log detailed events to the
swagent
log associated with each
target_selection.
- Command Log
The commands log messages to
/var/adm/sw/sw<task>.log.
(You can specify a different logfile by
modifying the
logfile
option.) - Target Log
A
swagent
process performs the actual
swacl,
swconfig,
swcopy,
swinstall,
swremove,
and
swverify
operation at each
target_selection.
For operations on target root objects,
the
swagent
logs messages to the file
var/adm/sw/swagent.log
beneath the root directory (e.g.
/
or an alternate root directory).
For operations on target depot objects,
the
swagent
logs messages to the file
swagent.log
beneath the depot directory (e.g.
/var/spool/sw). The
swagentd
running on a host logs events to the file
/var/adm/sw/swagentd.log. - Source Depot Audit Log
If both source and target machine are updated to SD revision B11.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
source_depot_audit
option in
swagent(1M)
for more information.
FILES- /dev/rmt/0m
Default source tape location. (Note that SD can read both
tar
and
cpio
tape depots.) - /etc/fstab
List of volumes that should be mounted. - $HOME/.swdefaults
Contains the user-specific default values for some or all SD
options. If this file does not exist, SD looks for user-specific
defaults in
$HOME/.sw/defaults. - $HOME/.sw/defaults.hosts
Contains the user-specific default list of hosts to manage. - $HOME/.sw/defaults.patchfilters
Contains the user-specific default list of patch filters. - $HOME/.sw/sessions/
Contains session files automatically saved by the SD commands, or
explicitly saved by the user. - $HOME/.sw/software/
Contains software files explicitly saved by the user. - $HOME/.sw/targets/
Contains target files explicitly saved by the user. - /usr/lbin/swagent
The SD agent. - /usr/lib/nls/$LANG/sw*.cat
The SD message catalogs. - /usr/lib/sw/help/
The directory which contains the help files used by the
SD GUIs' on-line help facility. - /usr/lib/sw/sys.defaults
Contains the master list of current SD options (with their default values). - /usr/lib/sw/ui/
The directory which contains the description files used by the
SD Graphical User Interfaces (GUIs). - /usr/newconfig/var/adm/sw/
The directory containing the configurable data shipped for the SD
product, which is conditionally copied into
/var/adm/sw/
based on the existing configuration. - /usr/sbin/sw*
The SD commands. - /var/adm/sw/
The directory which contains all of the configurable
(and non-configurable) data for SD.
This directory is also the default location of log files. - /var/adm/sw/defaults
Contains the active system-wide default values for some or all SD options. - /var/adm/sw/defaults.hosts
Contains the system-wide default list of hosts to manage. - /var/adm/sw/defaults.patchfilters
Contains the system-wide default list of patch filters. - /var/adm/sw/getdate.templ
Contains the set of date/time templates used when scheduling jobs. - /var/adm/sw/host_object
The file which stores the list of depots registered at the local host. - /var/adm/sw/products/
The Installed Products Database (IPD), a catalog of all products
installed on a system. - /var/adm/sw/queue/
The directory which contains the information about all active and complete
install, remove, and other jobs initiated by the SD commands. - /var/adm/sw/security/
The directory which contains ACLs for the system itself, template ACLS,
and the secrets file used to authenticate remote requests. - /var/adm/sw/target_hosts
The cache file created by a
swinstall
or
swcopy
process which contains target hostnames and their relevant
uname
attributes. - /var/spool/sw/
The default location of a source and target software depot. - /usr/lib/sw/examples/
The directory containing an example depot and example swpackage data.
AUTHORSoftware Distributor was developed by the Hewlett-Packard Company.
swagent,
swcopy,
swinstall,
swlist,
and
swpackage
were developed by the Hewlett-Packard Company and Mark H. Colburn (see
pax(1)). SEE ALSOinstall-sd(1M),
swacl(1M),
swagentd(1M),
swask(1M),
swconfig(1M),
swcopy(1M),
swinstall(1M),
swjob(1M),
swlist(1M),
swmodify(1M),
swpackage(1M),
swreg(1M),
swremove(1M),
swverify(1M),
swpackage(4),
sd(4). Software Distributor Administration Guide,
available at
http://docs.hp.com. SD customer web site at
http://docs.hp.com/en/SD/.
|