Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Execution of Control Scripts
Chapter 11388
• The set of control scripts executed during a particular phase of a task
are always executed in prerequisite order the scripts of each
prerequisite product/fileset are executed before the script of the
dependent fileset.
• All control scripts are readable by any other control script.
Checkinstall Scripts
• Checkinstall scripts are executed during the Analysis phase of a
swinstall session. The pathname of the script being executed is:
$ {SW_CONTROL_DIRECTORY}checkinstall
• A checkinstall script must not modify the system.
• A checkinstall script determines whether the product/fileset can be
installed by performing checks beyond those performed by swinstall.
Example checks include checking to see if the product/fileset is
actively in use, or checking that the system run-level is appropriate.
• If you are using a request script as part of the install, the
checkinstall script should:
— Verify that the response file exists.
— Prevent swinstall from “hanging” if:
— A script tries to read a response file that does not exist, or
— The install or configuration relies on information in the
missing response file.
• If the checkinstall script fails, the fileset will not be installed. The
interactive interface of swinstall will notify you that the checkinstall
script has failed. Then you can: diagnose the problem, fix it and
re-execute the analysis phase; or unselect the product/fileset. The
non-interactive interface tells you about each individual checkinstall
failure and the filesets are not installed.
• A checkinstall 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 running system
(that is, the primary root), it may not need to perform any actions
when the product/fileset is being installed into an alternate root.