search for: rpmsave

Hi list! After yum upgrade of my CentOS 4.0 to 4.2 x86_64 box I now have countless .rpmsave files, about 90% of them I never touched or are config/start scripts. Does anyone have a neat script that will find all the rpmsave stuff in /etc and then prompts per file whether it can replace the original or not? Somehow doing this all by hand doesn't seem a very attractive idea :) Than...

Hello I just upgraded Centos, and now doing some post upgarde task to make sure every thing is fine. First of all, it seems upgrade add rpmsave extension to configuration files, which we should copy them back example is /etc/httpd/conf/httpd.conf.rpmsave also what is Pegasus ? there is a lot of rpmsaved in /var/lib/pegasus example : /var/lib/Pegasus/prev_repository_2007-08-30-1188481293.980554182.rpmsave Thanks

RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.0alpha2/ SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.0alpha2.tar.gz This release is made off jenkins-release-19 -- Gluster Build System _______________________________________________ Gluster-devel mailing list Gluster-devel at nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel

...fs/vol1 [root at stor1 ~]# grep -n "share" /var/lib/glusterd/vols/volumedisk1/* /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 0 /var/lib/gluste...

...r1 ~]# grep -n "share" /var/lib/glusterd/vols/volumedisk1/* > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor1data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor1data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option > shared-brick-count 1 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor2data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor2data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option > shar...

After you do your update, done forget to do updatedb, makewhatis, ... The locate for rpmnew has a couple items of interest and the locate for rpmsave returns one that occupies 24MB of your precious disks - /var/lib/Pegasus/prev-repository*. It compresses nicely to appx. 1MB, cpio bzipped --best. Change in your rndc key too, for DNS.

...quot;share" /var/lib/glusterd/vols/volumedisk1/* >> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data. >> mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 >> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data. >> mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 >> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data. >> mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 >> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data. >> mnt-glusterfs-vol1-brick1.vol.rpmsave:3: optio...

...r1 ~]# grep -n "share" /var/lib/glusterd/vols/volumedisk1/* > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor1data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor1data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option > shared-brick-count 1 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor2data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 0 > /var/lib/glusterd/vols/volumedisk1/volumedisk1. > stor2data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option > shar...

...r-ahead: on [root at stor1 ~]# grep -n "share" /var/lib/glusterd/vols/volumedisk1/* /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 1 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol:3: option shared-brick-count 0 /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 0 /var/lib/glusterd/vols/v...

...; /var/lib/glusterd/vols/volumedisk1/* >>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol:3: >>> option shared-brick-count 1 >>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt >>> -glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 >>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol:3: >>> option shared-brick-count 1 >>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt >>> -glusterfs-vol1-brick1.vol.rpms...

...erd/vols/volumedisk1/* >>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol:3: >>>> option shared-brick-count 1 >>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt >>>> -glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 >>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol:3: >>>> option shared-brick-count 1 >>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt >>>> -glusterfs-vol1...

Horde RPMs got updated last night. However, the way configuration files were handled wasn't probably the best. It moved my configuration files to rpmsave, instead of leaving them as-is and putting new configs into rpmnew (like most packages do). warning: /usr/share/horde/config/conf.php saved as /usr/share/horde/config/conf.php.rpmsave warning: /usr/share/horde/turba/config/sources.php saved as /usr/share/horde/turba/config/sources.php.rpmsav...

...isk1/* >>>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt-glusterfs-vol1-brick1.vol:3: >>>>> option shared-brick-count 1 >>>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor1data.mnt >>>>> -glusterfs-vol1-brick1.vol.rpmsave:3: option shared-brick-count 1 >>>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt-glusterfs-vol1-brick1.vol:3: >>>>> option shared-brick-count 1 >>>>> /var/lib/glusterd/vols/volumedisk1/volumedisk1.stor2data.mnt >>>>>...

...nything when I > search the archives. The htdig packager for Fedora seems to think that it is more important that people have the lastest config files than that they have the right config files. When I installed an update via ''up2date'' my htdig.conf file was renamed htdig.conf.rpmsave and a new file was installed in its place. I''ve swapped the files around and have rebuilt the index. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists...

...'ve got several CentOS 3.x systems running DNS that we keep updated automatically via YUM. Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave. Which of course broke DNS for those servers. All servers got updated, but only two of them did the rewrite. Any ideas as to why it might have happed, or how to make sure it doesn't happen again? Hopefully nothing so simplistic as "exclude bind from auto updates" though if that&...

Hello, I encountered a problem when upgrading from 3.3 to 3.4 on i386. The machine is a production name server running bind. Looks like the new rpm moved my named.conf to .rpmsave and chkconfig'ed bind to off. That's really bad. A more gentle behavior would have been to save the new named.conf to .rpmnew and not mess with initscripts. Anyone else notice that? Francois Caen

...issing :( Here it is what i've noticed during the update process: # cat /etc/redhat-release CentOS release 3.1 (final) #yum update [...] warning: /etc/yum.conf created as /etc/yum.conf.rpmnew yum 100 % done 96/191 [...] warning: /etc/centos-base-yum.conf saved as /etc/centos-base-yum.conf.rpmsave Completing update for yum - 110/191 [...] Transaction(s) Complete # cat /etc/redhat-release CentOS release 3.3 (final) => files /etc/yum.conf* /etc/yum.conf -> /etc/centos-base-yum.conf ( Broken link! read the rest) /etc/yum.conf.rpmnew /etc/yum.conf-SAVE => files /etc/centos* /etc/c...

...edir /etc/krb5.conf.d' /etc/krb5.conf ; then > sed -i '1i # Other applications require this directory to perform krb5 configuration.\nincludedir /etc/krb5.conf.d/\n' /etc/krb5.conf > fi > > > Looks like that's the culprit. Good to know, but writing a rpmnew or rpmsave file would be nice to check against the life used file. The samba people are aware of that problem regarding the include line and are working on a patch ? the support at SerNet told me. Regards . G?tz

...y and saw all my hosts files. So looked like another smooth ride, well until today I noticed my domains dropped off the net. Too bad I did not check the bind gui or look at /etc/named.conf after the yum update since it was replaced with a generic version from 3.6. Luckily I copied /etc/named.conf-rpmsave to named.conf and I am back in business, well at least in 24 to 72 hours for the rest of the world :( __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

...[2/8] Installing: clamd ######################### [3/8] Cleanup : clamav ######################### [4/8] Removing : clamav-lib ######################### [5/8] warning: /etc/sysconfig/freshclam saved as /etc/sysconfig/freshclam.rpmsave warning: /etc/cron.d/clamav-update saved as /etc/cron.d/clamav-update.rpmsave Removing : clamav-update ######################### [6/8] warning: /var/lib/clamav/main.cvd saved as /var/lib/clamav/main.cvd.rpmsave warning: /var/lib/clamav/daily.cvd saved as /var/lib/clamav/daily.cvd....