Re: binaries grow overnight, but rpm -V does not catch the changes

• To: fedora-list@xxxxxxxxxx
• Subject: Re: binaries grow overnight, but rpm -V does not catch the changes
• From: "William Hooper" <whooperhsd3@xxxxxxxxxxxxx>
• Date: Wed, 13 Jul 2005 16:01:35 -0400 (EDT)
• In-reply-to: <[email protected]>
• List-archive: <https://www.redhat.com/archives/fedora-list>
• List-help: <mailto:[email protected]?subject=help>
• List-id: For users of Fedora Core releases <fedora-list.redhat.com>
• List-post: <mailto:[email protected]>
• List-subscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
• List-unsubscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
• References: <[email protected]>
• Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
• User-agent: SquirrelMail/1.5.1 [CVS]

Marcin Struzak wrote:
[snip]
> I am suspecting prelink is the culprit (found entries for all of the
> above in /var/log/prelink.log), but that still does not explain why rpm
> -V is absolutely silent about the changes?

RPM is prelink aware.  IIRC it un-prelinks the binary and checks the
MD5SUM against the RPM database, but I could be remembering incorrectly.

-- 
William Hooper

• References:
  • binaries grow overnight, but rpm -V does not catch the changes
    • From: Marcin Struzak

• Prev by Date: After FC3 to FC4 upgrade, KDE/K3b version mismatch
• Next by Date: Re: binaries grow overnight, but rpm -V does not catch the changes
• Previous by thread: binaries grow overnight, but rpm -V does not catch the changes
• Next by thread: Re: binaries grow overnight, but rpm -V does not catch the changes
• Index(es):
  • Date
  • Thread