Changeset 988 for vendor/current/docs/manpages/idmap_ad.8

Timestamp:

Nov 24, 2016, 1:14:11 PM (9 years ago)

Author:

Silvan Scherrer

Message:

Samba Server: update vendor to version 4.4.3

File:

• vendor/current/docs/manpages/idmap_ad.8 (modified) (4 diffs)

vendor/current/docs/manpages/idmap_ad.8

@@ -2 +2 @@
 .\"     Title: idmap_ad
 .\"    Author: [see the "AUTHOR" section]
-.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
-.\"      Date: 09/18/2013
+.\" Generator: DocBook XSL Stylesheets v1.7.1 <http://docbook.sf.net/>
+.\"      Date: 0
 .\"    Manual: System Administration tools
-.\"    Source: Samba 3.6
+.\"    Source: Samba 
 .\"  Language: English
 .\"
-.TH "IDMAP_AD" "8" "09/18/2013" "Samba 3\&.6" "System Administration tools"
+.TH "IDMAP_AD" "8" "0" "System Administration tools"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
@@ -34 +34 @@
 The idmap_ad plugin provides a way for Winbind to read id mappings from an AD server that uses RFC2307/SFU schema extensions\&. This module implements only the "idmap" API, and is READONLY\&. Mappings must be provided in advance by the administrator by adding the uidNumber attributes for users and gidNumber attributes for groups in the AD\&. Winbind will only map users that have a uidNumber and whose primary group have a gidNumber attribute set\&. It is however recommended that all groups in use have gidNumber attributes assigned, otherwise they are not working\&.
 .PP
-Note that the idmap_ad module has changed considerably since Samba versions 3\&.0 and 3\&.2\&. Currently, the
+Currently, the
 \fIad\fR
-backend does not work as the the default idmap backend, but one has to configure it separately for each domain for which one wants to use it, using disjoint ranges\&. One usually needs to configure a writeable default idmap range, using for example the
+backend does not work as the default idmap backend, but one has to configure it separately for each domain for which one wants to use it, using disjoint ranges\&. One usually needs to configure a writeable default idmap range, using for example the
 \fItdb\fR
 or
@@ -49 +49 @@
 .RE
 .PP
-schema_mode = <rfc2307 | sfu >
+schema_mode = <rfc2307 | sfu >
 .RS 4
-Defines the schema that idmap_ad should use when querying Active Directory regarding user and group information\&. This can be either the RFC2307 schema support included in Windows 2003 R2 or the Service for Unix (SFU) schema\&.
+Defines the schema that idmap_ad should use when querying Active Directory regarding user and group information\&. This can be either the RFC2307 schema support included in Windows 2003 R2 or the Service for Unix (SFU) schema\&.
 .RE
 .SH "EXAMPLES"
@@ -62 +62 @@
 .nf
         [global]
+
+
         idmap config * : backend = tdb
         idmap config * : range = 1000000\-1999999