Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Introduction to Control Scripts
Chapter 11 371
Types of Control Scripts
Here are the control scripts that SD-UX supports:
• Checkinstall Script
This script is run by swinstall during its Analysis phase to insure
that the installation (and configuration) can be attempted. For
example, the OS run state, running processes, or other prerequisite
conditions beyond dependencies could be checked. It should not
change the state of the system.
A checkinstall script’s chief merit is its ability to detect if the system
contains a hardware configuration that might lead to catastrophe -
an unbootable system or file system corruption - if the installation of
the selected software was allowed to proceed. It also acts as the test
for conflicts with other software selections or with software already
installed.
• Preinstall Script
This script is run by swinstall before loading the software files. For
example, this script could remove obsolete files, or move an existing
file aside during an update.
A preinstall script is called during swinstall’s Execution Phase. The
preinstall script for each file is executed just before that fileset’s files
are installed onto the target system. A product level preinstall script
is called before a product’s filesets.
Preinstall scripts for all kernel filesets and their prerequisites are all
run before the kernel build takes place. If the kernel build fails and
swinstall exits, the preinstall scripts are removed from the system.
Product level preinstall scripts are invoked twice for all products
that contain kernel filesets: once when the kernel filesets are their
prerequisites are installed; a second time when the remaining
filesets are installed.