swremove.1m (2011 09)

s
swremove(1M) swremove(1M)
Each agent will complete the removal task (if the execution phase has already started) before it wraps up.
This avoids leaving software in a corrupt state.
Terminal Support
For in-depth information about terminal support refer to:
The Software Distributor Administration Guide .
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
swremove session always returns 0. A non-interactive
swremove session returns:
0 The software_selections were successfully removed.
1 The remove operation failed on all target_selections.
2 The remove operation failed on some target_selections.
DIAGNOSTICS
The
swremove command writes to stdout, stderr, and to specific log files.
Standard Output
An interactive
swremove session does not write to stdout. A non-interactive
swremove 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
swremove session does not write to stderr. A non-interactive
swremove session writes
messages for all WARNING and ERROR conditions to stderr.
Logging
Both interactive and non-interactive
swremove sessions log summary events at the host where the com-
mand was invoked. They log detailed events to the
swagent logfile associated with each
target_selection.
Command Log
A non-interactive
swremove
session logs all stdout and stderr messages to the the logfile
/var/adm/sw/swremove.log
. Similar messages are logged by an interactive swremove ses-
sion. The user can specify a different logfile by modifying the
logfile
option.
Target Log
A
swagent process performs the actual remove operation at each target_selection. When remov-
ing installed software, the
swagent logs messages to the file var/adm/sw/swagent.log
beneath the root directory (for example,for example,for example,for example, / or an alternate root
directory). When removing available software (within a depot), the swagent logs messages to the
file swagent.log beneath the depot directory (for example, /var/spool/sw).
You can view command and target log files using the
sd or swjob command.
swagentd Disabled
If the
swagentd daemon has been disabled on the host, it can be enabled by the host’s system adminis-
trator by setting the SW_ENABLE_SWAGENTD entry in /etc/rc.config.d/swconfig
to 1 and exe-
cuting
/usr/sbin/swagentd -r.
EXAMPLES
Preview the remove of the C and Pascal products installed at the local host:
swremove -p cc pascal
Remove the C and Pascal products from several remote hosts:
swremove cc pascal @ hostA hostB hostC
Remove a particular version of HP Omniback:
swremove Omniback,l/opt/Omniback_v2.0
HP-UX 11i Version 3: September 2011 13 Hewlett-Packard Company 13