fverify(8) System Manager's Manual fverify(8)
fverify - verify software subsets
The command reads subset inventory records from standard input and verifies that the attributes for the files on the system match the
attributes listed in the corresponding records. Invoking with no arguments causes it to report errors to the standard output and prompt
the user for confirmation before making corrections.
Missing files and inconsistencies in file size, checksum, user id, group id, mode, and file type are reported. If inconsistencies in user
id, group id or mode are detected the user is asked if they are to be corrected. If a missing file is a directory, it will be created. All
errors and informational messages are logged to the file
The utility uses when installing subsets to guarantee correct installation.
Specifying both options will cause the -y option to be ignored.
-n Error reporting only. When specified, reports errors and does not perform any fixes.
-y Fixes only. When specified, fixes modes, UIDs and GIDs on any files which have incorrect values for these attributes. No user input
Problems with file size, file type, and file checksum cannot be corrected.
Because the subset inventories give file names as relative paths, run in the root directory to which the software is installed.
Many of the files on the system cannot be read or modified without appropriate privilege. Attempting to run without appropriate privilege
may result in an excess of access errors being reported.
To use to report verification problems with the BASE subset on ULTRIX, Version 4.0 (VAX), use the following command:
% cd /
% /etc/stl/fverify -n </usr/etc/subsets/ULTBASE400.inv
To correct all problems with the same subset without being presented any prompts or diagnostic output, type:
% cd /
% /etc/stl/fverify -y < /usr/etc/subsets/ULTBASE400.inv
To interactively repair verification problems with the COMM subset on ULTRIX, Version 4.0 (RISC), use the fverify command with no argu-
% cd /
% /etc/stl/fverify < /usr/etc/subsets/UDTCOMM400.inv
fverify: out of memory
Not enough memory is available from the system.
pathname: cannot stat (error-message)
The file pathname is listed in the inventory but is not on the system. The error-message explains why.
pathname: file type `x' should be `y'
The file is listed in the inventory as being of type `y', but the copy of the file on the disk is type `x'. The file type codes are:
b block device files
c character device files
d directory files
f regular files
l hard links
p fifos (named pipes)
s symbolic links
pathname: checksum n should be m
There is a checksum error on pathname. The values n and m are the actual and expected values.
pathname: size n should be m
The size of file pathname is not as expected. The numbers n and m are the actual and expected values.
pathname: gid n should be m
The group id for pathname is not as expected. The group ids n and m are the actual and expected values.
pathname: uid n should be m
The user id for pathname is not as expected. The user ids n and m are the actual and expected values.
pathname: permissions string1 should be string2
The permissions for pathname are not as expected. String1 and string2 are the actual and expected permissions. The format of string1 and
string2 is the same as that used by the command.
Creating directory pathname
The directory pathname is listed in the input inventory but does not exist on the system. The command will attempt to create the direc-
cannot correct pathname (error-message)
A problem reported with pathname could not be corrected. The error-message explains why.
A problem with pathname was successfully corrected.
Cannot create dir pathname (error-message)
The program could not create a directory it was attempting to create. The accompanying error-message explains why.
n verification errors encountered.
m corrections performed.
Before exiting, the program prints these statistics describing what had been done.
The exit status from is the total number of errors detected minus the total number of successful fixes.
Subset inventory files
ls(1), stl_inv(5), setld(8)
Guide to Preparing Software for Distribution on ULTRIX Systems