Skip to main content

yum update but exclude multiple packages


I have up2date setup for my servers to update most packages but ignore kernel updates as well as oracleasm-related updates. Kernel updates break things and must be done manually, when needed. However, I prefer using yum over up2date. But until now I did not find an easy way to tell yum to ignore updates on some packages. An old Duke mailing list had an improved man yum text that eluded to add multiple exclude=package* statements to the repos in /etc/yum.repos.d/. Thanks Duke!
Here is my example yum repo configuration with the excluded packages:
[el4_patch]name=Oracle Enterprise Linux - $releasever - $basearch - patchbaseurl=http://uln.example.com/yum/EL4/$releasever/patch/$basearch/exclude=kernel*exclude=oracleasm*gpgcheck=1enabled=1

Update: something is still not right for it just upgraded the kernel anyway.
Update2: When I moved the 'exclude' lines before the 'enabled' line, the yum update process does indeed ignore kernel updates, as expected. Before, I had the exclude lines after the line to enable that repo.
Update3: You can exclude at the main yum level (/etc/yum.conf) and on a per-repository basis. Using the command line switch disableexcludes=all you can then manually install the otherwise packages anyway. [Source]

Comments

Popular posts from this blog

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.

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...

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