NAME

pkg_validate — list mismatched and missing files of installed packages

SYNOPSIS

pkg_validate [-cDmoqv] [-b batchsize] [-j jobs] [-a]

pkg_validate [-CcdDgimOoqrvx] [-b batchsize] [-j jobs] pkg-name ...

pkg_validate -h

DESCRIPTION

The pkg_validate script provides the same functionality as running ‘pkg check -s’. It can be run by an unprivileged user and its use of multiple processes can make it significantly faster when files are cached in memory or read from a fast solid state drive.

Arguments

The following arguments are accepted:

batchsize: The number of files to verify in a single chunk. This controls the granularity of parallel job execution, the default is 1024.
jobs: The number of parallel processes to perform file validation. The default is number of detected cores plus one.
pkg-name: Packages are package names or shell glob patterns matching these. Whatever works with pkg-info(8) is an acceptable package.

Options

The following options are available:

-a, --all: Check all packages. This is the default action in case no pkg-name has been specified.
-b batchsize, --batch batchsize: Set the number of files to verify in a single chunk.
-C, --case-sensitive: See pkg-info(8).
-c, --clean: Create clean output without status messages.
-d, --dependencies: Also operate on the dependencies of the provided pkg-name.
-D, --developer: Produce additional output relevant to ports(7) and pkg(8) developers.
Currently it provides information about dead symlinks.
-g, --glob: See pkg-info(8).
-h, --help: Displays the available options.
-i, --case-insensitive: See pkg-info(8).
-j jobs, --jobs jobs: Specify the amount of parallel jobs the script will attempt run.
-m, --no-filter: In this mode files that cannot be checked due to user permissions are listed along with checksum mismatches and missing files.
-O, --by-origin: See pkg-info(8).
-o, --origin: Instead of the package name the package origin is printed.
-q, --quiet: Only print the names of affected packages. Do not print any details. This option is meant for machine readability.
This option cannot be combined with verbose output.
-r, --required-by: Also check packages that depend on the provided packages. This is a good idea when checking for the effects of a library update.
-v, --verbose: List the selected packages before checking them.
-x, --regex: See pkg-info(8).

EXAMPLES

To check all your packages run:

pkg_validate

List files that cannot be checked due to missing user privileges:

pkg_validate -m

Produce output suitable as input to other pkg(8) tools:

pkg_validate -q

For operating poudriere(8) or portmaster(8) it can be more useful to output package origins instead of names:

pkg_validate -o

Flags can be combined:

pkg_validate -qo

ENVIRONMENT

The following environment variables affect the operation of pkg_validate.

DEVELOPER: Activates additional diagnostics, see the --developer option.
Set to ‘yes’ or 1 to enable. This is equivalent to the DEVELOPER macro of <bsd.port.mk>.

EXIT STATUS

1: The script has terminated because it received SIGHUP, SIGINT or SIGTERM.
2: An unknown parameter has been supplied.
3: The incompatible parameters -v and -q have been supplied.
4: The parameter -j has been supplied without an acceptable number.

HISTORY

A pkg_validate script first appeared in the bsdadminscripts-3.0 collection. It was deemed obsolete with the inception of bsda2 and rewritten for bsda2-0.3.0.

AUTHORS

Dominic Fandrey <freebsd@k4m1.org>