swinstall(1M) swinstall(1M)
Hewlett-Packard Company
NAME [Toc] [Back]
swinstall, swcopy - install and configure software products; software
products for subsequent installation or distribution; respectively
SYNOPSIS [Toc] [Back]
swinstall [XToolkit Options] [-i] [-p] [-r] [-v] [-c catalog]
[-C session_file] [-f software_file] [-J jobid] [-Q date] [-s
source] [-S session_file] [-t target_file] [-x option=value] [-X
option_file] [software_selections] [@ target_selections]
swcopy [XToolkit Options] [-i] [-p] [-v] [-C session_file]
[-f software_file] [-J jobid] [-Q date] [-s source] [-S
session_file] [-t target_file] [-x option=value] [-X option_file]
[software_selections] [@ target_selections]
Remarks [Toc] [Back]
+ swinstall and swcopy have an interactive user interface. You
can invoke it by typing swinstall, swcopy, or by including the
-i option on the command line.
+ SD-UX commands are included with the HP-UX operating system and
manage software on the local host only.
+ To install and manage software simultaneously on multiple
remote hosts (including HP-UX, other UNIXr platforms, and
Windows NTr) from a central controller, you must purchase the
HP OpenView Software Distributor which provides extended
software management capabilities. Information specific only to
the OpenView product is marked with a heading similar the
following:
The following information applies to HP OpenView Software
Distributor only.
DESCRIPTION [Toc] [Back]
The swinstall command installs the software_selections from a software
source to either the local host or, in the case of the HP OpenView
Software Distributor product, to one or more target_selections (root
filesystems). By default, the software is configured for use on the
target after it is installed. (The software is not configured when
installed into an alternate root directory.)
The swcopy command copies or merges software_selections from a
software source to one or more software depot target_selections These
depots can then be accessed as a software source by the swinstall
command.
Updating the Operating System [Toc] [Back]
To perform an OS update with swinstall (or to reinstall SD from
media), you must use first use the swgettools command to get the
newest version of swinstall.
Hewlett-Packard Company - 1 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
CAUTION: You MUST use the latest version of swinstall to update your
system to the latest version of HP-UX. If you use a previous version
of swinstall, the update will fail.
The os_name and os_release options let you specify the desired OS name
and release during an HP-UX update. (These options should only be
specified from the command line.) The SD readme file lists correct
syntax for these options. You can display the readme file by entering:
swlist -a readme -l product SW-DIST
The match_target option, if set to true, selects software by locating
filesets on the source that match the target system's installed
filesets.
Refer to the Default Options section of this manual page,
swgettools(1M), and Installing HP-UX 11.0 and Updating HP-UX 10.x to
11.0 for more information.
Installing Kernel Software [Toc] [Back]
In HP-UX, the kernel installation process requires that the system
boots using the kernel at /stand/vmunix. Make sure that your system
is booted to the /stand/vmunix kernel before you install any kernel
software or perform an operating system update.
Dependencies Between Software [Toc] [Back]
The swinstall command supports 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, swinstall automatically select that software.
By default, all dependencies must be resolved before swinstall can
proceed. You can override this policy using the enforce_dependencies
option.
Note that if you specify a dependency for a fileset and the fileset is
superseded by another fileset as part of a patch, swinstall still
recognizes the dependency.
Features and Differences between swinstall and swcopy [Toc] [Back]
The key difference between swinstall and swcopy is that swinstall
performs the software installation, while swcopy copies software into
Hewlett-Packard Company - 2 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
a depot, making it available as a source for installation by
swinstall.
NOTE: To copy to a tape, see the swpackage(1M) manpage.
Other features (differences) include:
+ The swinstall command executes several vendor-supplied scripts
during the installation and configuration of the
software_selections. The swcopy command does not execute
these scripts. The swinstall command supports the following
scripts:
request a script that asks the user questions and
stores responses in a response file. The
response file can then be used by
configuration or other scripts.
checkinstall a script executed during the analysis of a
target_selection, it checks that the
installation can be attempted. If this check
fails, the software product is not installed.
preinstall a script executed immediately before the
software's files are installed.
postinstall a script executed immediately after the
software's files are installed.
configure a script executed during the configuration of
a target_selection, it configures the target
for the software (and the software for the
target). The preinstall and postinstall
scripts are not intended to be used for
configuration tasks. They are to be used for
simple file management needs such as removing
obsolete files from the previous revision
(which was just updated).
unpreinstall a script executed immediately after the
software's actual files are restored if the
software install will fail and the
autorecover_product option is set to true.
The script undoes the steps performed by
preinstall script.
unpostinstall a script executed immediately before the
software's actual files are restored if the
software install failed and the
autorecover_product option is set to true.
The script undoes the steps performed by
Hewlett-Packard Company - 3 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
postinstall script.
+ When a depot is created or modified using swcopy, catalog
files are built that describe the depot (as opposed to the
Installed Products Database (IPD) files that are built by the
swinstall command).
+ By default, the swinstall command only allows the selection of
compatible software from the source. This constraint ensures
that the architecture of the software matches that of the
target_selections. No compatibility checks are performed by
the swcopy command. (A depot can be a repository of software
targeted for a variety of architectures and operating
systems.)
+ By default, swinstall supports updates to higher revisions of
software. If a software_selection of the same revision is
already installed, swinstall will not reinstall it. If a
software_selection has a lower revision than the same software
which is already installed, swinstall will not reinstall it.
(The user can override these behaviors with control options.)
+ The swinstall command creates hard links and symbolic links as
specified for the software. If it encounters a symbolic link
where it expected a regular file, swinstall follows the
symbolic link and updates the file to which it points.
+ The swinstall command does not remove a product's current
files before installing the new ones. A fileset's install
scripts can do that, if necessary. Files being replaced are
overwritten unless they are in use. If in use, they are
unlinked or moved to #<file>. If the autorecover_product
option is set to true; all files are saved to #<file>, and
restored if the install fails.
+ The swinstall command supports kernel building scripts and
rebooting. Before or after software that modifies the kernel
is installed or updated, swinstall executes system-specific
scripts to prepare for or build the new version of the kernel.
The remaining software_selections are then installed. These
scripts are defined in swagent options and include:
install_setup_cmd, system_prep_cmd, kernel_build_cmd, and
install_cleanup_cmd.
After software that requires a system reboot is installed or
updated, swinstall automatically reboots the system. The
reboot command is defined by the swagent option: reboot_cmd.
When updating the operating system, you must use first use the
swgettools command to get the newest version of swinstall.
(See swgettools(1M) for more information.) Then you should
Hewlett-Packard Company - 4 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
install kernel software first to ensure that a new kernel can
be generated before the rest of the operating system is
updated. After all the software_selections are updated or
installed, swinstall reboots using the new kernel, then
executes the configure scripts for each software_selection.
After these scripts complete, it reboots the system again to
restore it to its normal state.
+ No kernel building or system reboots are performed by swcopy.
+ Both the swinstall and swcopy commands perform various checks
prior to installing or copying the software_selections, for
example disk space analysis.
Options [Toc] [Back]
swinstall and swcopy support the following options:
XToolKit Options
The swinstall and swcopy 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 by typing man X for a definition of these
options.
-i Runs the command in interactive mode by invoking
the Graphical User Interface (GUI). [Note: The
GUI is only supported on HP-UX]. The SD-UX
swinstall, swcopy, and swremove commands also
support an interactive terminal user interface
(text based) in which screen navigation is done
with the keyboard (no mouse).
-l (Applies only to HP-UX 10.X.) Runs the command in
linkinstall mode which makes software installed
under a server's shared root available to a
diskless client's private root (HP-UX only).
When run in the 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.
Hewlett-Packard Company - 5 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
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 old
one.
-p Previews an install task by running the session
through the analysis phase only.
-r (Applies to swinstall only.) Allows the command to
operate on target_selections that are alternate
root directories (root filesystems other than /).
Note that you cannot use this option to relocate
software during installation. You must use the
l=location syntax in the software selection
component.
-v Turns on verbose output to stdout. (The swinstall
or swcopy logfile is not affected by this option.)
Verbose output is enabled by default; see the
verbose option below.
-c catalog Specifies the pathname of an exported catalog
which stores copies of the response file or files
created by a request script (if -x ask=true or -x
ask=as_needed). The response files are also
stored in the Installed Products Database after
the installation process is complete.
-C session_file
Save the current options and operands to
session_file. You can enter a relative or
absolute path with the file name. The default
directory for session files is
$HOME/.sw/sessions/. You can recall a session
file with the -S option.
-f software_file
Read the list of software_selections from
software_file instead of (or in addition to) the
command line.
-J jobid (Applies only to HP OpenView Software
Distributor.)
Executes the previously scheduled job. This is
the syntax used by the daemon to start the job.
-Q date (Applies only to HP OpenView Software
Distributor.)
Hewlett-Packard Company - 6 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
Schedules the job for this date. The date's
format can be changed by modifying the file
/var/adm/sw/getdate.templ.
-s source Specifies the source depot (or tape) from which
software is installed or copied. (SD can read both
tar and cpio tape depots.) The default source
type is directory. The syntax is:
[host][:][/directory]
A host may be specified by its host name, domain
name, or internet address. A directory must be
specified by an absolute path.
-S session_file
Execute swinstall or swcopy based on the options
and operands saved from a previous session, as
defined in session_file. You can save session
information from a command-line session with the
-C session_file option.
-t target_file (Applies only to HP OpenView Software
Distributor.)
Read the list of target_selections from
target_file instead of (or in addition to) the
command line.
-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.
Operands [Toc] [Back]
The swinstall and swcopy 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 "software selections at targets".
Software Selections [Toc] [Back]
The selections operands consist of software_selections.
swinstall and swcopy support the following syntax for each
software_selection:
Hewlett-Packard Company - 7 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
bundle[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
+ The = (equals) relational operator lets you specify
selections with the following shell wildcard and patternmatching
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.
+ The <op> (relational operator) component can be of the form:
==, >=, <=, <, >, or !=
which performs individual comparisons on dot-separated
fields.
For example, r>=B.10.00 chooses all revisions greater than
or equal to B.10.00. The system compares each dot-separated
field to find matches.
Hewlett-Packard Company - 8 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
+ The = (equals) relational operator lets you specify
selections with the 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:
[instance_id]
within the context of an exported catalog, where instance_id
is an integer that distinguishes versions of products and
bundles with the same tag.
The \* software specification selects all products. It is not allowed
when removing software from the root directory /.
Target Selection [Toc] [Back]
The swinstall and swcopy commands support the following syntax for
each target_selection. The : (colon) is required if both a host and
directory are specified.
[host][:][/directory]
A host may be specified by its host name, domain name, or internet
address. A directory must be specified by an absolute path.
For linkinstall, on HP-UX 10.X systems: if the [directory] part of the
selection is a relative path, then the value of
default.shared_root=true is pre-pended for sources and the value of
default.private_root=true is pre-pended for targets. These are
normally /export/shared_roots and /export/private_roots, respectively.
EXTERNAL INFLUENCES [Toc] [Back]
Hewlett-Packard Company - 9 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
Default Options [Toc] [Back]
In 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
swinstall and swcopy commands. If a default value exists, it is
listed after the "=".
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 is true - the target agent automatically exits
when appropriate. If set to false, the target agent
will not exit until the controller ends the session.
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 is
used. The default of 10000 is slightly less than 7
days.
Hewlett-Packard Company - 10 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
allow_downdate=false
(Applies only to swinstall.) Prevents the installation
of an older revision of fileset that already exists at
the target(s). (Many software products do not support
"downdating".) If set to true, the older revision can
be installed.
allow_incompatible=false
(Applies only to swinstall.) 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.
allow_multiple_versions=false
(Applies only to swinstall.) Prevents the installation
of another, independent version of a product when a
version already is already installed at the target.
If set to true, another version of an existing product
can be installed into a new location. Multiple
versions can only be installed if a product is
locatable. Multiple configured versions will not work
unless the product supports it.
allow_split_patches=false
Permits the use of single patch filesets without
"sibling" filesets. In the default state of false,
installation or copying 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 or copied 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 by a patch,
while the other filesets would remain at an earlier
release.
ask=false (Applies only to swinstall.) When ask=true, executes a
request script which asks for a user response. If
ask=as_needed, the swinstall command first determines
if a response file already exists in the catalog
specified in the -c option or source depot and executes
Hewlett-Packard Company - 11 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
the request script only when a response file is absent.
If set to ask=true, or ask=as_needed, you can use the
-c catalog option to specify the pathname of an
exported catalog to store copies of the response file
or files created by the request script.
See swask(1M) for more information on request scripts.
autoreboot=false
(Applies only to swinstall.) Prevents the installation
of software requiring a reboot from the non-interactive
interface. If set to true, this software can be
installed and the target system(s) will be
automatically rebooted.
An interactive session always asks for confirmation
before software requiring a reboot is installed.
autorecover=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. At the cost
of a temporary increase in disk space and slower
performance, this allows for automatic recovery of the
original filesets if an installation error occurs. 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 Managing HP-UX Software With SD-UX for
complete information.
autorecover_product=false
(Applies only to swinstall.) Causes swinstall to remove
the original files as they are updated. If an error
occurs during the installation (e.g. network failure),
then the original files are lost, and the installation
must be re-tried.
If set to true, all files are saved as backup copies
until all filesets in the current product loading are
complete; then they are removed. At the cost of a
Hewlett-Packard Company - 12 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
temporary increase in disk space and slower
performance, this allows for automatic recovery of the
original filesets in that product if the load fails.
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 Managing HP-UX Software With SD-UX for
complete information.
The following option applies only to HP
OpenView Software Distributor.
autoremove_job=false
Controls automatic job removal of completed jobs. If
the job is automatically removed, job information (job
status or target logfiles) cannot be queried with
swjob.
autoselect_dependencies=true
Automatically select dependencies when software is
being selected. When set to true, and any software
which has dependencies is selected for install,
swinstall or swcopy makes sure that the dependencies
are met. If they are not already met, they are
automatically selected for you. If set to false,
automatic selections are not made to resolve
requisites. When set to as_needed, autoselected
dependencies are operated only if the dependency is not
already met on the target.
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 are not automatically selected.
The patch_filter= option can be used in conjunction
with autoselect_patches.
autoselect_reference_bundles=true
If true, bundles that are sticky are 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.
codeword= Provides the "codeword" needed to unlock protected HP
CD-ROM software.
Hewlett-Packard Company - 13 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
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. You may use
this default specification on the command line or the
SD-UX Interactive User Interface to enter the codeword.
This default stores the codeword for future reference,
and you need to enter the codeword only once. If you
purchase a new HP product and a previous codeword has
already been entered for that CD-ROM, just enter the
new codeword as usual and the codewords will be merged
internally.
NOTE: For HP-UX B.10.10 and later systems, SD searches
the .codewords file on the server that is providing
protected software to other hosts. It looks for valid
customer_id/codeword pairs. In doing so, SD eliminates
the need to enter codewords and customer_ids on every
host that is "pulling" the software.
To properly store the customer_id/codeword for a CDROM,
run swinstall -p or swcopy -p on the host serving
the CD-ROM. After the codeword has been stored, clients
installing or copying software using that host and CDROM
as a source will no longer need a codeword or
customer_id.
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: [host][:][/directory]
The controller_source_option supports the same syntax
as the -s source option. This option has no effect on
which sources the target uses and is ignored when used
with the Interactive User Interface.
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 is not created. This option can prevent the
erroneous creation of new target depots or new
alternate root directories.
create_time_filter=0
For cumulative source depots, this option allows
consistent software selections over time by swlist,
Hewlett-Packard Company - 14 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
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
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.
customer_id=
This number, also printed on the Software Certificate,
is used to "unlock" protected software and restrict its
installation to a specific site or owner. It is
entered using the -x customer_id= option or by using
the Interactive User Interface. The customer_id can be
used on any HP-UX 10.0X compatible HP9000 system.
defer_configure=false
(Applies only to swinstall.) Causes swinstall to
automatically configure the software_selections after
they are installed. When an alternate root directory
is specified, swinstall never performs the
configuration task, since only hosts using the software
should be configured. If set to true, this option
allows configuration to be deferred even when the root
directory is /.
An additional version of a product will not be
configured if another version is already configured.
The swconfig command must be run separately.
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.
distribution_target_directory=/var/spool/sw
(Applies only to swcopy.) Defines the default location
Hewlett-Packard Company - 15 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
of the target depot.
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 swinstall and swcopy commands will not proceed
unless the dependencies have also been selected or
already exist at the target in the correct state
(INSTALLED or AVAILABLE). This prevents unusable
software from being installed on the system. It also
ensures that depots contain usable sets of software.
If set to false, dependencies are still checked, but
not enforced. Corequisite dependencies, if not
enforced, may keep the selected software from working
properly. Prerequisite dependencies, if not enforced,
may cause the installation or configuration to fail.
enforce_dsa=true
Prevents the command from proceeding past the analysis
phase if the disk space required is beyond the
available free space of the impacted filesystem(s). If
set to false, the install or copy operation uses the
filesystems' minfree space and may fail because it
reaches the filesystem's absolute limit.
enforce_kernbld_failure=true
(Applies only to swinstall.) Prevents swinstall from
proceeding past the kernel build phase if the kernel
build processes fail. If set to false, the install
operation continues (without suspension if in the
interactive mode) despite failure or warnings from
either the system preparation process or the kernel
build process.
When set to the default value of true, this option
generates an error if a command tries to locate a nonlocatable
fileset. (Locatable filesets are packaged
with the is_locatable attribute set to true). When set
to false, the usual error handling process is
overridden, and SD permits the command to locate the
fileset.
enforce_locatable=true
Controls the handling of errors when locating a nonlocatable
fileset. If set to true, an error is
generated when an attempt is made to locate a nonlocatable
fileset. If false, an attempt is made to
locate the fileset in any case.
Hewlett-Packard Company - 16 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
enforce_scripts=true
Controls the handling of errors generated by scripts.
If true, and a script returns an error, an error
message appears reporting that the execution phase
failed. If false, swinstall attempts to continue
operation. A warning message appears saying that the
analysis or execution phase succeeded. The message
identifies the specific swinstall phase (checkinstall,
preinstall, postinstall, or configure).
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.
installed_software_catalog=products
Defines the directory path where the Installed Products
Database (IPD-information describing the installed
software) is stored. 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 /var/adm/sw 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.
job_title=
The following option applies only to HP
OpenView Software Distributor
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. The default value is to have no title. If a
Hewlett-Packard Company - 17 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
title is specified, it should be enclosed in quotes.
layout_version=1.0
(Applies only to swcopy.) 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 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.
See the description of the layout_version option in
sd(5) for more information.
logdetail=false
Controls the amount of detail written to the logfile.
When set to true, this option adds detailed task
information (such as options specified, progress
statements and additional summary information) to the
logfile. This information is in addition to log
information controlled by the loglevel option.
See loglevel=1 and the sd(5) manual page by typing man
5 sd for more information.
logfile=/var/adm/sw/swremove.log
This is the default command log file for the swinstall
command.
loglevel=1
Controls the log level for the events logged to the
command logfile, the target agent logfile, and the
source agent logfile. This information is in addition
to the detail controlled by the logdetail option. (See
logdetail=false and the sd(5) manual page for more
information.) A value of:
0 provides no information to the logfile.
1 enables verbose logging to the logfiles.
2 enables very verbose logging, including per-file
messages, to the logfiles.
log_msgid=0
Controls whether numeric identification numbers are
prepended to logfile messages produced by SD:
0 (default) No identifiers are attached to messages.
Hewlett-Packard Company - 18 - HP-UX 11i Version 2.0
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
1 Applies to ERROR messages only.
2 Applies to ERROR and WARNING messages.
3 Applies to ERROR, WARNING, and NOTE messages.
4 Applies to ERROR, WARNING, NOTE, and certain other
logfile messages.
match_target=false
(Applies only to swinstall.) 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.
max_targets=25
When set to a positive integer, SD 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 have been completed.
Server and network performance determines the optimal
|