2009/3/9 Troy Dawson <[log in to unmask]>:
> What is this glibc thing that you are talking about.  You point to a web
> page, which points to RedHat's Release notes.  RedHat's release notes are
> divided into 15 different web pages.  A little more information please.

Sorry,

Here is the link to the relevant info on RHEL's release notes:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Release_Notes/sect-Release_Notes-Known_Issues.html

Take a look at the 5th from paragraph 9.1: " The cause of the locking
issue is that the shared futex locking in glibc was enhanced with
per-process futexes between 5.2 and 5.3. As a result, programs running
against the 5.2 glibc can not properly perform shared futex locking
against programs running with the 5.3 glibc. This particular error
message is a side effect of a package calling rpm as part of its
install scripts. The rpm instance performing the upgrade is using the
prior glibc throughout the upgrade, but the rpm instance launched from
within the script is using the new glibc. To avoid this error, upgrade
glibc first in a separate run."

Hope this helps.

Regards,
Patrick