ACC SHELL

Path : /usr/share/doc/packages/rpm/RPM-Tips/
File Upload :
Current File : //usr/share/doc/packages/rpm/RPM-Tips/RPM-Tips-6.html

<HTML>
<HEAD>
<TITLE>Verifying</TITLE>
</HEAD>
<BODY>
<H1>6. <A NAME="s6"></A>Verifying</H1>
<P>
<A HREF="RPM-Tips.html#toc6">Contents of this section</A></P>

<P></P>
<P>Verifying packages can be a very enlightenting experience.  To verify,
use <CODE>-V</CODE> along with one of the ``package selection options'' listed
in the Querying section.  For instance, if you are having trouble
with the Emacs package, and can not figure out the problem, one of
the first things you might do is verify the package:</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
rpm -Vf /usr/bin/emacs
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>If any anomolies are reported, you should rerun the verification in
verbose mode with <CODE>-v</CODE>:</P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
rpm -Vvf /usr/bin/emacs
</PRE>
</CODE></BLOCKQUOTE>
</P>
<P>This will list the exact discrepencies the rpm finds, including
changed permission, owners, groups, file sizes, etc.  Sometimes,
these changes are normal and are not cause for alarm.  For instance,
if you modify a configuration file, the verification will report
it, but it is not necessarily a problem.  The /dev/tty* files are
another example.  These files change ownership as users log in and
out, so changes in ownership may not be cause for alarm.</P>
<P></P>
<HR>
<P>
<A HREF="RPM-Tips-7.html">Next</A> Chapter,
<A HREF="RPM-Tips-5.html">Previous</A> Chapter
<P>
Table of contents of <A HREF="RPM-Tips.html#toc6">this chapter</A>,
 General <A HREF="RPM-Tips.html#toc">table of contents</A></P>
<P>
<A HREF="RPM-Tips.html">Top</A> of the document,
 <A HREF="#0"> Beginning of this Chapter</A></P>
</BODY>
</HTML>

ACC SHELL 2018