swverify.1m (2012 03)

s
swverify(1M) swverify(1M)
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.
Standard Error
The swverify command also writes messages for all WARNING and ERROR conditions to stderr.
Logging
The
swverify command logs summary events at the host where the command was invoked. It logs
detailed events to the swagent logfile associated with each target_selection.
Command Log
The
swverify command logs all stdout and stderr messages to the the logfile
/var/adm/sw/swverify.log. (The user can specify a different logfile by modifying the log-
file option.)
Target Log
A
swagent process performs the actual verify operation at each target_selection. When verifying
installed software, the swagent logs messages to the file var/adm/sw/swagent.log beneath
the root directory (for example, / or an alternate root directory). When verifying available
10 Hewlett-Packard Company − 10 − HP-UX 11i Version 3: March 2012