Freezing v3-2-stable (2nd edition)

Björn Jacke bjacke at SerNet.DE
Tue Apr 22 09:24:16 GMT 2008

On 2008-04-22 at 11:08 +0200 Volker Lendecke sent off:
> Second case: The user has an explicit "ldap timeout" set. In
> this case, that user has apparently had some reason to do
> so. In this case, I would like both new parameters to
> default to what the user explicitly set, because having that
> explicit parameter was a conscious decision. We should mark
> "ldap timeout" as deprecated then, pointing out the new
> parameters in the documentation.

if you really want you can do that. But to me this looks too complex 
to do for what it's worth. Leaving "ldap timeout" as deprecated and 
use it for both new ldap timeout parameters - but what should be done 
if the new parameters are also set? Is the "ldap timeout" overwriting 
the "ldap operation/connection timeout" timeout or vice versa? There 
are so many changes in smb.conf configuration in minor releases that 
require smb.conf adjustment. Compared to other changes this is really 
a small change and just fine for a 3.2 release I think.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url :

More information about the samba-technical mailing list