I think I agree with Lars assessment. Here's my datapoint to support that -
In the ldap client authentication configuration wiki page they discuss using the nss_updatedb utility to build a local cache of the passwords/groups that are stored in ldap. This would typically be used with a laptop configuration where you could find yourself away from the network with your ldap authentication server. The configuration instructions call for the following changes to nsswitch.conf: passwd: files ldap [NOTFOUND=return] db group: files ldap [NOTFOUND=return] db The expected behavior is that first the local files will be checked for id/group information, then the ldap server will be tried, if the ldap server is unable to be reached, then the cached database information will be checked. The page on the wiki has notes saying that although this *should* work it doesn't. Could it be that the libraries aren't paying proper attention to the order of the methods specified in the configuration? -- ldap config causes Ubuntu to hang at a reboot https://bugs.launchpad.net/bugs/155947 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
