Leonardo Rodrigues wrote the following on 10/17/2013 2:04 PM:
Em 17/10/13 15:09, Blake Hudson escreveu:
Based on your suggestion, I did find the following bug report for
glibc from 2008 (that looks like Wietse had an indirect hand in):
http://sourceware.org/bugzilla/show_bug.cgi?id=5790
It appears that the issue was resolved in glibc due to Leonardo's
diligence. Unfortunately, although the issue was reported to RH via
their Fedora bugzilla it doesn't appear RH ever took any action.
Based on my results, I don't believe RH ever backported this fix to
any version of RHEL. I'm not too worried about it since we've
migrated most of our servers to RHEL 6 and the issue is resolved in
the version of glibc used in there. However, I will see if I can file
a bug report and have RHEL take action to prevent others from running
into the same issue.
Thank you for your and Weitse's comments and suggestions which helped
confirm where this issue was so I can address the problem directly
and mitigate any additional customer impact.
i was about to reply that i had similar problems some years ago
... just have, at this exact moment, the URL on my clipboard for
pasting :)
i'm the Leonardo that filed that bug report ...
Thanks Leonardo. In fact, I remembered your issue (or one similar to
it), but not with enough clarity to lead me to the exact problem without
some additional help.
I went ahead and filed a bug against RHEL 5 through RedHat's bugzilla
(https://bugzilla.redhat.com/show_bug.cgi?id=1020486). I received a
response within 24 hours that RH will "... consider this bug while we
scope issues to fix for the next release.". I'm guessing that means that
in RHEL 5.10 there's a slim chance this issue might be resolved. Perhaps
we will save someone else from wasting time with the same issue. Thanks
for your diligence investigating and reporting this issue to RH and the
glibc guys.
--Blake
