URL: https://github.com/SSSD/sssd/pull/142 Title: #142: Fix breakage caused by having the NSS responder socket-activated
fidencio commented: """ The second patch is not good to go. When a responder is started by the monitor and then the same responder is socket-activated or manually started by systemctl it will lead us in a bad state as the socket(s) used by the first will be unlinked. So, we need a more robust way to avoid this to happen. It's not going to happen ever when systemd is managing the services (systemd takes care of this case), but it is likely to happen (and will happen if you consider the 3rd patch) when we mix up who is managing the services. """ See the full comment at https://github.com/SSSD/sssd/pull/142#issuecomment-277434802
_______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
