Software Distributor Administrator Guide (September 2010)

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.
6. 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
2.3.3 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) ” (page 132)
-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” (page 52).
-F
Run a fix script. See “Fix Scripts” (page 286).
-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” (page 49).
-Q date
Schedules a job for the given date when remote
operations are enabled. See “Scheduling Jobs from the
2.3 Verifying Your Installation (swverify) 79