swinstall.1m (2011 09)

s
swinstall(1M) swinstall(1M)
example, subscripts).
SW_CONTROL_TAG
Holds the tag name of the control_file being executed. When packaging software, you
can define a physical name and path for a control file in a depot. This lets you define
the control_file with a name other than its tag and lets you use multiple control file
definitions to point to the same file. A control_file can query the
SW_LOCATION
Defines the location of the product, which may have been changed from the default
product directory. When combined with the SW_ROOT_DIRECTORY
, this variable
tells scripts where the product files are located.
SW_PATH A PATH variable which defines a minimum set of commands available to for use in a
control script (for example, /sbin:/usr/bin
).
SW_ROOT_DIRECTORY
Defines the root directory in which the session is operating, either "/" or an alternate
root directory. This variable tells
control scripts the root directory in which the
products are installed. A script must use this directory as a prefix to
SW_LOCATION
to locate the product’s installed files. The configure script is only run when
SW_ROOT_DIRECTORY
is /.
SW_SESSION_OPTIONS
Contains the pathname of a file containing the value of every option for a particular
command, including software and target selections. This lets scripts retrieve any com-
mand options and values other than the ones provided explicitly by other environment
variables. For example, when the file pointed to by SW_SESSIONS_OPTIONS
is
made available to a request script, the targets option contains a list of
software_collection_specs for all targets specified for the command. When the file
pointed to by
SW_SESSIONS_OPTIONS
is made available to other scripts, the targets
option contains the single software_collection_spec for the targets on which the script
is being executed.
SW_SOFTWARE_SPEC
This variable contains the fully qualified software specification of the current product
or fileset. The software specification allows the product or fileset to be uniquely
identified.
Additional environment variables that affect scripts for
swinstall:
SW_DEFERRED_KERNBLD
This variable is normally unset. If it is set, the actions necessary for preparing the
system file /stand/system
cannot be accomplished from within the postinstall
scripts, but instead must be accomplished by the configurescripts. This occurs when-
ever software is installed to a directory other than
/, such as for a cluster client sys-
tem. This variable should be read only by the configure and postinstall scripts of a
kernel fileset. The swinstall command sets these environment variables for use by
the kernel preparation and build scripts.
SW_INITIAL_INSTALL
This variable is normally unset. If it is set to 1, the swinstall session is being run
as the back end of an initial system software installation ("cold" install). If it is unset
or set to any other value,then it is not a cold-install session.
SW_KERNEL_PATH
The path to the kernel. The default value is /stand/vmunix, defined by the
swagent option or kernel_path.
SW_SESSION_IS_KERNEL
Indicates whether a kernel build is scheduled for the current install/remove session. A
TRUE value indicates that the selected kernel fileset is scheduled for a kernel build
and that changes to /stand/system are required. A null value indicates that a
kernel build is not scheduled and that changes to /stand/system are not required.
The value of this variable is always equal to the value of
SW_SESSION_IS_REBOOT.
SW_SESSION_IS_REBOOT
Indicates whether a reboot is scheduled for a fileset selected for removal. Because all
HP-UX 11i Version 3: September 2011 − 19 − Hewlett-Packard Company 19