HP-UX Reference (11i v2 07/12) - 1M System Administration Commands N-Z (vol 4)

s
swinstall(1M) swinstall(1M)
above). If there is more than one target selection, they must be separated by spaces.
uncompress_files=false
(Applies only to swcopy.) If set to
true, files being transferred from a source are
uncompressed before
swcopy store them on the target depot.
use_alternate_source=false
Empowers each target agent to use its own, configured alternate source, instead of the one
specified by the user. If
false, each target agent uses the same source (the source
specified by the user and validated by the command). If
true, each target agent uses its
own configured value for the source.
verbose=1
Controls the verbosity of the output (stdout). A value of
0 disables output to stdout. (Error and warning messages are always written to stderr).
1 enables verbose messaging to stdout.
write_remote_files=false
Prevents the installation or copying of files to a target which exists on a remote filesystem.
All files destined for a remote filesystem are skipped.
If set to
true and if the superuser has write permission on the remote filesystem, the
remote files are installed or copied.
Session File
Each invocation of the swinstall or swcopy command defines an installation or copy session. The
invocation options, source information, software selections, and target hosts are saved before the installa-
tion or copy task actually commences. This lets you re-execute the command even if the session ends
before proper completion.
Each session is saved to the file $HOME/.sw/sessions/swinstall{swcopy}.last
. This file is
overwritten by each invocation of
swinstall or swcopy.
You can also save session information from interactive or command-line sessions. From an interactive ses-
sion, 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. From a command-line session, you can save session information by execut-
ing
swinstall or swcopy with the -C session__file option.
A session file uses the same syntax as the defaults files. You can specify an absolute path for a session file.
If you do not specify a directory, the default location for a session file is
$HOME/.sw/sessions/.
To re-execute a saved session from an interactive session, use the Recall Session option from the File menu.
To re-execute a session from a command-line, specify the session file as the argument for the
-S
session__file option of swinstall or swcopy.
Note that 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 or parameters that you specify when you
invoke swinstall or swcopy take precedence over the values in the session file.
Software and Target Lists
Most 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. swin-
stall
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, the
swinstall and swcopy interactive user interfaces read a default list of hosts on which
to operate. The list is stored in:
/var/adm/sw/defaults.hosts the system-wide default list of hosts
$HOME/.swdefaults.hosts the user-specific default list of hosts
For each interactive command, target hosts containing roots and target hosts containing depots are
specified in separate lists ( hosts, 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}
HP-UX 11i Version 2: December 2007 Update − 16 − Hewlett-Packard Company 467