Bug 974471 - pam_cgroup is slow when cgrules.conf and /etc/passwd are large
Summary: pam_cgroup is slow when cgrules.conf and /etc/passwd are large
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libcgroup
Version: 6.4
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Peter Schiffer
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Keywords: ZStream
Depends On: 972893
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-14 08:54 UTC by Jan Kurik
Modified: 2018-12-01 14:26 UTC (History)
13 users (show)

(edit)
Previously, the pam_cgoup PAM module did not use cache. Consequently, when a system had several thousand users and the cgrules.conf file contained several thousand lines of configuration settings, the login time could take several seconds. This was because the libcgroup code read /etc/passwd once for every line in cgrules.conf, unless the CGFLAG_USECACHE flag was used. With this update, the libcgroup code no longer reads the /etc/passwd file once for every line in cgrules.conf, and the login time is no longer affected in the described scenario.
Clone Of:
(edit)
Last Closed: 2013-06-25 14:07:54 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0975 normal SHIPPED_LIVE libcgroup bug fix update 2013-06-25 18:07:19 UTC

Description Jan Kurik 2013-06-14 08:54:29 UTC
This bug has been copied from bug #972893 and has been proposed
to be backported to 6.4 z-stream (EUS).

Comment 5 Mike Gahagan 2013-06-19 19:08:05 UTC
bug reproduced with libcgroup-0.37-7.1.el6_4 and fix verified with libcgroup-0.37-7.2.el6_4 per reproducer in bz 972893.

Comment 7 errata-xmlrpc 2013-06-25 14:07:54 UTC
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/RHBA-2013-0975.html


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