Freezing v3-2-stable (2nd edition)
Volker.Lendecke at SerNet.DE
Mon Apr 21 19:56:24 GMT 2008
On Mon, Apr 21, 2008 at 05:21:24PM +0200, Björn Jacke wrote:
> On 2008-04-21 at 17:06 +0200 Volker Lendecke sent off:
> > Can we make the specific timeouts to default to "ldap
> > timeout", so that we don't change existing installations?
> having the "ldap connection timeout" *not* the default of "ldap
> timeout" is in fact a big advantage. In case of a setup
> passdb backend = ldapsam:"ldap://unreachable:389 ldap://reachable:389"
> we (or better said the LDAP libs) would timeout after infinit 15s
> to fall back to ldap://reachable:389 which might be too long for
> clients waiting for us to answer. Telling the LDAP libs to wait for 2s
> for an initial connection atempt reply and then try the next host
> makes the fallback mechanism work better IMHO.
Sure. I meant to try to default both to the "ldap timeout"
in case this is set explicitly. If no explicit ldap timeout
is set, I agree that a shorter connect timeout has benefits,
but I don't want to change behaviour for those who
consciously did set that parameter to something.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20080421/2328d943/attachment.bin
More information about the samba-technical