Software Distributor Administration Guide for HP-UX 11i

Using Control Scripts
Execution of Control Scripts
Chapter 11390
Configure Scripts
• Configure scripts are executed during the Configuration phase of a
swinstall session. SD expects configure scripts at system start-up if
the swinstall session triggers a system reboot. The swconfig
command can also execute configure scripts. The pathname of the
script being executed is:
$ {SW_CONTROL_DIRECTORY}configure
• A configure script is only executed for installations into the primary
root (“/”). If you choose to defer configuration in the swinstall session,
then the configure script will be executed by a swconfig session at
some time after the installation completes.
• A configure script is usually executed only when the product/fileset is
in the installed state.
• A configure script is the primary way to move a product/fileset from
the installed state to the configured state. The script should perform
all (or most of) the activities needed to enable the product/fileset for
use.
• A configure script can use configuration information provided by the
user and collected by a request script.
• When an existing version of a product is updated to a new version,
the configure script(s) for the new version must perform any
unconfigurations-configurations of the old version that are necessary
to properly configure the new version. The unconfigure script(s) for
the old version are not executed.
• Configure scripts are for architecture-dependent actions because
they will always be run on the architecture of the install target.
• Configure scripts are the best place for removing files and updating
the IPD, since the system is not in transition (i.e. as in an update).
• A configure script can help with software updates as well as new
installs. The script must also be able to handle reinstallation and
should include appropriate error control if data destruction is
possible.