From 36bfb1e2282d24d2cc20f812bc59ea1ede0e660c Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Mon, 17 Sep 2012 11:55:12 -0700 Subject: docs: Remove references to mulitple passdb backends These are long-gone and confusing. Andrew Bartlett --- docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml | 29 ----------------------------- 1 file changed, 29 deletions(-) (limited to 'docs-xml/Samba3-HOWTO') diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml index c1738e397d..54e00410c9 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml @@ -19,16 +19,6 @@ Account Information Databases - -account backends -password backends -scalability -ADS -Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This -capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to -work with only one specified passwd backend. - - passdb backend smbpasswd @@ -1654,25 +1644,6 @@ regarding this facility. Password Backends - -account database -SMB/CIFS server -Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one -begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend -feature in order to simplify problems that broke some installations. This removal has made the internal -operation of Samba-3 more consistent and predictable. - - - -multiple backends -tdbsam databases -Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier -versions of Samba-3 made it possible to specify multiple password backends, and even multiple -backends of the same type. The multiple passdb backend capability caused many problems with name to SID and -SID to name ID resolution. The Samba team wrestled with the challenges and decided that this feature needed -to be removed. - - Plaintext -- cgit