Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Introduction to Control Scripts
Chapter 11 373
NOTE Product level unpostinstall scripts are not supported.
• Configure Script
This script is run by swinstall or by swconfig to configure the host for
the software, or configure the software for host-specific information.
For example, this script could change a host’s specific configuration
file such as /etc/services, add the host name or other host
resources such as available printers to its own configuration file, or
perform compilations.
Configure scripts are run by swinstall for all products (in
prerequisite order) after the products have completed the Load
phase. However, they are only run 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.