Learn more about these different git repos.
Other Git URLs
This situation can happen when a system is misconfigured in a way that has the NSS responder's socket enabled and also has set up the NSS responder to be explicitly configured, which is a common case if you consider a distro may end up enabling all SSSD sockets by default.
So, during boot time both NSS responders will be up.
This situation is also easy to trigger by just having ANY @responder@ explicitly added to the services' line of sssd.conf and, after the service is up, then running systemctl start sssd-@responder@.service.
PR: https://github.com/SSSD/sssd/pull/146
Fields changed
owner: somebody => fidencio patch: 0 => 1 status: new => assigned
milestone: NEEDS_TRIAGE => SSSD 1.15.1
Metadata Update from @fidencio: - Issue assigned to fidencio - Issue set to the milestone: SSSD 1.15.1
master:
Metadata Update from @lslebodn: - Custom field design_review reset - Custom field mark reset - Custom field patch adjusted to on (was: 1) - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue close_status updated to: None
Metadata Update from @lslebodn: - Custom field design_review reset - Custom field mark reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4333
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.