Okay, snapshot of conclusions at this point...
(1) Any systems Feisty (and earlier) upgraded to Hardy (and later) would
require a manual migration of /etc/libnss-ldap.conf and /etc/pam-
ldap.conf if either or both of those files exist.
(2) None of the 5+ Ubuntu developers who have looked at this bug has
successfully reproduced the "boot hang" aspect of this bug. A boot hang
involves a system which is not responsive to a network ping, not responsive to
banging keys, and toggling caps-lock/num-lock does not affect the associated
LEDs. (That's a crude definition, of course, but some decent guidelines.)
ANYONE who is able to reproduce such a boot hang, please respond and attach (a
cleansed copy) of:
* /var/log/syslog (as retrieved from a subsequent rescue boot)
* /etc/ldap.conf
* /etc/nsswitch.conf
* /etc/libnss-ldap.conf
* /etc/pam-ldap.conf
(3) We have been able to reproduce a "hang on login". I'd argue that
this is a "functions as designed" scenario. If you require an LDAP
server to login, and it's not available, logins should not succeed until
the target LDAP server becomes available. In the case where you want to
relax that requirement, a system can be configured to use a soft bind
policy.
:-Dustin
** Changed in: libnss-ldap (Ubuntu)
Status: Confirmed => Incomplete
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
