| Maximum RPM: Taking the Red Hat Package Manager to the Limit | ||
|---|---|---|
| Prev | Chapter 6. Using RPM to Verify Installed Packages | Next |
When verifying a package, RPM produces output only Here is the format:
SM5DLUGT c <file>
|
Where:
S is the file size.
M is the file's mode.
5 is the MD5 checksum of the file.
D is the file's major and minor numbers.
L is the file's symbolic link contents.
U is owner of the file.
G is the file's group.
T is the modification time of the file.
c appears only if the file is a configuration file. This is handy for quickly identifying config files, as they are very likely to change, and therefore, very unlikely to verify successfully.
<file> is the file that failed verification. The complete path is listed to make it easy to find.
It's unlikely that every." will be printed in that flag's place. Let's look at an example or two:
.M5....T /usr/X11R6/lib/X11/fonts/misc/fonts.dir
|
c" between the attribute list and the filename).
S.5....T c /etc/passwd
|
Here, the size, checksum, and modification time of the system password file have all changed. The "c" indicates that this is a config file.
missing /var/spool/at/spool
|
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 blather package requires at least version 3.1 of the bother package.
| Главная |