Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 701444 - Fix libkrb5 to work when > 1024 file descriptors are in use
Fix libkrb5 to work when > 1024 file descriptors are in use
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: krb5 (Show other bugs)
5.7
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Nalin Dahyabhai
BaseOS QE Security Team
http://src.mit.edu/fisheye/changelog/...
:
Depends On:
Blocks: 701446
  Show dependency treegraph
 
Reported: 2011-05-02 17:05 EDT by Simo Sorce
Modified: 2015-10-30 10:24 EDT (History)
5 users (show)

See Also:
Fixed In Version: krb5-1.6.1-68.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 701446 (view as bug list)
Environment:
Last Closed: 2012-02-20 22:19:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2037503 None None None Never
Red Hat Product Errata RHSA-2012:0306 normal SHIPPED_LIVE Low: krb5 security and bug fix update 2012-02-21 02:24:53 EST

  None (edit)
Description Simo Sorce 2011-05-02 17:05:48 EDT
libkrb5 has issues working in processes that have more than 1024 files open due to the use of select()
Upstream has a patch to make libkrb5 use poll() instead.

Please backport it to RHEL5 so that daemons like samba do not have issues in those cases.
Comment 7 errata-xmlrpc 2012-02-20 22:19:17 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0306.html

Note You need to log in before you can comment on or make changes to this bug.