Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1135838

Summary: Man sssd-ldap shows parameter ldap_purge_cache_timeout with "Default: 10800 (12 hours)"
Product: Red Hat Enterprise Linux 6 Reporter: James Biao <jbiao>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: apeetham, grajaiya, jgalipea, lslebodn, mkosek, pbrezina, preichl
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.12.4-1.el6 Doc Type: Bug Fix
Doc Text:
Do not document
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:41:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Biao 2014-09-01 02:12:51 UTC
Description of problem:

man sssd-ldap shows 

ldap_purge_cache_timeout (integer)
               ...
               Default: 10800 (12 hours)

However 10800 seconds are 3 hours not 12 hours

Version-Release number of selected component (if applicable):


How reproducible:

man sssd-ldap and search for ldap_purge_cache_timeout

Steps to Reproduce:
1.
2.
3.

Actual results:

ldap_purge_cache_timeout (integer)
               ...
               Default: 10800 (12 hours)

Expected results:

ldap_purge_cache_timeout (integer)
               ...
               Default: 10800 (3 hours)

Additional info:

Comment 2 Lukas Slebodnik 2014-09-01 05:31:36 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2423

Comment 3 Jakub Hrozek 2014-09-04 09:08:55 UTC
RHEL6.6 is in the blocker phase already. Given that this is just a man page issue, I'm reproposing for 6.7. Thank you for reporting the bug.

Comment 4 Jakub Hrozek 2014-09-09 08:41:02 UTC
* master: 0253df73a348344fc0ae4a9302374feefa6c9452

Comment 6 Amith 2015-03-18 10:59:25 UTC
Verified the bug on SSSD Version - sssd-1.12.4-11.el6.x86_64 

Man page verified with the following contents: 

ldap_purge_cache_timeout (integer)
               Determine how often to check the cache for inactive entries (such as groups with no members and users who have never logged in) and remove them to save space. Setting this option to zero will disable the cache cleanup operation.

            Default: 10800 (3 hours)

Comment 8 errata-xmlrpc 2015-07-22 06:41:37 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.

https://rhn.redhat.com/errata/RHBA-2015-1448.html