--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 22, 2008 at 11:24:16AM +0200, Bj=F6rn Jacke wrote:
> if you really want you can do that. But to me this looks too complex=20
> to do for what it's worth. Leaving "ldap timeout" as deprecated and=20
> use it for both new ldap timeout parameters - but what should be done=20
> if the new parameters are also set? Is the "ldap timeout" overwriting=20
> the "ldap operation/connection timeout" timeout or vice versa? There=20
> are so many changes in smb.conf configuration in minor releases that=20
> require smb.conf adjustment. Compared to other changes this is really=20
> a small change and just fine for a 3.2 release I think.


If both "ldap timeout" and the new parameters are set, the
new, more specific ones will overwrite.

Volker

--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFIDbC5UzqjrWwMRl0RAkDwAJwNqC7sbNqaO7Jm0hMmpy 0AFYUbpQCfauVx
/JycVOfNf4oMSlDbpEsMYC0=
=0OhF
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--