#1718 Offline mode timeout not documented
Closed: Fixed None Opened 11 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=887277 (Red Hat Enterprise Linux 6)

Description of problem:
When sssd is in offline mode and a request comes in to a data provider, an
attempt to connect to the server is only made if the last attempt was 60 or
more seconds ago.

This mechanism and the specific hardcoded timeout are not found in the
documentation. It is important to have this documented, so, for example, system
administrators could predict when the clients will restore the connection after
the server comes back online.

Version-Release number of selected component (if applicable):
sssd-client-1.9.2-41.el6.x86_64
libsss_idmap-1.9.2-41.el6.x86_64
libsss_sudo-1.9.2-41.el6.x86_64
sudo-1.8.6p3-6.el6.x86_64
sssd-1.9.2-41.el6.x86_64

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
testsupdated: => 0

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Add to man pages.

changelog: =>
component: SSSD => Documentation
milestone: SSSD 1.13 beta => Interim Bucket
priority: major => critical
review: => 0

Fields changed

milestone: Interim Bucket => SSSD 1.12 beta

Fields changed

owner: somebody => okos

Fields changed

owner: okos => mzidek

Fields changed

patch: 0 => 1

Fields changed

status: new => assigned

Fields changed

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.12 beta

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2760

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Log in to comment on this ticket.

Metadata