The following table describes the control script keywords
for use in a PSF.
Table 11-2 Control Script Keywords
Keyword | Type | Size in Bytes | Example |
|---|
checkinstall | path_string | 1024 | /mfg/sd/scripts/checkinstall |
preinstall | path_string | 1024 | /mfg/sd/scripts/preinstall |
postinstall | path_string | 1024 | /mfg/sd/scripts/postinstall |
unpreinstall | path_string | 1024 | /mfg/sd/scripts/unpreinstall |
unpostinstall | path_string | 1024 | /mfg/sd/scripts/unpostinstall |
configure | path_string | 1024 | /mfg/sd/scripts/configure |
unconfigure | path_string | 1024 | /mfg/sd/scripts/unconfigure |
verify | path_string | 1024 | /mfg/sd/scripts/verify |
checkremove | path_string | 1024 | /mfg/sd/scripts/checkremove |
preremove | path_string | 1024 | /mfg/sd/scripts/preremove |
postremove | path_string | 1024 | /mfg/sd/scripts/postremove |
request | path_string | 1024 | /mfg/sd/scripts/request |
control_file | path_string | 1024 | /mfg/sd/scripts/subscripts |
| fix | path_string | 1024 | /mfg/sd/scripts/fix |
| space | path_string | 1024 | /mfg/sd/scripts/space |
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>
|
| |
|
 | NOTE: All necessary directories under /var/adm/sw will be created by the SD-UX process. All files under
those directories will be filled by SD-UX initiated processes. Files
must never be delivered directly under /var; it is a private directory. |
|
| |
|
Printable version
