swinstall.1m (2011 03)

s
swinstall(1M) swinstall(1M)
swcopy commands that modify a software depot are restricted from simultaneous modification using
fcntl() locking on the file <depot directory>
/catalog/swlock
(for example,
/var/spool/sw/catalog/swlock
).
Read Locks
Both
swinstall and swcopy commands set fcntl()
read locks on source depots using the
swlock file mentioned above. When a read lock is set, it prevents all SD commands from performing
modifications (that is, from setting write locks).
Terminal Support
For in-depth information about terminal support refer to:
The Software Distributor Administration Guide manual
Start the GUI or TUI, select the Help menu, then select the Keyboard... option to access the Key-
board Reference Guide .
RETURN VALUES
An interactive
swinstall or swcopy session always returns 0. A non-interactive
swinstall or
swcopy session returns:
0 The software_selections were successfully installed/copied.
1 The install/copy operation failed on all target_selections.
2 The install/copy operation failed on some target_selections.
DIAGNOSTICS
The
swinstall and swcopy commands write to stdout, stderr, and to specific logfiles.
Standard Output
An interactive
swinstall or swcopy session does not write to stdout. A non-interactive
swin-
stall or swcopy session writes messages for significant events. These include:
a begin and end session message,
selection, analysis, and execution task messages for each target_selection.
Standard Error
An interactive swinstall or swcopy session does not write to stderr. A non-interactive
swinstall
or swcopy session writes messages for all WARNING and ERROR conditions to stderr.
Logging
Both interactive and non-interactive
swinstall and swcopy sessions log summary events at the host
where the command was invoked. They log detailed events to the
swagent logfile associated with each
target_selection.
Command Log
The
swinstall and swcopy commands log all stdout and stderr messages to the the logfile
/var/adm/sw/swinstall.log (/var/adm/sw/swcopy.log
). Similar messages are logged
by an interactive
swinstall and swcopy session. The user can specify a different logfile by
modifying the logfile option.
Target Log
A
swagent process performs the actual install or copy operation at each target_selection.For
install tasks, the swagent logs messages to the file var/adm/sw/swagent.log beneath the
root directory (for example,
/ or an alternate root directory). For copy tasks, the swagent logs
messages to the file swagent.log beneath the depot directory (for example, /var/spool/sw).
You can view the command and target log files with the
swjob or sd command.
Source Depot Audit Log
If both source and target machine are updated to SD revision B.11.00 or later, the system adminis-
trator 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. (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. See the source_depot_audit option in the swagent (1M) man page.)
20 Hewlett-Packard Company 20 HP-UX 11i Version 3: March 2011