swinstall.1m (2011 03)

s
swinstall(1M) swinstall(1M)
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 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 com-
mand.
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() locking on the file <IPD location> /swlock (for example,
/var/adm/sw/products/swlock).
HP-UX 11i Version 3: March 2011 − 19 − Hewlett-Packard Company 19