URL: https://github.com/SSSD/sssd/pull/94 Title: #94: Enable {socket,dbus}-activation for responders
fidencio commented: """ Okay, I'm about to push a new version of the series ... just some small tips for testing: - Use SELinux as permissive or disabled, at least till we have the SELinux policy updated about the sssd binaries' context. - It's mentioned in the manual, but is worth to have it mentioned here as well: You must enable the responders' sockets you want to use (apart from the priv one). So, if you want to use the pam responder, please, do: "systemct enable sssd-pam.socket". - For the responders you have enabled, their sockets are started when SSSD service is started (so, in case you decided to enable enable a sssd-pam.socket and don't want to restart SSSD, remember to run "systemctl start sssd-pam.socket". I hope all the comments have been addressed (may be the case I missed some, let me know in case it happened). I'll also update the design page soon an drop an email to sssd-devel mailing list. """ See the full comment at https://github.com/SSSD/sssd/pull/94#issuecomment-267649653
_______________________________________________ sssd-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
