From 13c4c30a02269b91379a50acbc45a883588d37bf Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Tue, 31 May 2011 10:07:59 +0200 Subject: s3:doc: document "idmap backend" as deprecated. --- docs-xml/smbdotconf/winbind/idmapbackend.xml | 35 ++-------------------------- 1 file changed, 2 insertions(+), 33 deletions(-) (limited to 'docs-xml/smbdotconf') diff --git a/docs-xml/smbdotconf/winbind/idmapbackend.xml b/docs-xml/smbdotconf/winbind/idmapbackend.xml index 824476f454..bd96dfedd8 100644 --- a/docs-xml/smbdotconf/winbind/idmapbackend.xml +++ b/docs-xml/smbdotconf/winbind/idmapbackend.xml @@ -11,39 +11,8 @@ This option specifies the default backend that is used when no special - configuration set by matches the - specific request. - - - - This default backend also specifies the place where winbind-generated - idmap entries will be stored. So it is highly recommended that you - specify a writable backend like - idmap_tdb 8 - or - idmap_ldap 8 - as the idmap backend. The - idmap_rid 8 - and - idmap_ad 8 - backends are not writable and thus will generate - unexpected results if set as idmap backend. - - - - To use the rid and ad backends, please specify them via the - parameter, possibly also for the - domain your machine is member of, specified by . - - - Examples of SID/uid/gid backends include tdb ( - idmap_tdb8), - ldap (idmap_ldap - 8), rid ( - idmap_rid8), - and ad (idmap_ad - 8). + configuration set, but it is now deprecated in favour of the new + spelling . -- cgit