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
Before this fix, the {{{getpwnam.test}}} function would have crashed with a segfault if the SSSD server was restarted (e.g. with {{{service sssd restart}}}. Now it will properly reconnect to the SSSD with no user-visible error.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/571
Long running programs like gdm cannot reconnect to sssd after sssd is restarted, e.g. after an upgrade.
There is a corresponding report in https://bugzilla.redhat.com/show_bug.cgi?id=607233
Comments
Comment from sgallagh at 2010-07-30 13:12:37
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.2.2
owner: somebody => sbose
Comment from sgallagh at 2010-07-30 13:12:55
Fields changed
fixedin: => 1.2.2
resolution: => fixed
status: new => closed
Comment from sgallagh at 2010-07-30 13:21:54
Testing notes: this can be verified by running the following C program
This will do a getpwnam() lookup every five seconds on the user specified in the commandline. Usage:
Before this fix, the {{{getpwnam.test}}} function would have crashed with a segfault if the SSSD server was restarted (e.g. with {{{service sssd restart}}}. Now it will properly reconnect to the SSSD with no user-visible error.
Comment from mkosek at 2011-12-16 15:54:48
Fields changed
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=607233 607233]
Comment from sbose at 2017-02-24 14:51:07
Metadata Update from @sbose:
The text was updated successfully, but these errors were encountered: