similar to: yum configuration files lost while/after updating ?

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.

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

I just had a customer's bind server lose all of it's local DNS records. Yum updated the bind packages this morning at ~6am, and replaced the original /etc/named.conf file, saving the old as named.conf.rpmsave. This seems like the opposite of what it should have done (i.e. save the new file as named.conf.rpmnew). There does not appear to be any difference between the originally shipped

Hi folks, Just updating clamav 'bundle' from old 'clamav-server' (i think the just previous) and i noticed that the 'clamav' user/group for this pkg is not created by default by the rpm pkg. At the same time, the /var/log/clamav is not updated/created with clamav.clamav ownership, Don't know if it is my actual config (previous one untouched anyway), but this is what

> Am 15.06.2018 um 01:04 schrieb Gordon Messmer <gordon.messmer at gmail.com>: > > On 06/14/2018 09:30 AM, me at tdiehl.org wrote: >> On Thu, 14 Jun 2018, Richard Grainger wrote: >> >>> I looked at the spec file in the source RPM for the krb5-libs package >>> and it it has the correct %config(noreplace) directive next to that >>> file in the

You get so used to yum upgrades going so smoothly but I learned the hard way to always make a thorough inspection after a yum update. I let yum go ahead and upgrade from 3.5 to 3.6. Afterwards I made some basic queries to httpd, postfix and bind named (probably a cached query). I even checked the /var/named/ directory and saw all my hosts files. So looked like another smooth ride, well until

On Tue, 2004-11-30 at 12:17 +0700, Matthew Hodgett wrote: > > As for the 169.254 issue I tried to search the archives but got nothing. > I then tried to search on generic words, nothing. I then tried some > really common words like ''help'', ''initiated'', ''masq'' - nothing. I think > the index might be corrupt because I get no

i think that previous versions did this as well, but for sure the newest ypserv in 5.3 replaces /var/yp/Makefile with a new copy. needless to say if you've made any changes to that file, you will not be happy. we had a couple hours of phone calls after passwords stopped working. the original file is save as Makefile.rpmsave, so recovery of the file is straightforward. the issue has

Hi list, here is what happened: today I noticed some resolution's problems on my network. I did a "service named status" and here was the output: # /etc/init.d/named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. In the

Hello, all. My systems are centos 4.x or 5.x(i386 and x86_64) and various services(apache, mysql, java, sendmail... etc..). and I would like to set auto update using yum. But some staffs didn't agree my auto update plan, because some services can be effected by auto update. There were no side effects just yum updating until now, and it seems impossible for me to check

On Fri, May 6, 2016 04:36, John Hodrien wrote: > On Fri, 6 May 2016, Gary Stainburn wrote: > >> What I didn't expect, and what really threw me was that this has >> been implemented via a simply 'yum update' of an existing system, >> not at a major release level. > > > Something like RHEL is stuck in a trap here. Either they never > change a default

Hi guys: I saw the pelthora of threads where people had trouble moving to 4.4. So I'm chicken now and I was trying to wait for the dust to settle, I suppose it has and its been long enough I'm nervous about not upgrading. I need to do a a production server that is located in a data center far away so even more than normal I want a smooth upgrade. Can someone tell the what the

The old virt-v2v code ignored boot kernels with names like "/boot/vmlinuz-*.rpmsave". The transscribed code did not because the Str module requires ‘|’ to be escaped as ‘\|’. This changes the code to use PCRE and fixes it. --- v2v/linux_bootloaders.ml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index

--On Friday, June 05, 2020 1:39 PM -0700 John Pierce <jhn.pierce at gmail.com> wrote: > don't most packages create a .rpmnew file if you've modified the previous > package file ? That file is created AFTER you've made edits, and reflects only the state of the file in the latest package. So it's not clear what changed from the original package that needs to be

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:

I am about to set up a computer with Centos 6 that I'll probably never see again. I don't want to give out the root password, but I would like to have it automatically and transparently update itself. What is the best way to do this? I have been looking at webpages about yum-cron and yum-updatesd but nothing directly addresses Centos 6 and it appears that at least one of those two

We'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

Everyone, I upgraded Solaris 2.6 box running Samba 2.0.4 to a Solaris 7 with a new version of Samba 2.0.6 I used all my old smb.conf files on this new server and now I can see the server but when you try to connec to it is give the message " Not accessable " Unexpected network error occured" Thanks for any help getting this figured out it must be some thing small I am missing

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On 28/06/15 02:17, Joseph L. Casale wrote: > Your script within the rpm should have the logic. Clearly if > you know how to update it, you know how to identify if it > needs updating. Thanks Joseph. I am aware of this option, but it would be only a last resort, because checking the format of the config file is error-prone. I would prefer RPM to tell me the old and new version numbers,