summaryrefslogtreecommitdiffstats
path: root/docs-xml/manpages-3/idmap_rid.8.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs-xml/manpages-3/idmap_rid.8.xml')
-rw-r--r--docs-xml/manpages-3/idmap_rid.8.xml7
1 files changed, 3 insertions, 4 deletions
diff --git a/docs-xml/manpages-3/idmap_rid.8.xml b/docs-xml/manpages-3/idmap_rid.8.xml
index a2a1c58a6f4..3f8735288ca 100644
--- a/docs-xml/manpages-3/idmap_rid.8.xml
+++ b/docs-xml/manpages-3/idmap_rid.8.xml
@@ -28,7 +28,7 @@
Currently, there should to be an explicit idmap configuration for each
domain that should use the idmap_rid backend, using disjoint ranges.
One usually needs to define a writeable default idmap range, using
- a backent like <parameter>tdb</parameter> or <parameter>ldap</parameter>
+ a backend like <parameter>tdb</parameter> or <parameter>ldap</parameter>
that can create unix ids, in order to be able to map the BUILTIN sids
and other domains, and also in order to be able to create group mappings.
See the example below.
@@ -106,9 +106,8 @@
security = domain
workgroup = MAIN
- idmap backend = tdb
- idmap uid = 1000000-1999999
- idmap gid = 1000000-1999999
+ idmap config * : backend = tdb
+ idmap config * : range = 1000000-1999999
idmap config MAIN : backend = rid
idmap config MAIN : range = 10000 - 49999