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.

Description of problem:
refresh_expired_interval man page doc is not clear

Version-Release number of selected component (if applicable):
sssd-1.9.2-127.el6.x86_64 (man pages)



From man sssd.conf 

refresh_expired_interval (integer)

"Specifies how many seconds SSSD has to wait before refreshing expired records"
We were trying to figure out if this is the no. of seconds before entry_cache_timeout

This can be:
Specifies how many seconds SSSD has to wait before triggering background refresh task.
 
Recommended to keep it less then entry_cache_timeout. You can consider setting this value to 3/4 * entry_cache_timeout.
Default: 0 (disabled)

Upstream ticket:
https://fedorahosted.org/sssd/ticket/2114

I agree with Niru, but I think it's too late for 6.5. We can add a Deployment Guide note, but the man pages should be fixed in 6.6

Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Fixed upstream:
*  master: 6973f38e624e757587b14f1dbabc3466492d1dac
*  sssd-1-11: ca4514cfffdc0e3ee44b48ccf1bb8e5d0377a0c3

Tested with sssd-1.11.6-12.el6.x86_64

# man sssd.conf

refresh_expired_interval (integer)
           Specifies how many seconds SSSD has to wait before triggering a background refresh task which will refresh all expired or nearly expired records.

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-2014-1375.html