swremove.1m (2012 03)
s
swremove(1M) swremove(1M)
NAME
swremove - unconfigure and remove software products
SYNOPSIS
swremove [XToolkit Options ][
-d|-r][-i][-p][-v
][-C session_file][-f software_file]
[
-J jobid][-Q date ][
-S session_file][-t target_file][-x option=value ][-X
option_file]
[software_selections][
@ target_selections]
Remarks
•
swremove supports an interactive user interface (GUI) that can be invoked alone or by the
sd
command. See Interactive Operation below.
• This command supports operations on remote systems. See Remote Operation below.
• For an overview of all SD commands, see the sd(5) man page by typing
man5sdon the com-
mand line.
DESCRIPTION
The
swremove command removes software_selections from target_selections (for example, root file sys-
tems). When removing installed software,
swremove also unconfigures the software before it is
removed. The software is not unconfigured when removed from an alternate root directory since it was
not configured during installation. When removing available software (within a depot),
swremove also
does not perform the unconfiguration task.
When
HP-UX Containers (SRP) is installed and enabled, the swremove command behavior is
changed to support software management for system containers. (For more information on HP-UX Con-
tainers, refer to srp(1M) and container_system(5) manpages.)
NOTE : Selecting a bundle for removal does not always remove all filesets in that bundle. If a particular
fileset is required by another bundle, that fileset will not be removed. For example, if the bundles
Pas-
cal and FORTRAN both use the fileset Debugger.Run and you try to remove FORTRAN, the fileset
Debugger.Run will not be removed because it is also used by the bundle Pascal. This prevents the
removal of one bundle from inadvertently causing the removal of filesets needed by another bundle.
Remote Operation
You can enable Software Distributor (SD) to manage software on remote systems. To let the root user
from a central SD controller (also called the central management server or manager node) perform opera-
tions on a remote target (also called the host or agent ):
1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit
root access from the controller system. To do this, run the following command on each remote sys-
tem:
/usr/lib/sw/mx/setaccess
controller
NOTES:
• controller is the name of the central management server.
• If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed
on remote system before running
setaccess.
• If remote system is older than 11.00 or for some other reason does not have
setaccess in place,
copy setaccess script from an 11.11 or higher system to the remote system.
2)
swinstall, swcopy, and swremove have enhanced GUI interfaces for remote operations. Enable
the enhanced GUIs by creating the .sdkey file on the controller. Use this command:
touch /var/adm/sw/.sdkey
NOTE: You can also set up remote access by using the swacl directly on the remote machines to grant
root or non-root access to users from the controller system.
Interactive Operation
swremove supports a graphical user interface (GUI) or a terminal user interface (in which screen navi-
gation is done with the keyboard and no mouse) if your terminal or display cannot support the GUI.
To invoke the GUI, type
HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1