HP-UX Reference (11i v2 07/12) - 5 Miscellaneous (vol 9)

s
sd(5) sd(5)
("cold" install).
SW_KERNEL_PATH
Only applies to swinstall. 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
Only applies to swinstall. The path to the kernel’s system file. The default value is
/stand/system .
Signals
The SD 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 comple-
tion, 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.
The following paragraph applies only to swconfig, swcopy, swinstall, swremove, and swverify.
For SIGUSR1, the command sends an RPC to the agents to quit immediately, as if the agent had received a
SIGTERM signal. When SIGUSR1 is sent to the SD Controller, it shuts down target agents with SD revi-
sion B.11.01 or later, then shuts itself down. When the target agent receives the shutdown RPC, it invokes
its handler for signal 15 (SIGTERM), which resembles what happens if a superuser on the target machine
used a kill command on the target agent process.
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() locking on the file
var/adm/sw/products/swlock
relative to the root directory (for example, /var/adm/sw/products/swlock
).
The SD commands which modify software in a depot are restricted from simultaneous modification using
fcntl() locking on the file
catalog/swlock
relative to the depot directory (for example, /var/spool/sw/catalog/swlock).
All commands set fcntl() 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 (that is, from set-
ting write locks).
HP-UX 11i Version 2: December 2007 Update − 29 − Hewlett-Packard Company 399