source: vendor/3.5.0/docs/manpages/idmap_tdb.8

Last change on this file was 414, checked in by Herwig Bauernfeind, 15 years ago

Samba 3.5.0: Initial import

File size: 3.4 KB
Line 
1'\" t
2.\" Title: idmap_tdb
3.\" Author: [see the "AUTHOR" section]
4.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
5.\" Date: 02/19/2010
6.\" Manual: System Administration tools
7.\" Source: Samba 3.5
8.\" Language: English
9.\"
10.TH "IDMAP_TDB" "8" "02/19/2010" "Samba 3\&.5" "System Administration tools"
11.\" -----------------------------------------------------------------
12.\" * set default formatting
13.\" -----------------------------------------------------------------
14.\" disable hyphenation
15.nh
16.\" disable justification (adjust text to left margin only)
17.ad l
18.\" -----------------------------------------------------------------
19.\" * MAIN CONTENT STARTS HERE *
20.\" -----------------------------------------------------------------
21.SH "NAME"
22idmap_tdb \- Samba\'s idmap_tdb Backend for Winbind
23.SH "DESCRIPTION"
24.PP
25The idmap_tdb plugin is the default backend used by winbindd for storing SID/uid/gid mapping tables\&.
26.PP
27In 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
28\fIidmap alloc backend\fR\&.
29.PP
30Note 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"\&.
31.PP
32Furthermore, 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\&.
33.SH "IDMAP OPTIONS"
34.PP
35range = low \- high
36.RS 4
37Defines 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\&.
38.RE
39.SH "EXAMPLES"
40.PP
41This 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\&.
42.sp
43.if n \{\
44.RS 4
45.\}
46.nf
47 [global]
48 # "idmap backend = tdb" is redundant here since it is the default
49 idmap backend = tdb
50 idmap uid = 1000000\-2000000
51 idmap gid = 1000000\-2000000
52
53.fi
54.if n \{\
55.RE
56.\}
57.PP
58This (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\&.
59.sp
60.if n \{\
61.RS 4
62.\}
63.nf
64 [global]
65 idmap backend = ldap
66 idmap uid = 1000000\-2000000
67 idmap gid = 1000000\-2000000
68 # use a different uid/gid allocator:
69 idmap alloc backend = tdb
70
71 idmap config DOM1 : backend = tdb
72 idmap config DOM1 : range = 1000000\-2000000
73
74.fi
75.if n \{\
76.RE
77.\}
78.SH "AUTHOR"
79.PP
80The 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 to the way the Linux kernel is developed\&.
Note: See TracBrowser for help on using the repository browser.