HP-UX Reference (11i v1 00/12) - 5 Miscellaneous Topics, 7 Device (Special) Files, 9 General Information, Index (vol 9)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man5/!!!intro.5
________________________________________________________________
___ ___
s
sd(5) sd(5)
(Hewlett-Packard Company)
LC_ALL
Determines the locale to be used to override any values for locale categories specified by the
settings of LANG or any environment variables beginningwith LC_.
LC_CTYPE
Determines the interpretation of sequences of bytes of text data as characters (e.g., single-
versus multibyte characters in values for vendor-defined attributes).
LC_MESSAGES
Determines the language in which messages should be written.
LC_TIME
Determines the format of dates (create_date and mod_date) when displayed by swlist.
Used by all utilities when displaying dates and times in stdout, stderr, and logging.
TZ Determines the time zone for use when displaying dates and times.
Environment variables that affect scripts:
SW_CATALOG
Holds the path to the Installed Products Database (IPD), relative to the path in the
SW_ROOT_DIRECTORY environment variable. Note that you can specify a path for the IPD
using the installed_software_catalog
default option.
SW_CONTROL_DIRECTORY
Defines the current directory of the script being executed, either a temporary catalog directory,
or a directory within in the Installed Products Database (IPD). This variable tells scripts where
other control scripts for the software are located (e.g. 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_CONTROL_TAG
variable to determine which tag is being exe-
cuted.
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 for use in a control script
(e.g.
/sbin:/usr/bin).
SW_ROOT_DIRECTORY
Defines the root directory in which the session is operating, either "/" or an alternate root direc-
tory. 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 command 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 com-
mand. 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 run by
swinstall and swremove:
SW_DEFERRED_KERNBLD
Only applies to swinstall. 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 postin-
stall scripts, but instead must be accomplished by the configurescripts. This occurs whenever
HP-UX Release 11i: December 2000 − 28 − Section 5−−323
___
___