Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Execution of Control Scripts
Chapter 11 391
Unconfigure Scripts
• Unconfigure scripts are executed during the
Unconfiguration-Configuration phase of a swremove session. They
can also be executed by the swconfig command. The pathname of the
script being executed is:
$ {SW_CONTROL_DIRECTORY}unconfigure
• An unconfigure script is executed only for software installed into the
primary root (“/”).
• An unconfigure script is re-executed even when the product/fileset is
in the configured state.
• An unconfigure script is the primary way to move a product/fileset
from the configured state back to the installed state. The script
should perform all (or most of) the activities needed to disable the
product/fileset for use.
• An unconfigure script must undo all configuration tasks performed
by its companion configure script. The user should be able to
configure, unconfigure, configure, etc. an installed product/fileset and
always end up with the same configured result.
Verify Scripts
• Verify scripts are executed by the swverify command. The pathname
of the script being executed is:
$ {SW_CONTROL_DIRECTORY}verify
• A verify script must not modify the system.
• A verify script is the primary way to check the configuration tasks
performed by a configure script for correctness and completeness.
• A verify script is executed for installations into the primary root (“/”)
or an alternate root. Since most of the actions of this script will
involve checking the current conditions of a configured
product/fileset (in the primary root), it may not need to perform any
actions for a product/fileset installed into an alternate root directory.
• An environment variable, SW_IS_COMPATIBLE, can help a verify
script determine if installed software is compatible with the system
on which it is installed. See “SW_IS_COMPATIBLE” on page 386.