when using nss_ldap with nsswitch.conf boot process get stuck when starting named. The name service trying to resolve "bind" user through "ldap" database despite a success in the "files" database configuration used for nsswitch.conf is group: files [success=return] ldap passwd: files [success=return] ldap Was working fine in 9.0-RC3 Fix: in nss_ldap.conf: nss_initgroups_ignoreusers root,ldap,bind How-To-Repeat: install nss_ldap and configure nsswitch.conf to group: files [success=return] ldap passwd: files [success=return] ldap try to start named
This isuue is like thousand years old. And it concerns every available backend, not just ldap. The same thing is with nss_winbind, for example. Furthermore, [success=return] is the default status/action pair. Plus, first I saw this issue on like 7.x. So I can say - 7.x and 8.x are affected too. And I can say, this leads up to even more weird situation. Imagine OpenLDAP server running on a FreeBSD. After successful test we configure the same FreeBSD as LDAP client - from now on slapd will stuck on start, as it waits for itself.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped