man rpm
will (most likely) explain why those files are there; that's a design
feature of rpm, it's trying to protect your configuration files.
DP
--
David-Paul Niner, RHCE
Jacksonville, Florida, USA
dpniner@xxxxxxxxxxx :: http://www.dpniner.net
Public Key: http://www.dpniner.net/files/Gnupg/DpninerDotNetPubKey.text
Free/Busy Information: https://horde.dpniner.net/kronolith/fb.php?u=dpniner
Quoting Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>:
I'm a flailing at cluefulness here. Maybe someone can set me straight.
I run "yum" nightly (as as service), but I see a lot of "*.rpmnew" files
being left around.
What's most bizarre is that the original RPM files haven't been changed,
and often the two files have the same size, contents (and hence MD5
signature), permissions, ownership, etc. Even the same file modification
date in most cases.
So why do they get left behind?
# cd /etc/security
# ls -ltr chroot*
-rw-r--r-- 1 root root 82 Aug 1 05:18 chroot.conf.rpmnew
-rw-r--r-- 1 root root 82 Aug 1 05:18 chroot.conf
# diff -c chroot.conf.rpmnew chroot.conf
# mv chroot.conf.rpmnew chroot.conf
#
Thanks,
-Philip
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
