Software Distributor Administration Guide (March 2009)

when installing to a system that will actually be using the software. They are
deferred when installing to an alternate root (for example, for diskless or building
test file systems) and run instead by the swconfig command when the alternate
root is now the root of the system using the software.
The swconfig command can also be used to rerun configure scripts that failed
during a normal install. A successful execution of the configure step (whether
there is a script or not) moves the software from the installed state to the configured
or ready-to-use state. Configure scripts (and all others) must be able to be run
many times (that is, they must be re-executable).
Configure scripts are a good place to remove obsolete files.
Configure scripts are not run for installations to alternate roots.
• Verify Script
Verify scripts are run by the swverify command any time after the software has
been installed and configured. Like other scripts, they are intended to verify
anything that the SD-UX software management tools do not verify by default. For
example, this script could check to see that the software is configured properly
and that you have a proper license to use it.
• Fix Script
Defines the fix script run by swverify to correct and report problems on installed
software. The fix script can create missing directories, correct file modifications
(mode, owner, group, major, and minor), and recreate symbolic links.
• Unconfigure Script
A script run by swconfig or swremove to undo a host or software configuration
originally performed by a configure script. For example, an unconfigure script
could remove the configuration from the /etc/services file. (The unconfigure
task moves the software from the configured state back to the installed state.)
Only the swremove command actually removes software, although you can run
unconfigure scripts using swconfig. Unconfigure scripts are not run for removals
from alternate roots.
• Checkremove Scripts
The checkremove script is run by swremove during the remove analysis phase to
allow any checks before the software is permanently removed. For example, the
script could check whether anyone was currently using the software before
removing it.
• Preremove Scripts
This script is executed just before removing files. It can be destructive to the
application because files will be removed next. It could remove files that the
postinstall script created. For example, a preremove script could save a specific
fileset to another location before removing the rest of the filesets in the product.
268 Using Control Scripts