HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swinstall(1M) swinstall(1M)
(Hewlett-Packard Company)
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_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 (e.g.
/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:
• The Software Distributor Administration Guide manual
• Start the GUI or TUI, select the Help menu, then select the Keyboard... option to access the Key-
board Reference Guide.
RETURN VALUES
An interactive
swinstall or swcopy session always returns 0. A non-interactive swinstall or
swcopy session returns:
0 The software_selections were successfully installed/copied.
1 The install/copy operation failed on all target_selections.
2 The install/copy operation failed on some target_selections.
Section 1M−−884 − 18 − HP-UX Release 11i: December 2000
___
___