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

Table 51 Control Script Keywords (continued)
ExampleSize in
Bytes
TypeKeyword
/mfg/sd/scripts/postinstall1024path_stringpostinstall
/mfg/sd/scripts/unpreinstall1024path_stringunpreinstall
/mfg/sd/scripts/unpostinstall1024path_stringunpostinstall
/mfg/sd/scripts/configure1024path_stringconfigure
/mfg/sd/scripts/unconfigure1024path_stringunconfigure
/mfg/sd/scripts/verify1024path_stringverify
/mfg/sd/scripts/checkremove1024path_stringcheckremove
/mfg/sd/scripts/preremove1024path_stringpreremove
/mfg/sd/scripts/postremove1024path_stringpostremove
/mfg/sd/scripts/request1024path_stringrequest
/mfg/sd/scripts/subscripts1024path_stringcontrol_file
/mfg/sd/scripts/fix1024path_stringfix
/mfg/sd/scripts/space1024path_stringspace
The value of each keyword is the source filename for the specific control script. swpackage will
copy the specified control script’s filename into the depot’s storage directory for the associated
product or fileset, using the keyword as the tag of the stored script (for example, “configure”).
You can include control script specifications or data files with the product or fileset. These are
stored alongside the standard SD-UX control scripts. For example, you could specify a subscript
called by the supported control scripts, or a data file read by these scripts. These additional scripts
are specified using the syntax:
PATH[=tag]
If you do not specify the tag component, swpackage uses the basename(1) value of the source
pathname as the tag.
Control Script Location on the File System During Execution
The checkinstall, preinstall, postinstall, and auxiliary scripts for a fileset are downloaded to a
temporary directory from which they are invoked:
<FILESET>/control_script/var/tmp/<CATALOG_DIR>/ \
catalog/<PRODUCT>/
The form of the <CATALOG_DIR> is: aaaa<pid>, where <pid> is the swinstall process ID
number.
The scripts are delivered to that location from the depot immediately after Product Selection has
completed, at the beginning of the Analysis phase and before any system checks have begun. The
temporary directory is removed automatically upon exiting swinstall.
After successful fileset installation, all other control scripts will be located in the IPD. They will be
delivered to that location from the depot as part of the installation of the fileset’s other files:
/var/adm/sw/products/<PRODUCT>/<FILESET>/control_script
The location of the IPD is relative to the root directory under which the software installation is done.
If the installation is to an alternate root, /mnt/disk2 for example, then the IPD for that software
will be under:
/mnt/disk2/var/adm/sw/products/<PRODUCT>/<FILESET>
206 Using Control Scripts