Updating glibc redhat

Rated 3.85/5 based on 835 customer reviews

If that's not possible, then care must be taken to ensure that the correct rpm's are used.

Assuming we are talking about the updated Glibc from the RH 9 errata there are two possible procedures, as follows: for a 686 class CPU (i.e., from 'uname -m' ) one must use: rpm -F glibc-2.3.2-27.9.i686\ glibc-common-2.3.2-27.9.i3 Warning!

I have tried Google, but, I found others who had similiar problems, and how they tried to resolve them, but no concise guide on how to do the update.

The easiest and cleanest way to update Glibc on a Red Hat box is to use up2date.

Edit: The Red Hat documentation used to list the version of the libraries they included.

Our vulnerability and exploit database is updated frequently and contains the most recent security research.

When you check your redhat version, you will see something like 5.11. Patches can arrive at any time and for a production server, you want to patch them as quickly as possible.

This information is very helpful for technical support staff as well as knowing if you are up to date with the latest patches.

Having this info can help you quickly determine if software will be compatible with your system.

Leave a Reply