for my part, i corrected this problem with this hack in config file. I found it was an undocumented feature of the new nss_ldap, and can be used in ldap.conf
nss_reconnect_tries 2
with a bind_policy hard it takes time to boot, but not so much (it tries only 2 times, instead of ... nearly forever). Moreover, i found recently you can change the timeout period with an (undocumented too) parameter. Didn't have the chance (time) for the moment to test it, but i think we can use it as a workaround ?
configuration workaround
for my part, i corrected this problem with this hack in config file. I found it was an undocumented feature of the new nss_ldap, and can be used in ldap.conf
nss_reconnect_tries 2
with a bind_policy hard it takes time to boot, but not so much (it tries only 2 times, instead of ... nearly forever). Moreover, i found recently you can change the timeout period with an (undocumented too) parameter. Didn't have the chance (time) for the moment to test it, but i think we can use it as a workaround ?
bye bye
mRyOuNg