HP-UX Reference (11i v2 07/12) - 5 Miscellaneous (vol 9)

s
sd(5) sd(5)
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 Files
Each invocation of an SD command defines a task session. Most SD commands automatically save task ses-
sion 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 com-
plete. 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:
swpackage.verbose=3
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 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, 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,
396 Hewlett-Packard Company − 26 − HP-UX 11i Version 2: December 2007 Update