swverify.1m (2011 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swverify(1M) swverify(1M)

NAME

swverify - verify software products

SYNOPSIS

swverify [-d|-r][-F

][-v][-C session_ﬁle][-f software_ﬁle][

-J jobid] [-Q date ]

[

-S session_ﬁle][

-t target_ﬁle][-x option=value ][-X option_ﬁle ]

[software_selections][

@ target_selections]

Remarks

• This command supports operations on remote systems. See Remote Operation below.

• For an overview of all SD commands, see the sd(5) man page by typing

man5sdon the com-

mand line.

DESCRIPTION

The

swverify command veriﬁes the software_selections at one or more target_selections (for example,

root ﬁlesystems). When verifying installed software,

swverify checks software states, dependency

relationships, ﬁle existence and integrity, in addition to executing vendor-supplied veriﬁcation scripts.

The

swverify command also veriﬁes software_selections at one or more target depots. For target

depots,

swverify performs all of the checks listed above, but does not execute veriﬁcation scripts.

NOTE: swverify does not support operations on a tape depot.

The

swverify command also supports these features:

• Veriﬁes whether installed or conﬁgured software is compatible with the hosts on which that

software is installed.

• Veriﬁes that all dependencies (prerequisites, corequisites, exrequisites) are being met (for

installed software) or can be met (for available software).

• Executes vendor-speciﬁc

verify scripts that check if the software products is correctly

conﬁgured.

• Executes vendor-speciﬁc

fix scripts that correct and report speciﬁc problems.

• Reports missing ﬁles, check all ﬁle attributes (ignoring volatile ﬁles). These attributes include

permissions, ﬁle types, size, checksum, mtime, link source and major/minor attributes.

Remote Operation

You can enable SD to manage software on remote systems. To let the root user from a central SD con-

troller (also called the central management server or manager node) perform operations on a remote tar-

get (also called the host or agent ):

1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit

root access from the controller system. To do this, run the following command on each remote sys-

tem:

/usr/lib/sw/mx/setaccess controller

NOTES:

• controller is the name of the central management server.

• If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed

on remote system before running

setaccess.

• If remote system is older than 11.00 or for some other reason does not have

setaccess in place,

copy setaccess script from an 11.11 or higher system to the remote system.

swinstall, swcopy, and swremove have enhanced GUI interfaces for remote operations. Enable

the enhanced GUIs by creating the .sdkey ﬁle on the controller. Use this command:

touch /var/adm/sw/.sdkey

See sd(5), swinstall (1M), swcopy(1M), swjob(1M), swlist (1M), or swremove (1M) for more information

on interactive operations.

NOTE: You can also set up remote access by using

swacl directly on the remote machines to grant root

or non-root access to users from the controller system.

HP-UX 11i Version 3: March 2011 − 1 − Hewlett-Packard Company 1

Summary of content (12 pages)

PAGE 1
swverify(1M) swverify(1M) NAME swverify - verify software products SYNOPSIS swverify [-d|-r] [-F] [-v] [-C session_file ] [-f software_file ] [-J jobid] [-Q date ] [-S session_file ] [-t target_file ] [-x option=value ] [-X option_file ] [software_selections] [@ target_selections] Remarks • This command supports operations on remote systems. See Remote Operation below. • For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the command line.
PAGE 2
swverify(1M) swverify(1M) Options swverify supports the following options: -d Operate on a depot rather than installed software. -F Runs vendor-specific fix scripts to correct and report problems on installed software. The fix script can create missing directories, correct file modifications (mode, owner, group, major, and minor), and recreate symbolic links. -r Operates on an alternate root directory, which must be specified in the @ target_selections option.
PAGE 3
swverify(1M) swverify(1M) [,r revision ][,a arch ][,v vendor ] [,c category ][,q=qualifier][,l=location ] [,fr revision ][,fa arch ] • location applies only to installed software and refers to software installed to a location other than the default product directory. • fr and fa apply only to filesets. • r, a, v, c, and l apply only to bundles and products. They are applied to the leftmost bundle or product in a software specification.
PAGE 4
swverify(1M) swverify(1M) The optional command_name prefix denotes one of the SD commands. Using the prefix limits the change in the default value to that command. If you leave the prefix off, the change applies to all commands. You can also override default values from the command line with the -x or -X options: command -x option =value command -X option_file The following section lists all of the keywords supported by the swverify command. If a default value exists, it is listed after the =.
PAGE 5
swverify(1M) swverify(1M) autoremove_job=false Controls automatic job removal of completed jobs. If the job is automatically removed, job information (job status or target log files) cannot be queried with swjob. autoselect_dependencies=true Controls the automatic selection of prerequisite, corequisite, and exrequisite software that is not explicitly selected by the user. When set to true, the requisite software is automatically selected for configuration.
PAGE 6
swverify(1M) swverify(1M) [host ][:][path ] This option has no effect on which sources the target uses. distribution_target_directory=/var/spool/sw Defines the default distribution directory of the target depot. The target_selection operand overrides this default. enforce_dependencies=true Requires that all dependencies specified by the software_selections be resolved either in the specified source, or at the target_selections themselves.
PAGE 7
swverify(1M) swverify(1M) If true, promotes the corequisite of a prerequisite to prerequisite. If false, corequisites are not used in determining load order. logdetail=false[true] Controls the amount of detail written to the logfile. When set to true, this option adds detailed task information (such as options specified, progress statements, and additional summary information) to the logfile. This information is in addition to log information controlled by the loglevel option.
PAGE 8
swverify(1M) swverify(1M) the other commands use to contact the daemon. If the connection fails for one protocol sequence, the next is attempted. SD supports both the tcp (ncacn_ip_tcp:[2121]) and udp (ncadg_ip_udp:[2121]) protocol sequence on most platforms. See the sd(5) man page by typing man 5 sd for more information. rpc_timeout=5 Relative length of the communications timeout. This is a value in the range from 0 to 9 and is interpreted by the DCE RPC.
PAGE 9
swverify(1M) swverify(1M) You can also save session information to a specific file by executing swverify with the -C session_file option. A session file uses the same syntax as the defaults files. You can specify an absolute path for the session file. If you do not specify a directory, the default location for a session file is $HOME/.sw/sessions/. To re-execute a session file, specify the session file as the argument for the -S session_file option of swverify.
PAGE 10
swverify(1M) swverify(1M) 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 /.
PAGE 11
swverify(1M) swverify(1M) 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 / or an alternate root directory). When verifying available the root directory (for example, software (within a depot), the swagent logs messages to the file swagent.log beneath the depot directory (for example, /var/spool/sw).
PAGE 12
swverify(1M) swverify(1M) Software Distributor Administration Guide , available at http://www.hp.com/go/sd-docs. SD customer web site at http://www.hp.com/go/sd-docs.