similar to: yum/RPM behaviour: does yum/RPM overwrite a file modified by a user during an update ?

Hi, We have a cluster with CentOS 5.5 installed with oscar. The firm which has pre-installed the cluster has done strange things...and now I get problems: - if I understand correctly what was done, several infiniband CentOS packages were installed (compat-dapl, compat-dapl-devel, compat-dapl-utils, libibcm, libibverb, librdmacm, mpi-selector). - Then the tar package from OFED was installed.

I want to get the original version of /etc/clamd.d/amavis.conf from the amavisd-new rpm to get the defaults to submit a bug report. I could not figure out how to do this, so I did a reinstall, but it did not replace this file (whatprovides says it comes from this rpm). Is there a way to extract just the one file, and better yet, place it elsewhere than its regular destination? thanks

hi all, I've got a data frame, this data frame have 76 columns and 22600 rows. The data inside can be redundant because the data can be captured simultaneously and overlap each other. My aim is to supress these overlaps I've test some solutions to do that but they all give a big cpu load and eat all of the memory then swap a lot, then killall R because it don't end. actually

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

Hi, we have a cluster. The master has CentOS 5.5 on it. At the moment it crashes randomly...perhaps a hardware problem...no idea. But to eliminate a software problem I would like to test the integrity of the system or of the installed package. Is it a way to check if the binary installed by binary.rpm is the good one ? with md5sum or something else ? Thx a lot, Guillaume

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,

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, on our cluster we have 5 network interfaces. I was surprised to discover that the ifcfd-* files under /etc/sysconfig/networking and /etc/sysconfig/network-scripts were not the same. So I have searched a little bit, but I'm now confused: - the files under /etc/sysconfig/networking come from system-config-network. - the files under /etc/sysconfig/network-scripts are read by the

On 6/5/2020 12:21 PM, Johnny Hughes wrote: > if you click on the six digit number, for example, e52775 for the > current latest "import 389-ds-base-1.3.10.1-9.el7_8". The result is > every diff of every change for the rpm. That's quite handy! But not what I'm looking for. I'm trying to figure out what edits I made to my config files. My most recent case was

Hi, I'm totally new with centos...we have a cluster in our labo with centos oscar. The gcc which was provided with the release is gcc41 and gfortran41. There are packages for gcc44 and gfortran44. I have installed them. But the gcc is not a link to gcc41 or gcc44. it is just an executable. idem for gfortran. So which is the good way on centOS to choose the gcc44 and gfortran44 per default.

> 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

> On Dec 7, 2015, at 8:03 PM, Wes James <comptekki at me.com> wrote: > <snip> > I finally just did yum update on this box (actually 6.3) and now it is 6.7. During the update it created a CentOS-Base.repo.rpmnew file. I renamed my current one and this one to just .repo and now I again get: > > ---- > > yum update > Loaded plugins: fastestmirror, presto

While attempting to grab some packages from the repos I've been getting a lot of mirror errors. Anyone have any idea why? I've recently updated from CentOS 5 Beta2 to the final version and it went flawlessly. The first thing I did though was to update the centos-release packages per a previous post. I was under the impression this would take care of repo problems. Was I incorrect?

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

Hello, I just started updating my RH9 Linux servers with Shorewall 1.4.9. I had Shorewall 1.4.8 installed on the server before I updated it. I installed it using the following command: rpm -Uvh Shorewall-1.4.9-1.noarch.rpm I got the normal rpm "Preparing." message and then it displayed the following message five times before listing expected warnings of creating rpmnew

> On Nov 20, 2015, at 10:41 AM, Jim Perrin <jperrin at centos.org> wrote: > > It should be looking at /6/ instead of a specific point release. We > (CentOS) do not provide updates for individual point releases. You are > several years behind in security and bug-fix updates. Once a specific > minor version is expired, it is moved off the main mirrors and into the >

Hello, does this bug still exists: http://web.archiveorange.com/archive/v/IPyW4fzzpEetiWKnJyfJ ? It seems that I have the same problem, although "store dos attributes" is set (Samba 3.6.18; GPFS 3.5.0-11). Here my share definition: [shared] comment = <comment> path = <path> available = yes

I've read that it's not recommended to automatically apply updates via yum-updated on production servers, but I keep encountering servers that have this enabled. Are any of you doing automatic yum updates on production servers in CentOS 5 via yum-updatesd? Have you experienced any negative side effects? The only thing I can think of is if say a client had a custom version of PHP

I'm puzzled by such statements as diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ I thought the point of rpmnew files was so that we could check what has been changed? Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part

This is probably a dumb question, but I'll ask anyway (I do that - you all know... :-). Due to a bug I found in OOo 2.0, I moved to using OOo 2.3, back when I was still running CentOS 5.0. Now that I have upgraded to 5.1, yum wants to update my OOo from 2.3 BACK to 2.0. Is it possible to get yum to recognize that 2.3 is newer than 2.0, or should I just exclude OOo from the updates? Thanks.