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

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swremove(1M) swremove(1M)
(Hewlett-Packard Company)
swremove on the command line (without command-line arguments) or include -i with any other
command-line options when you invoke swremove from the command line.
The sd command provides an interactive interface for monitoring software jobs. You can also use it to
invoke the swinstall, swcopy,orswremove GUIs.
If you have enabled SD’s central management features, swinstall, swcopy, and swremove provide
enhanced GUIs to support operations on remote machines. See Remote Operations above.
Removing Patches or Patch Rollback Files
To remove patch software, rollback files corresponding to the patch must be available for rollback. You must
remove the base software modified by the patch. (Removing the base software also removes the patches
associated with that software.)
To commit (make permanent) a patch, use the swmodify command’s patch_commit option to remove
the files saved for patch rollback, or use the swinstall command’s save_patch_files option to not save
them initially. See swmodify(1M) and swinstall(1M) for more information.
Control Scripts
When removing installed software, the swremove command executes several vendor-supplied scripts (if
they exist) during the removal of the software_selections. The
swremove command supports the follow-
ing scripts:
checkremove
a script executed during the analysis of each target_selection, it checks to make sure the removal
can be attempted. If this check fails, the software product will not be removed.
preremove
a script executed immediately before the software files are removed.
postremove
a script executed immediately after the software files are removed.
unconfigure
a script executed during the unconfiguration of each target_selection, it unconfigures the host for
the software (and the software for the host). The
preremove and postremove scripts are
not intended for unconfiguration tasks. They are to be used for simple file management needs
such as restoring files moved during install. The unconfigure script allows the swremove
command to unconfigure the hosts on which it has been running before removing the software
specified.
Options
The swremove supports the following options:
XToolKit Options
The swremove command supports a subset of the standard X Toolkit options to con-
trol the appearance of the GUI. The supported options are: -bg, -background,
-fg, -foreground, -display, -name, -xrm, and -synchronous . See the
X(1) manual page for a definition of these options.
-d Operate on a depot rather than installed software.
-r Operates on an alternate root directory, which must be specified the @
target_selections option. Note that unconfigure scripts are not run when removing
software from an alternate root directory. (This option is not required for alternate
root operations but is maintained for backward compatibility. See the
Alternate
Root Directory and Depot Directory
heading in sd(5) for more informa-
tion.)
-i Runs the command in interactive mode (Graphical User Interface). See the
Interactive Operation and Remote Operation headings above for addi-
tional details.
-p Previews a remove task by running the session through the analysis phase only.
-v Turns on verbose output to stdout. (The swremove log file is not affected by this
option.) Verbose output is controlled by the default verbose=x.
HP-UX Release 11i: December 2000 2 Section 1M931
___
___