You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, where there would be no response from the LDAP server, there would be no R/W events on the LDAP fd, so sdap_async_sys_connect_done would never be called.
Patch 5bf2314 added a tevent timer that cancels the connection after SDAP_NETWORK_TIMEOUT seconds.
Filing this ticket for sake of tracking and linking with Bugzilla.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/977
In some cases, where there would be no response from the LDAP server, there would be no R/W events on the LDAP fd, so sdap_async_sys_connect_done would never be called.
Patch 5bf2314 added a tevent timer that cancels the connection after SDAP_NETWORK_TIMEOUT seconds.
Filing this ticket for sake of tracking and linking with Bugzilla.
Comments
Comment from jhrozek at 2011-08-19 16:07:42
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.5.13
owner: somebody => jhrozek
Comment from jhrozek at 2011-08-19 16:08:24
Fields changed
resolution: => fixed
status: new => closed
Comment from mkosek at 2011-12-16 16:16:15
Fields changed
rhbz: 731747 => [https://bugzilla.redhat.com/show_bug.cgi?id=731747 731747]
Comment from jhrozek at 2017-02-24 14:51:23
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: