Next:
rpm -V
Up:
RPM and Computer Users
Previous:
A Few Handy Queries
 
Contents
 
Index
Using RPM to Verify Installed Packages
rpm -V
(
or
--verify, or -y)
options
Package Selection Options
Page
pkg1 ... pkgN
Verify named package(s)
-p
<file>
Verify against package file
<file>
-f
<file>
Verify package owning
<file>
-a
Verify all installed packages
-g
<group>
Verify packages belonging to group
<group>
Verify--specific Options
Page
--noscripts
Do not execute verification script
--nodeps
Do not verify dependencies
--nofiles
Do not verify file attributes
General Options
Page
-v
Display additional information
-vv
Display debugging information
--root
<path>
Set alternate root to
<path>
--rcfile
<rcfile>
Set alternate rpmrc file to
<rcfile>
--dbpath
<path>
Use
<path>
to find the RPM database
Subsections
rpm -V
-- What Does it Do?
What Does it Verify?
File Ownership
File Group
File Mode
MD5 Checksum
File Size
Major Number
Minor Number
Symbolic Link
Modification Time
When Verification Fails -
rpm -V
Output
Other Verification Failure Messages
Selecting What to Verify, and How
The Package Label -- Verify an Installed Package Against the RPM Database
-a
-- Verify All Installed Packages Against the RPM Database
-f
<file>
-- Verify the Package Owning
<file>
Against the RPM Database
-p
<file>
-- Verify Against a Specific Package File
-g
<group>
-- Verify Packages Belonging To
<group>
--nodeps
: Do Not Check Dependencies Before Erasing Package
--noscripts
: Do Not Execute Verification Script
--nofiles
: Do Not Verify File Attributes
-v
-- Display Additional Information
-vv
-- Display Debugging Information
--dbpath
<path>
: Use
<path>
To Find RPM Database
--root
<path>
: Set Alternate Root to
<path>
--rcfile
<rcfile>
: Set Alternate
rpmrc
file to
<rcfile>
We've Lied to You...
RPM Controls What Gets Verified
The Package Builder Can Also Control What Gets Verified
Next:
rpm -V
Up:
RPM and Computer Users
Previous:
A Few Handy Queries
 
Contents
 
Index
converted to HTML by
Tim Riker