Verifying Your Installation (swverify)

The swverify command verifies depot, installed, or configured software products on the specified host.

Features and Limitations

Determines whether installed or configured software is compatible with the host on which that software is installed.
Makes sure that all dependencies (prerequisites, corequisites) are being met (for installed software) or can be met (for copied software).
Executes verification scripts that check the correctness of the product’s configuration (that is, scripts verify that the installed state of the software is configured).
Executes fix scripts to correct or report problems with installed software:
Fix
Corrects and reports on problems in installed software. Typical uses are to create missing directories, correct file modifications (mode, owner, group, major, minor), and to recreate missing symbolic links.
Verify
Verifies the configuration of filesets or products, in addition to the standard swverify checks.
(See Chapter 11: “Using Control Scripts ” for more information.)
Reports missing files, checks all file attributes including permissions, file types, size, checksum, mtime, link source and major/minor attributes.
Uses dependencies to automatically select software on which to operate (in addition to any software you specify directly). See “Software Dependencies ” for more information.

The Verification Process

The software verification process has only two phases: selection and analysis.

Phase I: Selection

This phase consist of swverify resolving all information on the command line, including all necessary host, software, dependency, and product information.

Phase II: Analysis

The analysis phase for swverify takes place on the host. The host’s environment is not modified.

The sequential analysis tasks on each host are:

Initiate analysis
Process software selections. The system accesses the Installed Products Database (IPD) or depot catalog to get the product information for the selected software:
For installed software, the system checks that all products are compatible with its uname attributes. This check is controlled by the default option allow_incompatible:
- If allow_incompatible is set to false, the system produces an error stating that the product is not compatible with the host.
- If allow_incompatible is set to true, a warning is issued stating that the product is not compatible.
Check for correct states in the filesets (installed, configured or available). For installed software, swverify also checks for multiple versions that are controlled by the allow_multiple_versions option:
- If allow_multiple_versions is false, an error is produced that multiple versions of the product exist and the option is disabled.
- If allow_multiple_versions is true, a warning is issued saying that multiple versions exist.
Check dependencies. An error or warning is issued if a dependency cannot be met. Dependencies are controlled by the enforce_dependencies option:
- If enforce_dependencies is true, an error is generated telling you the type of dependency and what state the product is in.
- If enforce_dependencies is false, a warning is issued with the same information.
- If the dependency is a corequisite, it must be present before the software will operate.
- If the dependency is a prerequisite, it must be present before the software can be installed or configured.
Execute verify or fix scripts on installed software in prerequisite order.
A verify script is used to ensure that the configuration of the software is correct. Possible vendor-specific tasks for a verify script include:
- Determine active or inactive state of the product.
- Check for corruption of product configuration files.
- Check for (in)correct configuration of the product into the OS platform, services or configuration files.
- Check licensing factors.
Vendor-supplied scripts are executed and the return values generate an ERROR (1) or a WARNING (2).
Scripts are executed in prerequisite order.
Perform file-level checks for:
- Contents (mtime, size and checksum) for control_files
- Contents (mtime, size and checksum) for files
- Missing control_files, files and directories
- Permissions (owner, group, mode) for installed files
- Proper symlink values

Using swverify

Syntax

swverify  [-d|-r] [-F][-v] [-C session_file] [-f software_file]
[-Q date] [-S session_file] [-t target_file]
[-x option=value] [-X option_file]
[software_selections][@ target_selections]

Options & Operands

-d: Operate on a depot rather than installed software. See “Verifying a Depot (swverify -d) ”
-r: Operate on an alternate root rather than /. Verify scripts are not run.
-v: Turn on verbose output to stdout and display all activity to the screen. Lets you see the results of the command as it executes.
-C session_file: Run the command and save the current option and operand values to session_file for re-use in another session. See “Session Files”.
-F: Run a fix script. See “Fix Scripts”.
-f software_file: Read a list of software selections from a separate file instead of (or in addition to) the command line. See “Software Files”.
-Q date: Schedules a job for the given date when remote operations are enabled. See “Scheduling Jobs from the Command Line” and Chapter 7: “Remote Operations Overview”
-S session_file: Run the command based on values saved from a previous verify session, as defined in session_file. See “Session Files”.
-t target_file: Read a list of target selections from a separate file instead of (or in addition to) the command line. See “Target Files”.
-x option=value: Sets a command option to value and overrides default values or a values in options files. See “Changing Command Options ”.
-X option_file: Read session options and behaviors from option_file. See “Changing Command Options ”.
software_selections: The software objects to be verified. See “Software Selections”.
target_selections: The target of the command. See “Target Selections”.

Changing Command Options

You can change the behavior of this command by specifying additional command-line options when you invoke the command (using the -xoption) or by reading predefined values from a file. The following table shows the defaults and options that apply to swverify.

Table 2-6 swverify Command Options and Default Values

admin_directory=/var/spool/sw
agent_auto_exit=true
agent_timeout_minutes=10000
allow_incompatible=false
allow_multiple_versions=false
autoremove_job=false
autoselect_dependencies=true
autoselect_minimum_dependencies=false
check_contents=true
check_contents_uncompressed=false
check_contents_use_cksum=true
check_permissions=true
check_requisites=true
check_scripts=true
check_volatile=false
controller_source=
distribution_target_directory= /var/spool/sw
enforce_dependencies=true

fix=false
installed_software_catalog=products
job_title=
log_msgid=0
logdetail=false
logfile=/var/adm/sw/swverify.log
loglevel=1
mount_all_filesystems=true
reuse_short_job_numbers=true
rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
rpc_timeout=5
run_as_superuser=true
select_local=true
software=
target_directory=
verbose=1

For More Information

See Appendix A for more information about setting options and a complete listing and description of each option.

Verification Tasks and Examples

To verify an installed fileset mysoft.myfileset located on the default depot at myhosts, type:

swverify -d mysoft.myfileset @ myhosts

(The @ sign and the myhost target designation are optional because the software being verified located in the default depot on the local host.)

To verify the C and Pascal products that are installed on the local host:

swverify C Pascal

To verify the HP Omniback product that is installed on the local host and display detailed messages from the process (-v) on stdout:

swverify -v Omniback

To verify the 2.0 version of Omniback that is installed on the local host at /opt/Omniback:

swverify Omniback,r=2.0 @ /opt/Omniback

Verify a particular version of HP Omniback:

swverify Omniback,1=/opt/Omniback_v2.0

Verify the entire contents of a local depot:

swverify -d \*@/var/spool/sw