swconfig.1m (2011 03)

s
swconfig(1M) swconfig(1M)
SW_CONFIG_AFTER_REBOOT
This variable should be read only by the
configure script. If this is set to any value
it indicates the
configure script was invoked by the
swconfig command during
system startup. This variable is set by the
/sbin/init.d/swconfig
system
startup script.
SW_CONTROL_DIRECTORY
Defines the current directory of the script being executed, either a temporary catalog
directory, or a directory within in the Installed Products Database (IPD). This vari-
able tells scripts where other control scripts for the software are located (for example,
subscripts).
SW_CONTROL_TAG
Holds the tag name of the control_file being executed. When packaging software, you
can define a physical name and path for a control file in a depot. This lets you define
the control_file with a name other than its tag and lets you use multiple control file
definitions to point to the same file. A control_file can query the
SW_CONTROL_TAG
variable to determine which tag is being executed.
SW_LOCATION
Defines the location of the product, which may have been changed from the default
product directory. When combined with the SW_ROOT_DIRECTORY
, this variable
tells scripts where the product files are located.
SW_PATH A PATH variable which defines a minimum set of commands available for use in a
control script (for example, /sbin:/usr/bin
).
SW_ROOT_DIRECTORY
Defines the root directory in which the session is operating, either "/" or an alternate
root directory. This variable tells control scripts the root directory in which the pro-
ducts are installed. A script must use this directory as a prefix to SW_LOCATION
to
locate the product’s installed files. The configure script is only run when
SW_ROOT_DIRECTORY
is /.
SW_SESSION_OPTIONS
Contains the pathname of a file containing the value of every option for a particular
command, including software and target selections. This lets scripts retrieve any com-
mand options and values other than the ones provided explicitly by other environment
variables. For example, when the file pointed to by
SW_SESSIONS_OPTIONS
is
made available to a request script, the targets option contains a list of
software_collection_specs for all targets specified for the command. When the file
pointed to by
SW_SESSIONS_OPTIONS
is made available to other scripts, the targets
option contains the single software_collection_spec for the targets on which the script
is being executed.
SW_SOFTWARE_SPEC
This variable contains the fully qualified software specification of the current product
or fileset. The software specification allows the product or fileset to be uniquely
identified.
Signals
The
swconfig command catches the signals SIGQUIT and SIGINT, and SIGUSR1. If these signals are
received, swconfig 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.
Each agent will complete the configuration task (if the execution phase has already started) before it
wraps up. This avoids leaving software in a corrupt state.
10 Hewlett-Packard Company − 10 − HP-UX 11i Version 3: March 2011