Software Distributor Administration Guide (March 2009)

This script and the postremove script are part of the Remove phase of swremove.
Within each product, preremove scripts are run (in the reverse order dictated by
any prerequisites), files are removed, then all postremove scripts are run.
• Postremove Scripts
This script is executed just after removing files. It is the companion script to the
postinstall script. For example, if this was a patch fileset, then the preinstall script
could move the original file aside, and this postremove script could move the
original file back if the patch was removed.
• Request Scripts
This interactive script requests a response from the user as part of software
installation or configuration. Request scripts write information into a response file
for later use by the configure script or other scripts. You can run requests scripts
by executing the swask command or using the ask option with swinstall or
swconfig after selection and before the analysis phase.
• Other Scripts
You can include other control scripts, such as a subscript that is sourced by the
above scripts. The location of the control scripts is passed to all scripts via the
SW_CONTROL_DIRECTORY environment variable, and are denoted by the keyword
control_file within the PSF.
11.1.1.1 Space Files
The space control file is not a script. It lets you define additional disk space requirements
for the filesets and notes positive disk space impact on any directory or file that results
from the actions of control scripts.
Each fileset or product may contain a space file. The space file lists a path and a byte
size for each path. For example:
/tmp/space_dummy1 2000
/opt/space_dummy2 2000
/tmp/space_dummy3 3000
/mydir/ 4000
For each directory or file path listed in the space file, swinstall adds the size in bytes
to the disk space requirements. The size reflects the maximum transient or permanent
disk space required for the install.
11.1.1.2 Script Interpreter
By default, SD interprets scripts with a POSIX shell (sh). You can specify other script
interpreters in two ways.
First, any control script can define an interpreter in the first line of the script.
Second, you can use the interpreter keyword to define a different interpreter for
specific scripts. The syntax is:
11.1 Introduction to Control Scripts 269