Skip to main content

Removing Duplicate RPM Packages

My OEL4 servers still have duplicate RPM packages on 64 bit servers. Libs for 32 bit and 64 bit are often installed, even though they may not always be used. When upgrading a package, such as glibc, you run into the error that yum won't touch a package because it finds duplicates.

In this case you can try Removing Duplicate RPM Packages or remove a package using an explicit architecture tag:
yum package.{i386,i686,x86_64} such as yum remove glibc.i686.

If you have RHEL/OEL5 or higher, you're in luck because you can try to install the package yum-utils and run package-cleanup --cleandupes. yum-utils offer a bunch of useful tools for working with yum repos and so on.

Comments

Popular posts from this blog

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Logbook and Note Book

I'm no longer actively working with Linux although I use it privately. This was my work logbook during my job as a Linux Engineer and Architect for KPN Data Centers.  I'm keeping this as a log and note book. Who knows when it comes in handy although much will be outdated. If you find any good resources or more current howtos for what was written here, let me know!