> b) change the fallback polling code to keep trying, instead of giving
up right away

AFAICT, this will only happen if /etc/resolv.conf is a broken symlink.

What happens if the symlink exists but doesn't provide something valid,
sssd goes into offline, and then the symlink is changed to something
that does work? I get the impression that this case hasn't been fixed.
Am I right?

Nevertheless the fix you have is correct and would be useful to land for
the common case failure. Thank you to everyone involved in identifying
the problem. So +1 for the SRU review, and this is ready to accept. I
only wait in case you want to do something different if my edge case
above is correct. Let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723350

Title:
  sssd offline on boot, stays offline forever

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to