HP-UX Reference (11i v2 07/12) - 1M System Administration Commands N-Z (vol 4)

s
swverify(1M) swverify(1M)
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 pro-
duct 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 to 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 products 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
swverify command catches 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.
RETURN VALUES
The swverify command returns:
0 The software_selections were successfully verified.
1 The verify operation failed on all target_selections.
2 The verify operation failed on some target_selections.
DIAGNOSTICS
The swverify command writes to stdout, stderr, and to specific logfiles.
Standard Output
The swverify command writes messages for significant events. These include:
• a begin and end session message,
• selection, analysis, and execution task messages for each target_selection.
538 Hewlett-Packard Company − 9 − HP-UX 11i Version 2: December 2007 Update