When verifying a package, RPM produces output only
if there is a verification failure. When a file fails verification, the
format of the output is a bit cryptic, but it packs all the information
you need into one line per file. Here is the format:
S is the file size.
M is the file's mode.
5 is the MD5 checksum of the
D is the file's major and minor
L is the file's symbolic link
U is owner of the file.
G is the file's group.
T is the modification time of the
c appears only if the file is a
This is handy for quickly identifying config files, as they are
very likely to change, and therefore, very
unlikely to verify successfully.
is the file that failed verification. The complete path is listed
to make it easy to find.
It's unlikely that every
file attribute will fail
to verify, so each of the eight attribute flags will only appear if
there is a problem. Otherwise, a "
will be printed in that flag's place. Let's look at an example or two:
In this case, the mode, MD5 checksum, and modification time for the
specified file have failed to verify. The file is not a config file
(Note the absence of a "
" between the
attribute list and the filename).
Here, the size, checksum, and modification time of the system password
file have all changed. The "
indicates that this is a config file.
This last example illustrates what RPM does when a file, that should be
there, is missing entirely.
When rpm -V
finds other problems, the output is a
bit easier to understand:
rpm -V blather
Unsatisfied dependencies for blather-7.9-1: bother >= 3.1
It's pretty easy to see that the
requires at least version 3.1 of the
The output from a package's verification script is a bit harder to
categorize, as the script's contents, as well as its messages, are
entirely up to the package builder.
Если вам понравилась статья, поделитесь ею с друзьями: