[Ubuntu-x-swat] [Bug 1732735] Re: hostname lookup broken in ldap.conf

2017-12-18 Thread Reinhard
It looks like, that there is a problem, when the ldap-client searches with exponential backoff for the servers: Following change seems to fix the problem, BUT a rational sounding has to be changed? In /etc/ldap.conf: default Reconnect policy: bind_policy hard has to be changed to: bin

[Ubuntu-x-swat] [Bug 1732735] Re: hostname lookup broken in ldap.conf

2017-11-20 Thread Reinhard
Did more testing in Ubuntu 17.10: in ldap.conf: host 10.0.0.9 10.0.0.10 => IP is working host ldap01 ldap02 => hostname is NOT working host ldap01.app.tsn => FQHN is NOT working and NOT working does not mean that just ldap is broken, it means pc stays in endless boot loop :-( -- You received