URL:
https://github.com/SSSD/sssd/pull/143
Author: fidencio
Title: #143: Explicitly add ordering dependency for the responders' sockets
Action: edited
Changed field: body
Original value:
"""
While debugging the whole breakage reported by Stric I've noticed that the NSS socket
has been starting up the NSS responder _before_ SSSD being up. Leading us to a chaotic
situation.
By adding this ordering explicitly we can avoid the reported situation.
Interesting that I haven't seen the same behaviour when starting/stopping the socket
after the system is up.
I also haven't noticed any kind of problem caused by explicitly adding
"After=sssd.service" to the unit files.
**EDITED:
- This patch set previously consisted in two patches before but I ended up dropping the
second one as I've noticed some issues about breaking the dependency cycle.
"""