diff options
Diffstat (limited to 'docs/htmldocs/manpages/idmap_tdb.8.html')
| -rw-r--r-- | docs/htmldocs/manpages/idmap_tdb.8.html | 53 |
1 files changed, 8 insertions, 45 deletions
diff --git a/docs/htmldocs/manpages/idmap_tdb.8.html b/docs/htmldocs/manpages/idmap_tdb.8.html index 478313b57e..ddf11e858a 100644 --- a/docs/htmldocs/manpages/idmap_tdb.8.html +++ b/docs/htmldocs/manpages/idmap_tdb.8.html @@ -4,56 +4,19 @@ </p><p> In contrast to read only backends like idmap_rid, it is an allocating backend: This means that it needs to allocate new user and group IDs in - order to create new mappings. The allocator can be provided by the - idmap_tdb backend itself or by any other allocating backend like - idmap_ldap or idmap_tdb2. This is configured with the - parameter <em class="parameter"><code>idmap alloc backend</code></em>. - </p><p> - Note that in order for this (or any other allocating) backend to - function at all, the default backend needs to be writeable. - The ranges used for uid and gid allocation are the default ranges - configured by "idmap uid" and "idmap gid". - </p><p> - Furthermore, since there is only one global allocating backend - responsible for all domains using writeable idmap backends, - any explicitly configured domain with idmap backend tdb - should have the same range as the default range, since it needs - to use the global uid / gid allocator. See the example below. - </p></div><div class="refsect1" title="IDMAP OPTIONS"><a name="id266361"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p> + order to create new mappings. + </p></div><div class="refsect1" title="IDMAP OPTIONS"><a name="id266342"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p> Defines the available matching uid and gid range for which the backend is authoritative. - If the parameter is absent, Winbind fails over to use - the "idmap uid" and "idmap gid" options - from smb.conf. - </p></dd></dl></div></div><div class="refsect1" title="EXAMPLES"><a name="id266838"></a><h2>EXAMPLES</h2><p> + </p></dd></dl></div></div><div class="refsect1" title="EXAMPLES"><a name="id266365"></a><h2>EXAMPLES</h2><p> This example shows how tdb is used as a the default idmap backend. - It configures the idmap range through the global options for all - domains encountered. This same range is used for uid/gid allocation. - </p><pre class="programlisting"> - [global] - # "idmap backend = tdb" is redundant here since it is the default - idmap backend = tdb - idmap uid = 1000000-2000000 - idmap gid = 1000000-2000000 - </pre><p> - This (rather theoretical) example shows how tdb can be used as the - allocating backend while ldap is the default backend used to store - the mappings. - It adds an explicit configuration for some domain DOM1, that - uses the tdb idmap backend. Note that the same range as the - default uid/gid range is used, since the allocator has to serve - both the default backend and the explicitly configured domain DOM1. + This configured range is used for uid and gid allocation. </p><pre class="programlisting"> [global] - idmap backend = ldap - idmap uid = 1000000-2000000 - idmap gid = 1000000-2000000 - # use a different uid/gid allocator: - idmap alloc backend = tdb - - idmap config DOM1 : backend = tdb - idmap config DOM1 : range = 1000000-2000000 - </pre></div><div class="refsect1" title="AUTHOR"><a name="id266872"></a><h2>AUTHOR</h2><p> + # "backend = tdb" is redundant here since it is the default + idmap config * : backend = tdb + idmap config * : range = 1000000-2000000 + </pre></div><div class="refsect1" title="AUTHOR"><a name="id266838"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar |