Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

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.
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.
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:
interpreter interpreter_name
For example:
control_file
source scripts
tag checkinstall
interpreter ksh
SD checks that the interpreter is available. If the interpreter is not available, the script fails. (To
avoid this problem, you can use a checkinstall script to verify the existence of any script interpreters
that you specify.) If SD finds the interpreter, it processes the script normally using the interpreter
that you specified.
204 Using Control Scripts