similar to: Bind update overwrites named.conf

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

Hello centOS users, Today i've installed a fresh centos 3.1, and modified the [update] section of my/etc/yum.conf, to point on my own update repository. My update repository (3.1) contains exactly the same content that the official one. Update was successful but now /etc/yum.conf is missing :( Here it is what i've noticed during the update process: # cat /etc/redhat-release CentOS

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

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.

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

> 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

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

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

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

Good morning: We're about to start moving our public DNS to in-house managed servers. My first thought was "Linux + BIND" and we're done. Someone in another business unit's IT dept. has suggested tinydns be used. >From what I could find, it looks like this software hasn't really had any community drive behind it in a while. The latest RPMs on rpmforge are for red hat

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,

CentOS Errata and Security Advisory 2008:0533 https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/bind-9.2.4-28.0.1.el4.s390.rpm updates/s390/RPMS/bind-chroot-9.2.4-28.0.1.el4.s390.rpm updates/s390/RPMS/bind-devel-9.2.4-28.0.1.el4.s390.rpm

Hi Nithya, I applied the workarround for this bug and now df shows the right size: [root at stor1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 26T 1,1T 25T 4% /mnt/glusterfs/vol0 /dev/sdc1 50T 16T 34T 33% /mnt/glusterfs/vol1 stor1data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor1data:/volumedisk1

Hi Jose, On 28 February 2018 at 18:28, Jose V. Carri?n <jocarbur at gmail.com> wrote: > Hi Nithya, > > I applied the workarround for this bug and now df shows the right size: > > That is good to hear. > [root at stor1 ~]# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sdb1 26T 1,1T 25T 4% /mnt/glusterfs/vol0 > /dev/sdc1

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 :

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 :) Thanks!!

Hi Jose, On 28 February 2018 at 22:31, Jose V. Carri?n <jocarbur at gmail.com> wrote: > Hi Nithya, > > My initial setup was composed of 2 similar nodes: stor1data and stor2data. > A month ago I expanded both volumes with a new node: stor3data (2 bricks > per volume). > Of course, then to add the new peer with the bricks I did the 'balance > force' operation.

Hi Nithya, My initial setup was composed of 2 similar nodes: stor1data and stor2data. A month ago I expanded both volumes with a new node: stor3data (2 bricks per volume). Of course, then to add the new peer with the bricks I did the 'balance force' operation. This task finished successfully (you can see info below) and number of files on the 3 nodes were very similar . For volumedisk1 I

CentOS Errata and Security Advisory 2008:0533 https://rhn.redhat.com/errata/RHSA-2008-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/bind-9.2.4-28.0.1.el4.ia64.rpm updates/ia64/RPMS/bind-chroot-9.2.4-28.0.1.el4.ia64.rpm updates/ia64/RPMS/bind-devel-9.2.4-28.0.1.el4.ia64.rpm