Dustin C. Hatch
27b172f083
If winbind is unable to communicate with any domain controller, the `pam_winbind.so` module will time out. In _auth_ and _account_ context, this was not an issue, at least for local users, because other modules terminated the stack before `pam_winbind.so` was called. In _session_ context, though, nothing terminated the stack at all, so `pam_winbind.so` was called unconditionally. This prevented even _root_ from logging in on the console. This made troubleshooting difficult, especially for the VM hosts, when the domain controllers were down.