HP-UX Reference (11i v1 05/09) - 1M System Administration Commands N-Z (vol 4)
s
swinstall(1M) swinstall(1M)
(HP-UX Software Distributor)
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, the
swinstall session is being run as the
back end of an initial system software installation ("cold" install).
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 kernel filesets are also reboot filesets, the values of this variables is always equal to the
value of SW_SESSION_IS_KERNEL
.
SW_SESSION_IS_UPDATE
A value of 1 indicates the SD command was invoked by the update-ux command during
an Operating System update. This variable is set by the update-ux command.
SW_SYSTEM_FILE_PATH
The path to the kernel’s system file. The default value is /stand/system
.
Signals
The
swinstall and swcopy commands catch the signals SIGQUIT, SIGINT, and SIGUSR1. If these
signals are received, the command prints a message, sends a Remote Procedure Call (RPC) to the agents to
wrap up after completion, 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 the Installed Products Data-
base (IPD) and software depots. This mechanism allows multiple readers but only one writer on an IPD or
depot:
Write Locks
swinstall commands that modify the IPD are restricted from simultaneous modification using fcntl(2)
locking on the file <IPD location>/swlock (e.g. /var/adm/sw/products/swlock
).
swcopy commands that modify a software depot are restricted from simultaneous modification using
fcntl(2) locking on the file <depot directory>/catalog/swlock
(for example,
/var/spool/sw/catalog/swlock).
Read Locks
Both
swinstall and swcopy commands set fcntl(2) read locks on source depots using the swlock
file mentioned above. When a read lock is set, it prevents all SD commands from performing modifications
(i.e. from setting write locks).
Terminal Support
For in-depth information about terminal support refer to:
HP-UX 11i Version 1: September 2005 − 18 − Hewlett-Packard Company Section 1M−−935