HP-UX Reference (11i v1 05/09) - 1M System Administration Commands N-Z (vol 4)

s
swpackage(1M) swpackage(1M)
(HP-UX Software Distributor)
To re-execute a session file, specify the session file as the argument for the
-S session__file option of
swpackage.
Note that when you re-execute a session file, the values in the session file take precedence over values in
the system defaults file. Likewise, any command line options or parameters that you specify when you
invoke swpackage take precedence over the values in the session file.
Environment Variables
The environment variable that affects
swpackage is:
LANG Determines the language in which messages are displayed. If LANG is not specified or is
set to the empty string, a default value of
C is used. See the lang(5) man page by typing
man 5 lang for more information.
NOTE: The language in which the SD agent and daemon log messages are displayed is set
by the system configuration variable script,
/etc/rc.config.d/LANG
. For example,
/etc/rc.config.d/LANG
, must be set to
LANG=ja_JP.SJIS
or
LANG=ja_JP.eucJP
to make the agent and daemon log messages display in Japanese.
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 beginning with 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.
Signals
The swpackage command catches the signals SIGQUIT and SIGINT. If these signals are received, the
command prints a message, sends a Remote Procedure Call (RPC) to the agents to wrap up, and then exits.
The agent ignores SIGHUP, SIGINT, and SIGQUIT. It immediately exits gracefully after receiving
SIGTERM, SIGUSR1, or SIGUSR2. Killing the agent may leave corrupt software on the system, and thus
should only be done if absolutely necessary. Note that when an SD command is killed, the agent does not
terminate until completing the task in progress.
The daemon ignores SIGHUP, SIGINT and SIGQUIT. It immediately exits gracefully after receiving
SIGTERM and SIGUSR2. After receiving SIGUSR1, it waits for completion of a copy or remove from a
depot session before exiting, so that it can register or unregister depots if necessary. Requests to start new
sessions are refused during this wait.
Locking
SD commands use a common locking mechanism for reading and modifying both root directories and
software depots. This mechanism allows multiple readers but only one writer on a root or depot.
The SD commands which modify software in an (alternate) root directory are restricted from simultaneous
modification using fcntl(2) locking on the file
var/adm/sw/products/swlock
relative to the root directory (e.g. /var/adm/sw/products/swlock).
The SD commands which modify software in a depot are restricted from simultaneous modification using
fcntl(2) locking on the file
catalog/swlock
relative to the depot directory (e.g. /var/spool/sw/catalog/swlock
).
All commands set fcntl(2) read locks on roots and depots using the
swlock file mentioned above. When a
read lock is set, it prevents other SD commands from performing modifications (i.e. from setting write
locks).
HP-UX 11i Version 1: September 2005 − 8 − Hewlett-Packard Company Section 1M−−973