Philip Prindeville wrote:
> 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
Bingo:
# ls -l /etc/security/chroot.conf*
-rw-r--r-- 1 root root 82 Aug 1 05:18 /etc/security/chroot.conf
-rw-r--r-- 1 root root 82 Aug 1 05:18 /etc/security/chroot.conf.rpmnew
# perl -e 'print join(", ", stat("/etc/security/chroot.conf")),
"\n"'
64768, 721510, 33188, 1, 0, 0, 0, 82, 1154431139, 1154431139, 1156023232, 4096, 8
# perl -e 'print join(", ",
stat("/etc/security/chroot.conf.rpmnew")), "\n"'
64768, 719917, 33188, 1, 0, 0, 0, 82, 1154431128, 1154431128, 1156023323, 4096, 8
# perl -e 'print scalar
localtime((stat("/etc/security/chroot.conf.rpmnew"))[9]), "\n"'
Tue Aug 1 05:18:48 2006
# perl -e 'print scalar localtime((stat("/etc/security/chroot.conf"))[9]),
"\n"'
Tue Aug 1 05:18:59 2006
#
And there you have it.
Why are the packages being generated with a few seconds jitter?
This seems to be generating a lot of .rpmnew files gratuitously.
-Philip