This bug is created as a clone of upstream ticket:
We don't close the fd when we write the selinux login file in the pam responder. This results in a fd leak.
1. lsof -p $(pidof sssd_pam) | grep selinux
2. login as a user
3. lsof -p $(pidof sssd_pam) | grep selinux
The number stays the same
The file stays open
*** Bug 872595 has been marked as a duplicate of this bug. ***
-System Test Defect Verification
Test Run Duration:
Test Env /Config:
-Red Hat Enterprise Linux Server release 6.4 Beta (Santiago)
-IPA server version 3.0.1.pre1. API version 2.44
-Installed 2012-10-29 10:49:25 -04:00 -04:00 Job=324310
-Kernel Linux version 2.6.32-330.el6.x86_64
-Installed 2 Ipa Servers and 2 Ipa clients
-10K Users divided into 10 user groups
-11 sudo rules and approx 1500 sudo commands
-I yum upgraded my test environment with the fixes Jakub submitted and the issue immediately disappeared in the next system test run.
-The test environment has been subjected to tests that previously triggered the defect. The test load is running through runtime ssh/sudo multi-thread load, cycling through 10k ipa users. Load simulating 10 concurrent simulated users 24/7 while applying light administration work via cli and UI. Over 6+ days consisting of pos/neg ssh/sudo use cases were applied against the test environment. The UI admin load use case was to add/delete sudo rules from each Ipa Server simultaneously each day.
-I'm not seeing the reported symptoms/results described in this defect. Not able to reproduced, this is a good thing.
Closing defect as Verified
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.