Changeset 745 for trunk/server/docs/manpages
- Timestamp:
- Nov 27, 2012, 4:43:17 PM (13 years ago)
- Location:
- trunk/server
- Files:
-
- 3 deleted
- 83 edited
- 4 copied
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 581,587,591,594,597,600,615,618,740
- Property svn:mergeinfo changed
-
trunk/server/docs/manpages/eventlogadm.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "EVENTLOGADM" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "EVENTLOGADM" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 23 23 .SH "SYNOPSIS" 24 24 .HP \w'\ 'u 25 eventlogadm [\fB\- d\fR] [\fB\-h\fR] \fB\-o\fR\ addsource\ \fIEVENTLOG\fR\ \fISOURCENAME\fR\ \fIMSGFILE\fR25 eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ addsource\ \fIEVENTLOG\fR\ \fISOURCENAME\fR\ \fIMSGFILE\fR 26 26 .HP \w'\ 'u 27 eventlogadm [\fB\- d\fR] [\fB\-h\fR] \fB\-o\fR\ write\ \fIEVENTLOG\fR27 eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ write\ \fIEVENTLOG\fR 28 28 .HP \w'\ 'u 29 eventlogadm [\fB\- d\fR] [\fB\-h\fR] \fB\-o\fR\ dump\ \fIEVENTLOG\fR\ \fIRECORD_NUMBER\fR29 eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ dump\ \fIEVENTLOG\fR\ \fIRECORD_NUMBER\fR 30 30 .SH "DESCRIPTION" 31 31 .PP … … 38 38 .SH "OPTIONS" 39 39 .PP 40 \fB\-s\fR \fIFILENAME\fR 41 .RS 4 42 The 43 \-s 44 option causes 45 eventlogadm 46 to load the configuration file given as FILENAME instead of the default one used by Samba\&. 47 .RE 48 .PP 40 49 \fB\-d\fR 41 50 .RS 4 … … 275 284 DAT 276 285 \- This field should be left unset\&. 286 .RE 277 287 .SH "EXAMPLES" 278 288 .PP -
trunk/server/docs/manpages/findsmb.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "FINDSMB" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "FINDSMB" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/idmap_ad.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_AD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_AD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 24 24 .PP 25 25 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 posixAccount/posixGroup classes and relative attribute/value pairs to the user and group objects in the AD\&. 26 .PP 27 Note that the idmap_ad module has changed considerably since Samba versions 3\&.0 and 3\&.2\&. Currently, the 28 \fIad\fR 29 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 30 \fItdb\fR 31 or 32 \fIldap\fR 33 backend, in order to be able to map the BUILTIN sids and possibly other trusted domains\&. The writeable default config is also needed in order to be able to create group mappings\&. This catch\-all default idmap configuration should have a range that is disjoint from any explicitly configured domain with idmap backend 34 \fIad\fR\&. See the example below\&. 26 35 .SH "IDMAP OPTIONS" 27 36 .PP … … 44 53 .nf 45 54 [global] 46 idmap backend = tdb 47 idmap uid = 1000000\-1999999 48 idmap gid = 1000000\-1999999 55 idmap config * : backend = tdb 56 idmap config * : range = 1000000\-1999999 49 57 50 58 idmap config CORP : backend = ad -
trunk/server/docs/manpages/idmap_adex.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_ADEX" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_ADEX" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 40 40 .nf 41 41 [global] 42 idmap backend = adex 43 idmap uid = 1000\-4000000000 44 idmap gid = 1000\-4000000000 42 idmap config * : backend = adex 43 idmap config * : range = 1000\-4000000000 45 44 46 45 winbind nss info = adex -
trunk/server/docs/manpages/idmap_hash.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_HASH" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_HASH" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 41 41 .nf 42 42 [global] 43 idmap backend = hash 44 idmap uid = 1000\-4000000000 45 idmap gid = 1000\-4000000000 43 idmap config * : backend = hash 44 idmap config * : range = 1000\-4000000000 46 45 47 46 winbind nss info = hash -
trunk/server/docs/manpages/idmap_ldap.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_LDAP" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_LDAP" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 25 25 The idmap_ldap plugin provides a means for Winbind to store and retrieve SID/uid/gid mapping tables in an LDAP directory service\&. 26 26 .PP 27 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_ldap backend itself or by any other allocating backend like idmap_tdb or idmap_tdb2\&. This is configured with the parameter 28 \fIidmap alloc backend\fR\&. 29 .PP 30 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"\&. 31 .PP 32 Furthermore, since there is only one global allocating backend responsible for all domains using writeable idmap backends, any explicitly configured domain with idmap backend ldap should have the same range as the default range, since it needs to use the global uid / gid allocator\&. See the example below\&. 27 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\&. 33 28 .SH "IDMAP OPTIONS" 34 29 .PP 35 30 ldap_base_dn = DN 36 31 .RS 4 37 Defines the directory base suffix to use when searchingfor SID/uid/gid mapping entries\&. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb\&.conf\&.32 Defines the directory base suffix to use for SID/uid/gid mapping entries\&. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb\&.conf\&. 38 33 .RE 39 34 .PP 40 35 ldap_user_dn = DN 41 36 .RS 4 42 Defines the user DN to be used for authentication\&. If absent an anonymous bind will be performed\&. 37 Defines the user DN to be used for authentication\&. The secret for authenticating this user should be stored with net idmap secret (see 38 \fBnet\fR(8))\&. If absent, the ldap credentials from the ldap passdb configuration are used, and if these are also absent, an anonymous bind will be performed as last fallback\&. 43 39 .RE 44 40 .PP 45 41 ldap_url = ldap://server/ 46 42 .RS 4 47 Specifies the LDAP server to use when searching for existingSID/uid/gid map entries\&. If not defined, idmap_ldap will assume that ldap://localhost/ should be used\&.43 Specifies the LDAP server to use for SID/uid/gid map entries\&. If not defined, idmap_ldap will assume that ldap://localhost/ should be used\&. 48 44 .RE 49 45 .PP 50 46 range = low \- high 51 47 .RS 4 52 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\&. 53 .RE 54 .SH "IDMAP ALLOC OPTIONS" 55 .PP 56 ldap_base_dn = DN 57 .RS 4 58 Defines the directory base suffix under which new SID/uid/gid mapping entries should be stored\&. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb\&.conf\&. 59 .RE 60 .PP 61 ldap_user_dn = DN 62 .RS 4 63 Defines the user DN to be used for authentication\&. If absent an anonymous bind will be performed\&. 64 .RE 65 .PP 66 ldap_url = ldap://server/ 67 .RS 4 68 Specifies the LDAP server to which modify/add/delete requests should be sent\&. If not defined, idmap_ldap will assume that ldap://localhost/ should be used\&. 48 Defines the available matching uid and gid range for which the backend is authoritative\&. 69 49 .RE 70 50 .SH "EXAMPLES" 71 51 .PP 72 The follow sets of a LDAP configuration which uses two LDAP directories, one for storing the ID mappings and one for retrieving new IDs\&.52 The following example shows how an ldap directory is used as the default idmap backend\&. It also configures the idmap range and base directory suffix\&. The secret for the ldap_user_dn has to be set with "net idmap secret \'*\' password"\&. 73 53 .sp 74 54 .if n \{\ … … 77 57 .nf 78 58 [global] 79 idmap backend = ldap:ldap://localhost/ 80 idmap uid = 1000000\-1999999 81 idmap gid = 1000000\-1999999 59 idmap config * : backend = ldap 60 idmap config * : range = 1000000\-1999999 61 idmap config * : ldap_url = ldap://localhost/ 62 idmap config * : ldap_base_dn = ou=idmap,dc=example,dc=com 63 idmap config * : ldap_user_dn = cn=idmap_admin,dc=example,dc=com 64 65 .fi 66 .if n \{\ 67 .RE 68 .\} 69 .PP 70 This example shows how ldap can be used as a readonly backend while tdb is the default backend used to store the mappings\&. It adds an explicit configuration for some domain DOM1, that uses the ldap idmap backend\&. Note that a range disjoint from the default range is used\&. 71 .sp 72 .if n \{\ 73 .RS 4 74 .\} 75 .nf 76 [global] 77 # "backend = tdb" is redundant here since it is the default 78 idmap config * : backend = tdb 79 idmap config * : range = 1000000\-1999999 82 80 83 idmap alloc backend = ldap 84 idmap alloc config : ldap_url = ldap://id\-master/ 85 idmap alloc config : ldap_base_dn = ou=idmap,dc=example,dc=com 81 idmap config DOM1 : backend = ldap 82 idmap config DOM1 : range = 2000000\-2999999 83 idmap config DOM1 : read only = yes 84 idmap config DOM1 : ldap_url = ldap://server/ 85 idmap config DOM1 : ldap_base_dn = ou=idmap,dc=dom1,dc=example,dc=com 86 idmap config DOM1 : ldap_user_dn = cn=idmap_admin,dc=dom1,dc=example,dc=com 86 87 87 88 .fi -
trunk/server/docs/manpages/idmap_nss.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_NSS" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_NSS" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 33 33 .nf 34 34 [global] 35 idmap backend = tdb 36 idmap uid = 1000000\-1999999 37 idmap gid = 1000000\-1999999 35 idmap config * : backend = tdb 36 idmap config * : range = 1000000\-1999999 38 37 39 38 idmap config SAMBA : backend = nss -
trunk/server/docs/manpages/idmap_rid.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_RID" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_RID" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 24 24 .PP 25 25 The idmap_rid backend provides a way to use an algorithmic mapping scheme to map UIDs/GIDs and SIDs\&. No database is required in this case as the mapping is deterministic\&. 26 .PP 27 Note that the idmap_rid module has changed considerably since Samba versions 3\&.0\&. and 3\&.2\&. 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 28 \fItdb\fR 29 or 30 \fIldap\fR 31 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\&. 32 .PP 33 Note that the old syntax 34 \fIidmap backend = rid:"DOM1=range DOM2=range2 \&.\&.\&."\fR 35 is not supported any more since Samba version 3\&.0\&.25\&. 26 36 .SH "IDMAP OPTIONS" 27 37 .PP … … 77 87 workgroup = MAIN 78 88 79 idmap backend = tdb 80 idmap uid = 1000000\-1999999 81 idmap gid = 1000000\-1999999 89 idmap config * : backend = tdb 90 idmap config * : range = 1000000\-1999999 82 91 83 92 idmap config MAIN : backend = rid -
trunk/server/docs/manpages/idmap_tdb.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_TDB" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_TDB" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 25 25 The idmap_tdb plugin is the default backend used by winbindd for storing SID/uid/gid mapping tables\&. 26 26 .PP 27 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 28 \fIidmap alloc backend\fR\&. 29 .PP 30 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"\&. 31 .PP 32 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\&. 27 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\&. 33 28 .SH "IDMAP OPTIONS" 34 29 .PP 35 30 range = low \- high 36 31 .RS 4 37 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\&.32 Defines the available matching uid and gid range for which the backend is authoritative\&. 38 33 .RE 39 34 .SH "EXAMPLES" 40 35 .PP 41 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\&.36 This example shows how tdb is used as a the default idmap backend\&. This configured range is used for uid and gid allocation\&. 42 37 .sp 43 38 .if n \{\ … … 46 41 .nf 47 42 [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 58 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\&. 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 43 # "backend = tdb" is redundant here since it is the default 44 idmap config * : backend = tdb 45 idmap config * : range = 1000000\-2000000 73 46 74 47 .fi -
trunk/server/docs/manpages/idmap_tdb2.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "IDMAP_TDB2" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "IDMAP_TDB2" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 25 25 The idmap_tdb2 plugin is a substitute for the default idmap_tdb backend used by winbindd for storing SID/uid/gid mapping tables in clustered environments with Samba and CTDB\&. 26 26 .PP 27 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_tdb2 backend itself or by any other allocating backend like idmap_tdb or idmap_ldap\&. This is configured with the parameter 28 \fIidmap alloc backend\fR\&. 29 .PP 30 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"\&. 31 .PP 32 Furthermore, since there is only one global allocating backend responsible for all domains using writeable idmap backends, any explicitly configured domain with idmap backend tdb2 should have the same range as the default range, since it needs to use the global uid / gid allocator\&. See the example below\&. 27 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\&. 33 28 .SH "IDMAP OPTIONS" 34 29 .PP 35 30 range = low \- high 36 31 .RS 4 37 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\&. 32 Defines the available matching uid and gid range for which the backend is authoritative\&. 33 .RE 34 .PP 35 script 36 .RS 4 37 This option can be used to configure an external program for performing id mappings instead of using the tdb counter\&. The mappings are then stored int tdb2 idmap database\&. For details see the section on IDMAP SCRIPT below\&. 38 38 .RE 39 39 .SH "IDMAP SCRIPT" 40 40 .PP 41 The tdb2 idmap backend supports a script for performing id mappings through the smb\&.conf option 42 \fIidmap : script\fR\&. The script should accept the following command line options\&. 41 The tdb2 idmap backend supports an external program for performing id mappings through the smb\&.conf option 42 \fIidmap config * : script\fR 43 or its deprecated legacy form 44 \fIidmap : script\fR\&. 45 .PP 46 The mappings obtained by the script are then stored in the idmap tdb2 database instead of mappings created by the incrementing id counters\&. It is therefore important that the script covers the complete range of SIDs that can be passed in for SID to Unix ID mapping, since otherwise SIDs unmapped by the script might get mapped to IDs that had previously been mapped by the script\&. 47 .PP 48 The script should accept the following command line options\&. 43 49 .sp 44 50 .if n \{\ … … 70 76 .RE 71 77 .\} 72 .PP73 Note that the script should cover the complete range of SIDs that can be passed in for SID to Unix ID mapping, since otherwise SIDs unmapped by the script might get mapped to IDs that had previously been mapped by the script\&.74 78 .SH "EXAMPLES" 75 79 .PP 76 This example shows how tdb2 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\&.80 This example shows how tdb2 is used as a the default idmap backend\&. 77 81 .sp 78 82 .if n \{\ … … 81 85 .nf 82 86 [global] 83 idmap backend = tdb2 84 idmap uid = 1000000\-2000000 85 idmap gid = 1000000\-2000000 87 idmap config * : backend = tdb2 88 idmap config * : range = 1000000\-2000000 89 90 .fi 91 .if n \{\ 92 .RE 93 .\} 94 .PP 95 This example shows how tdb2 is used as a the default idmap backend using an external program via the script parameter: 96 .sp 97 .if n \{\ 98 .RS 4 99 .\} 100 .nf 101 [global] 102 idmap config * : backend = tdb2 103 idmap config * : range = 1000000\-2000000 104 idmap config * : script = /usr/local/samba/bin/idmap_script\&.sh 86 105 87 106 .fi -
trunk/server/docs/manpages/ldb.3
r620 r745 3 3 .\" Author: [see the "Author" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: C Library Functions 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDB" "3" "0 8/02/2011" "Samba 3\&.5" "C Library Functions"10 .TH "LDB" "3" "06/07/2011" "Samba 3\&.6" "C Library Functions" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 104 104 ldbmodify(1) 105 105 \- modify records in a ldb database using LDIF formatted input 106 .RE 106 107 .SH "FUNCTIONS" 107 108 .sp … … 429 430 \fBldb_set_debug_stderr(3)\fR 430 431 \- set a debug handler for stderr output 432 .RE 431 433 .SH "AUTHOR" 432 434 .PP -
trunk/server/docs/manpages/ldbadd.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBADD" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBADD" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 48 48 .SH "VERSION" 49 49 .PP 50 This man page is correct for version 4\&.0of the Samba suite\&.50 This man page is correct for version 3\&.6 of the Samba suite\&. 51 51 .SH "SEE ALSO" 52 52 .PP -
trunk/server/docs/manpages/ldbdel.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBDEL" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBDEL" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 48 48 .SH "VERSION" 49 49 .PP 50 This man page is correct for version 4\&.0of the Samba suite\&.50 This man page is correct for version 3\&.6 of the Samba suite\&. 51 51 .SH "SEE ALSO" 52 52 .PP -
trunk/server/docs/manpages/ldbedit.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBEDIT" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBEDIT" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 81 81 .SH "VERSION" 82 82 .PP 83 This man page is correct for version 4\&.0of the Samba suite\&.83 This man page is correct for version 3\&.6 of the Samba suite\&. 84 84 .SH "SEE ALSO" 85 85 .PP -
trunk/server/docs/manpages/ldbmodify.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBMODIFY" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBMODIFY" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 43 43 .SH "VERSION" 44 44 .PP 45 This man page is correct for version 4\&.0of the Samba suite\&.45 This man page is correct for version 3\&.6 of the Samba suite\&. 46 46 .SH "SEE ALSO" 47 47 .PP -
trunk/server/docs/manpages/ldbrename.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBRENAME" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBRENAME" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 51 51 .SH "VERSION" 52 52 .PP 53 This man page is correct for version 4\&.0of the Samba suite\&.53 This man page is correct for version 3\&.6 of the Samba suite\&. 54 54 .SH "SEE ALSO" 55 55 .PP -
trunk/server/docs/manpages/ldbsearch.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 0 8/02/20115 .\" Date: 06/07/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LDBSEARCH" "1" "0 8/02/2011" "Samba 3\&.5" "User Commands"10 .TH "LDBSEARCH" "1" "06/07/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 61 61 .SH "VERSION" 62 62 .PP 63 This man page is correct for version 4\&.0of the Samba suite\&.63 This man page is correct for version 3\&.6 of the Samba suite\&. 64 64 .SH "SEE ALSO" 65 65 .PP -
trunk/server/docs/manpages/libsmbclient.7
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: 7 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LIBSMBCLIENT" "7" "08/0 2/2011" "Samba 3\&.5" "7"10 .TH "LIBSMBCLIENT" "7" "08/08/2011" "Samba 3\&.6" "7" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/lmhosts.5
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: File Formats and Conventions 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LMHOSTS" "5" "08/0 2/2011" "Samba 3\&.5" "File Formats and Conventions"10 .TH "LMHOSTS" "5" "08/08/2011" "Samba 3\&.6" "File Formats and Conventions" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 65 65 .sp 66 66 If the trailing \'#\' is omitted then the given IP address will be returned for all names that match the given name, whatever the NetBIOS name type in the lookup\&. 67 .RE 67 68 .sp 68 69 .RE -
trunk/server/docs/manpages/log2pcap.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "LOG2PCAP" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "LOG2PCAP" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/net.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "NET" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "NET" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 468 468 .\} 469 469 comment \- Freeform text description of the group 470 .RE 470 471 .sp 471 472 .RE … … 550 551 .PP 551 552 List all interdomain trust relationships\&. 553 .SS "RPC TRUSTDOM LIST" 554 .PP 555 List all interdomain trust relationships\&. 556 .SS "RPC TRUST" 557 .SS "RPC TRUST CREATE" 558 .PP 559 Create a trust trust object by calling lsaCreateTrustedDomainEx2\&. The can be done on a single server or on two servers at once with the possibility to use a random trust password\&. 560 .PP 561 \fBOptions:\fR 562 .PP 563 otherserver 564 .RS 4 565 Domain controller of the second domain 566 .RE 567 .PP 568 otheruser 569 .RS 4 570 Admin user in the second domain 571 .RE 572 .PP 573 otherdomainsid 574 .RS 4 575 SID of the second domain 576 .RE 577 .PP 578 other_netbios_domain 579 .RS 4 580 NetBIOS (short) name of the second domain 581 .RE 582 .PP 583 otherdomain 584 .RS 4 585 DNS (full) name of the second domain 586 .RE 587 .PP 588 trustpw 589 .RS 4 590 Trust password 591 .RE 592 .PP 593 \fBExamples:\fR 594 .PP 595 Create a trust object on srv1\&.dom1\&.dom for the domain dom2 596 .RS 4 597 .sp 598 .if n \{\ 599 .RS 4 600 .\} 601 .nf 602 net rpc trust create \e 603 otherdomainsid=S\-x\-x\-xx\-xxxxxxxxxx\-xxxxxxxxxx\-xxxxxxxxx \e 604 other_netbios_domain=dom2 \e 605 otherdomain=dom2\&.dom \e 606 trustpw=12345678 \e 607 \-S srv1\&.dom1\&.dom 608 .fi 609 .if n \{\ 610 .RE 611 .\} 612 .RE 613 .PP 614 Create a trust relationship between dom1 and dom2 615 .RS 4 616 .sp 617 .if n \{\ 618 .RS 4 619 .\} 620 .nf 621 net rpc trust create \e 622 otherserver=srv2\&.dom2\&.test \e 623 otheruser=dom2adm \e 624 \-S srv1\&.dom1\&.dom 625 .fi 626 .if n \{\ 627 .RE 628 .\} 629 .RE 630 .SS "RPC TRUST DELETE" 631 .PP 632 Delete a trust trust object by calling lsaDeleteTrustedDomain\&. The can be done on a single server or on two servers at once\&. 633 .PP 634 \fBOptions:\fR 635 .PP 636 otherserver 637 .RS 4 638 Domain controller of the second domain 639 .RE 640 .PP 641 otheruser 642 .RS 4 643 Admin user in the second domain 644 .RE 645 .PP 646 otherdomainsid 647 .RS 4 648 SID of the second domain 649 .RE 650 .PP 651 \fBExamples:\fR 652 .PP 653 Delete a trust object on srv1\&.dom1\&.dom for the domain dom2 654 .RS 4 655 .sp 656 .if n \{\ 657 .RS 4 658 .\} 659 .nf 660 net rpc trust delete \e 661 otherdomainsid=S\-x\-x\-xx\-xxxxxxxxxx\-xxxxxxxxxx\-xxxxxxxxx \e 662 \-S srv1\&.dom1\&.dom 663 .fi 664 .if n \{\ 665 .RE 666 .\} 667 .RE 668 .PP 669 Delete a trust relationship between dom1 and dom2 670 .RS 4 671 .sp 672 .if n \{\ 673 .RS 4 674 .\} 675 .nf 676 net rpc trust delete \e 677 otherserver=srv2\&.dom2\&.test \e 678 otheruser=dom2adm \e 679 \-S srv1\&.dom1\&.dom 680 .fi 681 .if n \{\ 682 .RE 683 .\} 684 .RE 685 .SS "" 552 686 .SS "RPC RIGHTS" 553 687 .PP … … 726 860 .PP 727 861 Restore the mappings from the specified file or stdin\&. 728 .SS "IDMAP SECRET <DOMAIN> |ALLOC<secret>"862 .SS "IDMAP SECRET <DOMAIN> <secret>" 729 863 .PP 730 864 Store a secret for the specified domain, used primarily for domains that use idmap_ldap as a backend\&. In this case the secret is used as the password for the user DN used to bind to the ldap server\&. 865 .SS "IDMAP DELETE [\-f] [\-\-db=<DB>] <ID>" 866 .PP 867 Delete a mapping sid <\-> gid or sid <\-> uid from the IDMAP database\&. The mapping is given by <ID> which may either be a sid: S\-x\-\&.\&.\&., a gid: "GID number" or a uid: "UID number"\&. Use \-f to delete an invalid partial mapping <ID> \-> xx 868 .PP 869 Use "smbcontrol all idmap \&.\&.\&." to notify running smbd instances\&. See the 870 \fBsmbcontrol\fR(1) 871 manpage for details\&. 872 .SS "IDMAP CHECK [\-v] [\-r] [\-a] [\-T] [\-f] [\-l] [\-\-db=<DB>]" 873 .PP 874 Check and repair the IDMAP database\&. If no option is given a read only check of the database is done\&. Among others an interactive or automatic repair mode may be chosen with one of the following options: 875 .PP 876 \-r|\-\-repair 877 .RS 4 878 Interactive repair mode, ask a lot of questions\&. 879 .RE 880 .PP 881 \-a|\-\-auto 882 .RS 4 883 Noninteractive repair mode, use default answers\&. 884 .RE 885 .PP 886 \-v|\-\-verbose 887 .RS 4 888 Produce more output\&. 889 .RE 890 .PP 891 \-f|\-\-force 892 .RS 4 893 Try to apply changes, even if they do not apply cleanly\&. 894 .RE 895 .PP 896 \-T|\-\-test 897 .RS 4 898 Dry run, show what changes would be made but don\'t touch anything\&. 899 .RE 900 .PP 901 \-l|\-\-lock 902 .RS 4 903 Lock the database while doing the check\&. 904 .RE 905 .PP 906 \-\-db <DB> 907 .RS 4 908 Check the specified database\&. 909 .RE 910 .PP 911 .RS 4 912 .RE 913 It reports about the finding of the following errors: 914 .PP 915 Missing reverse mapping: 916 .RS 4 917 A record with mapping A\->B where there is no B\->A\&. Default action in repair mode is to "fix" this by adding the reverse mapping\&. 918 .RE 919 .PP 920 Invalid mapping: 921 .RS 4 922 A record with mapping A\->B where B\->C\&. Default action is to "delete" this record\&. 923 .RE 924 .PP 925 Missing or invalid HWM: 926 .RS 4 927 A high water mark is not at least equal to the largest ID in the database\&. Default action is to "fix" this by setting it to the largest ID found +1\&. 928 .RE 929 .PP 930 Invalid record: 931 .RS 4 932 Something we failed to parse\&. Default action is to "edit" it in interactive and "delete" it in automatic mode\&. 933 .RE 731 934 .SS "USERSHARE" 732 935 .PP … … 890 1093 .PP 891 1094 Delete the list of includes from the provided section (global or share)\&. 1095 .SS "REGISTRY" 1096 .PP 1097 Manipulate Samba\'s registry\&. 1098 .PP 1099 The registry commands are: 1100 .RS 4 1101 net registry enumerate \- Enumerate registry keys and values\&. 1102 .RE 1103 .RS 4 1104 net registry enumerate_recursive \- Enumerate registry key and its subkeys\&. 1105 .RE 1106 .RS 4 1107 net registry createkey \- Create a new registry key\&. 1108 .RE 1109 .RS 4 1110 net registry deletekey \- Delete a registry key\&. 1111 .RE 1112 .RS 4 1113 net registry deletekey_recursive \- Delete a registry key with subkeys\&. 1114 .RE 1115 .RS 4 1116 net registry getvalue \- Print a registry value\&. 1117 .RE 1118 .RS 4 1119 net registry getvalueraw \- Print a registry value (raw format)\&. 1120 .RE 1121 .RS 4 1122 net registry setvalue \- Set a new registry value\&. 1123 .RE 1124 .RS 4 1125 net registry increment \- Increment a DWORD registry value under a lock\&. 1126 .RE 1127 .RS 4 1128 net registry deletevalue \- Delete a registry value\&. 1129 .RE 1130 .RS 4 1131 net registry getsd \- Get security descriptor\&. 1132 .RE 1133 .RS 4 1134 net registry getsd_sdd1 \- Get security descriptor in sddl format\&. 1135 .RE 1136 .RS 4 1137 net registry setsd_sdd1 \- Set security descriptor from sddl format 1138 string\&. 1139 .RE 1140 .RS 4 1141 net registry import \- Import a registration entries (\&.reg) file\&. 1142 .RE 1143 .RS 4 1144 net registry export \- Export a registration entries (\&.reg) file\&. 1145 .RE 1146 .RS 4 1147 net registry convert \- Convert a registration entries (\&.reg) file\&. 1148 .RE 1149 .SS "REGISTRY ENUMERATE key " 1150 .PP 1151 Enumerate subkeys and values of 1152 \fIkey\fR\&. 1153 .SS "REGISTRY ENUMERATE_RECURSIVE key " 1154 .PP 1155 Enumerate values of 1156 \fIkey\fR 1157 and its subkeys\&. 1158 .SS "REGISTRY CREATEKEY key " 1159 .PP 1160 Create a new 1161 \fIkey\fR 1162 if not yet existing\&. 1163 .SS "REGISTRY DELETEKEY key " 1164 .PP 1165 Delete the given 1166 \fIkey\fR 1167 and its values from the registry, if it has no subkeys\&. 1168 .SS "REGISTRY DELETEKEY_RECURSIVE key " 1169 .PP 1170 Delete the given 1171 \fIkey\fR 1172 and all of its subkeys and values from the registry\&. 1173 .SS "REGISTRY GETVALUE key name" 1174 .PP 1175 Output type and actual value of the value 1176 \fIname\fR 1177 of the given 1178 \fIkey\fR\&. 1179 .SS "REGISTRY GETVALUERAW key name" 1180 .PP 1181 Output the actual value of the value 1182 \fIname\fR 1183 of the given 1184 \fIkey\fR\&. 1185 .SS "REGISTRY SETVALUE key name type value ..." 1186 .PP 1187 Set the value 1188 \fIname\fR 1189 of an existing 1190 \fIkey\fR\&. 1191 \fItype\fR 1192 may be one of 1193 \fIsz\fR, 1194 \fImulti_sz\fR 1195 or 1196 \fIdword\fR\&. In case of 1197 \fImulti_sz\fR 1198 \fIvalue\fR 1199 may be given multiple times\&. 1200 .SS "REGISTRY INCREMENT key name [inc]" 1201 .PP 1202 Increment the DWORD value 1203 \fIname\fR 1204 of 1205 \fIkey\fR 1206 by 1207 \fIinc\fR 1208 while holding a g_lock\&. 1209 \fIinc\fR 1210 defaults to 1\&. 1211 .SS "REGISTRY DELETEVALUE key name" 1212 .PP 1213 Delete the value 1214 \fIname\fR 1215 of the given 1216 \fIkey\fR\&. 1217 .SS "REGISTRY GETSD key" 1218 .PP 1219 Get the security descriptor of the given 1220 \fIkey\fR\&. 1221 .SS "REGISTRY GETSD_SDDL key" 1222 .PP 1223 Get the security descriptor of the given 1224 \fIkey\fR 1225 as a Security Descriptor Definition Language (SDDL) string\&. 1226 .SS "REGISTRY SETSD_SDDL keysd" 1227 .PP 1228 Set the security descriptor of the given 1229 \fIkey\fR 1230 from a Security Descriptor Definition Language (SDDL) string 1231 \fIsd\fR\&. 1232 .SS "REGISTRY IMPORT file[opt]" 1233 .PP 1234 Import a registration entries (\&.reg) 1235 \fIfile\fR\&. 1236 .SS "REGISTRY EXPORT keyfile[opt]" 1237 .PP 1238 Export a 1239 \fIkey\fR 1240 to a registration entries (\&.reg) 1241 \fIfile\fR\&. 1242 .SS "REGISTRY CONVERT in out [[inopt] outopt]" 1243 .PP 1244 Convert a registration entries (\&.reg) file 1245 \fIin\fR\&. 892 1246 .SS "EVENTLOG" 893 1247 .PP … … 1024 1378 \fIREBOOT\fR 1025 1379 is an optional parameter that can be set to reboot the remote machine after successful join to the domain\&. 1380 .RE 1026 1381 .sp 1027 1382 .RE … … 1071 1426 \fIREBOOT\fR 1072 1427 is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain\&. 1428 .RE 1073 1429 .sp 1074 1430 .RE … … 1130 1486 \fIREBOOT\fR 1131 1487 is an optional parameter that can be set to reboot the remote machine after successful rename in the domain\&. 1488 .RE 1132 1489 .sp 1133 1490 .RE … … 1180 1537 \fICOMMAND\fR 1181 1538 defines the shell command to execute\&. 1539 .RE 1182 1540 .SS "G_LOCK LOCKS" 1183 1541 .PP -
trunk/server/docs/manpages/nmbd.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "NMBD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "NMBD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/nmblookup.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "NMBLOOKUP" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "NMBLOOKUP" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/ntlm_auth.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "NTLM_AUTH" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "NTLM_AUTH" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 112 112 indicates that one side has finished supplying data to the other\&. (Which in turn could cause the helper to authenticate the user)\&. 113 113 .sp 114 Cur ently implemented parameters from the external program to the helper are:114 Currently implemented parameters from the external program to the helper are: 115 115 .PP 116 116 Username -
trunk/server/docs/manpages/pam_winbind.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: 8 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "PAM_WINBIND" "8" "08/0 2/2011" "Samba 3\&.5" "8"10 .TH "PAM_WINBIND" "8" "08/08/2011" "Samba 3\&.6" "8" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/pam_winbind.conf.5
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: 5 7 7 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "PAM_WINBIND\&.CONF" "5" "08/0 2/2011" "Samba 3\&.6" "5"10 .TH "PAM_WINBIND\&.CONF" "5" "08/08/2011" "Samba 3\&.6" "5" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/pdbedit.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "PDBEDIT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "PDBEDIT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 317 317 .\} 318 318 I: Domain Trust Account 319 .RE 319 320 .sp 320 321 .RE -
trunk/server/docs/manpages/profiles.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "PROFILES" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "PROFILES" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/rpcclient.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "RPCCLIENT" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "RPCCLIENT" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 42 42 .RE 43 43 .PP 44 \-c|\-\-command= \'command string\'45 .RS 4 46 execute semicolon separated commands (listed below))44 \-c|\-\-command=<command string> 45 .RS 4 46 Execute semicolon separated commands (listed below) 47 47 .RE 48 48 .PP … … 466 466 .RE 467 467 .PP 468 deldriver 468 deldriver <driver> 469 469 .RS 4 470 470 Delete the specified printer driver for all architectures\&. This does not delete the actual driver files from the server, only the entry from the server\'s list of drivers\&. -
trunk/server/docs/manpages/samba.7
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: Miscellanea 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SAMBA" "7" "08/0 2/2011" "Samba 3\&.5" "Miscellanea"10 .TH "SAMBA" "7" "08/08/2011" "Samba 3\&.6" "Miscellanea" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/sharesec.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SHARESEC" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SHARESEC" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 211 211 \fIO\fR 212 212 \- Take ownership 213 .RE 213 214 .sp 214 215 .RE … … 250 251 \fIFULL\fR 251 252 \- Equivalent to \'RWXDPO\' permissions 253 .RE 252 254 .SH "EXIT STATUS" 253 255 .PP -
trunk/server/docs/manpages/smb.conf.5
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: File Formats and Conventions 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMB\&.CONF" "5" "08/0 2/2011" "Samba 3\&.5" "File Formats and Conventions"10 .TH "SMB\&.CONF" "5" "08/08/2011" "Samba 3\&.6" "File Formats and Conventions" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 149 149 .\} 150 150 If no path was given, the path is set to the user\'s home directory\&. 151 .RE 151 152 .sp 152 153 .RE … … 236 237 .\} 237 238 If the share does not permit guest access and no username was given, the username is set to the located printer name\&. 239 .RE 238 240 .sp 239 241 .RE … … 456 458 %a 457 459 .RS 4 458 The architecture of the remote machine\&. It currently recognizes Samba (\fBSamba\fR), the Linux CIFS file system (\fBCIFSFS\fR), OS/2, (\fBOS2\fR), Windows for Workgroups (\fBWfWg\fR), Windows 9x/ME (\fBWin95\fR), Windows NT (\fBWinNT\fR), Windows 2000 (\fBWin2K\fR), Windows XP (\fBWinXP\fR), Windows XP 64\-bit(\fBWinXP64\fR), Windows 2003 including 2003R2 (\fBWin2K3\fR), and Windows Vista (\fBVista\fR)\&. Anything else will be known as460 The architecture of the remote machine\&. It currently recognizes Samba (\fBSamba\fR), the Linux CIFS file system (\fBCIFSFS\fR), OS/2, (\fBOS2\fR), Mac OS X (\fBOSX\fR), Windows for Workgroups (\fBWfWg\fR), Windows 9x/ME (\fBWin95\fR), Windows NT (\fBWinNT\fR), Windows 2000 (\fBWin2K\fR), Windows XP (\fBWinXP\fR), Windows XP 64\-bit(\fBWinXP64\fR), Windows 2003 including 2003R2 (\fBWin2K3\fR), and Windows Vista (\fBVista\fR)\&. Anything else will be known as 459 461 \fBUNKNOWN\fR\&. 460 462 .RE … … 463 465 .RS 4 464 466 the IP address of the client machine\&. 467 .sp 468 Before 3\&.6\&.0 it could contain IPv4 mapped IPv6 addresses, now it only contains IPv4 or IPv6 addresses\&. 465 469 .RE 466 470 .PP … … 468 472 .RS 4 469 473 the local IP address to which a client connected\&. 474 .sp 475 Before 3\&.6\&.0 it could contain IPv4 mapped IPv6 addresses, now it only contains IPv4 or IPv6 addresses\&. 470 476 .RE 471 477 .PP … … 555 561 .RS 4 556 562 controls what the default case is for new filenames (ie\&. files that don\'t currently exist in the filesystem)\&. Default 557 \fIlower\fR\&. IMPORTANT NOTE: This option will be used to modify the case of 563 \fIlower\fR\&. IMPORTANT NOTE: As part of the optimizations for directories containing large numbers of files, the following special case applies\&. If the options 564 \m[blue]\fBcase sensitive = yes\fR\m[], 565 \m[blue]\fBpreserve case = No\fR\m[], and 566 \m[blue]\fBshort preserve case = No\fR\m[] 567 are set, then the case of 558 568 \fIall\fR 559 incoming client filenames, not just new filenames if the options 560 \m[blue]\fBcase sensitive = yes\fR\m[], 561 \m[blue]\fBpreserve case = No\fR\m[], 562 \m[blue]\fBshort preserve case = No\fR\m[] 563 are set\&. This change is needed as part of the optimisations for directories containing large numbers of files\&. 569 incoming client filenames, not just new filenames, will be modified\&. See additional notes below\&. 564 570 .RE 565 571 .PP … … 909 915 .\} 910 916 \fIdevice URI\fR 911 .sp 912 .RE 913 The deviceURI is in the for of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>\&. 917 .RE 918 .sp 919 .RE 920 The deviceURI is in the format of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>\&. 914 921 .sp 915 922 Default: … … 1001 1008 .\} 1002 1009 \fIWindows 9x driver location\fR 1010 .RE 1003 1011 .sp 1004 1012 .RE … … 1109 1117 \fImax connections\fR 1110 1118 Number of maximum simultaneous connections to this share\&. 1119 .RE 1111 1120 .sp 1112 1121 .RE … … 1397 1406 Example: 1398 1407 \fI\fIannounce version\fR\fR\fI = \fR\fI2\&.0\fR\fI \fR 1408 .RE 1409 1410 async smb echo handler (G) 1411 .\" async smb echo handler 1412 .PP 1413 .RS 4 1414 This parameter specifies whether Samba should fork the async smb echo handler\&. It can be beneficial if your file system can block syscalls for a very long time\&. In some circumstances, it prolongs the timeout that Windows uses to determine whether a connection is dead\&. 1415 .sp 1416 Default: 1417 \fI\fIasync smb echo handler\fR\fR\fI = \fR\fIno\fR\fI \fR 1399 1418 .RE 1400 1419 … … 1742 1761 \fImax connections\fR 1743 1762 Number of maximum simultaneous connections to this share\&. 1763 .RE 1744 1764 .sp 1745 1765 .RE … … 1839 1859 will attempt to authenticate itself to servers using the NTLMv2 encrypted password response\&. 1840 1860 .sp 1841 If enabled, only an NTLMv2 and LMv2 response (both much more secure than earlier versions) will be sent\&. Many servers (including NT4 < SP4, Win9x and Samba 2\&.2) are not compatible with NTLMv2\&.1861 If enabled, only an NTLMv2 and LMv2 response (both much more secure than earlier versions) will be sent\&. Older servers (including NT4 < SP4, Win9x and Samba 2\&.2) are not compatible with NTLMv2 when not in an NTLMv2 supporting domain 1842 1862 .sp 1843 1863 Similarly, if enabled, NTLMv1, … … 1850 1870 client lanman auth\&. 1851 1871 .sp 1852 Note that some sites (particularly those following \'best practice\' security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM\&.1853 .sp 1854 Default: 1855 \fI\fIclient ntlmv2 auth\fR\fR\fI = \fR\fI no\fR\fI \fR1872 Note that Windows Vista and later versions already use NTLMv2 by default, and some sites (particularly those following \'best practice\' security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM\&. 1873 .sp 1874 Default: 1875 \fI\fIclient ntlmv2 auth\fR\fR\fI = \fR\fIyes\fR\fI \fR 1856 1876 .RE 1857 1877 … … 2120 2140 .RE 2121 2141 2142 ctdb locktime warn threshold (G) 2143 .\" ctdb locktime warn threshold 2144 .PP 2145 .RS 4 2146 In a cluster environment using Samba and ctdb it is critical that locks on central ctdb\-hosted databases like locking\&.tdb are not held for long\&. With the current Samba architecture it happens that Samba takes a lock and while holding that lock makes file system calls into the shared cluster file system\&. This option makes Samba warn if it detects that it has held locks for the specified number of milliseconds\&. If this happens, 2147 \fIsmbd\fR 2148 will emit a debug level 0 message into its logs and potentially into syslog\&. The most likely reason for such a log message is that an operation of the cluster file system Samba exports is taking longer than expected\&. The messages are meant as a debugging aid for potential cluster problems\&. 2149 .sp 2150 The default value of 0 disables this logging\&. 2151 .sp 2152 Default: 2153 \fI\fIctdb locktime warn threshold\fR\fR\fI = \fR\fI0\fR\fI \fR 2154 .RE 2155 2122 2156 ctdb timeout (G) 2123 2157 .\" ctdb timeout … … 2545 2579 \fIshareName\fR 2546 2580 \- the name of the existing service\&. 2581 .RE 2547 2582 .sp 2548 2583 .RE … … 3011 3046 .PP 3012 3047 .RS 4 3013 This parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either3048 This deprecated parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either 3014 3049 net rpc rights 3015 3050 or one of the Windows user and group manager tools\&. This parameter is enabled by default\&. It can be disabled to prevent members of the Domain Admins group from being able to assign privileges to users or groups which can then result in certain smbd operations running as root that would normally run under the context of the connected user\&. … … 3415 3450 .\} 3416 3451 uid of user or gid of group 3452 .RE 3417 3453 .sp 3418 3454 .RE … … 3461 3497 .\} 3462 3498 4 \- group default quotas (gid = \-1) 3499 .RE 3463 3500 .sp 3464 3501 .RE … … 3551 3588 .\} 3552 3589 Arg 8(optional) \- the number of bytes in a block(default is 1024) 3590 .RE 3553 3591 .sp 3554 3592 .RE … … 3614 3652 \m[blue]\fBguest account\fR\m[]\&. 3615 3653 .sp 3616 This param ater nullifies the benifits of setting3654 This parameter nullifies the benefits of setting 3617 3655 \m[blue]\fBrestrict anonymous = 2\fR\m[] 3618 3656 .sp … … 3908 3946 .RE 3909 3947 3910 idmap alloc backend (G)3911 .\" idmap alloc backend3912 .PP3913 .RS 43914 The idmap alloc backend provides a plugin interface for Winbind to use when allocating Unix uids/gids for Windows SIDs\&. This option refers to the name of the idmap module which will provide the id allocation functionality\&. Please refer to the man page for each idmap plugin to determine whether or not the module implements the allocation feature\&. The most common plugins are the tdb (\fBidmap_tdb\fR(8)) and ldap (\fBidmap_ldap\fR(8)) libraries\&.3915 .sp3916 This parameter defaults to the value3917 \m[blue]\fBidmap backend\fR\m[]3918 was set to, so by default winbind will allocate Unix IDs from the default backend\&. You will only need to set this parameter explicitly if you have an external source for Unix IDs, like a central database service somewhere in your company\&.3919 .sp3920 Also refer to the3921 \m[blue]\fBidmap alloc config\fR\m[]3922 option\&.3923 .sp3924 \fINo default\fR3925 .sp3926 Example:3927 \fI\fIidmap alloc backend\fR\fR\fI = \fR\fItdb\fR\fI \fR3928 .RE3929 3930 idmap alloc config (G)3931 .\" idmap alloc config3932 .PP3933 .RS 43934 The idmap alloc config prefix provides a means of managing settings for the backend defined by the3935 \m[blue]\fBidmap alloc backend\fR\m[]3936 parameter\&. Refer to the man page for each idmap plugin regarding specific configuration details\&.3937 .sp3938 \fINo default\fR3939 .RE3940 3941 3948 idmap backend (G) 3942 3949 .\" idmap backend … … 3945 3952 The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables\&. 3946 3953 .sp 3947 This option specifies the default backend that is used when no special configuration set by 3948 \m[blue]\fBidmap config\fR\m[] 3949 matches the specific request\&. 3950 .sp 3951 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 3952 \fBidmap_tdb\fR(8) 3953 or 3954 \fBidmap_ldap\fR(8) 3955 as the idmap backend\&. The 3956 \fBidmap_rid\fR(8) 3957 and 3958 \fBidmap_ad\fR(8) 3959 backends are not writable and thus will generate unexpected results if set as idmap backend\&. 3960 .sp 3961 To use the rid and ad backends, please specify them via the 3962 \m[blue]\fBidmap config\fR\m[] 3963 parameter, possibly also for the domain your machine is member of, specified by 3964 \m[blue]\fBworkgroup\fR\m[]\&. 3965 .sp 3966 Examples of SID/uid/gid backends include tdb (\fBidmap_tdb\fR(8)), ldap (\fBidmap_ldap\fR(8)), rid (\fBidmap_rid\fR(8)), and ad (\fBidmap_ad\fR(8))\&. 3954 This option specifies the default backend that is used when no special configuration set, but it is now deprecated in favour of the new spelling 3955 \m[blue]\fBidmap config * : backend\fR\m[]\&. 3967 3956 .sp 3968 3957 Default: … … 3984 3973 .PP 3985 3974 .RS 4 3986 The idmap config prefix provides a means of managing each trusted domain separately\&. The idmap config prefix should be followed by the name of the domain, a colon, and a setting specific to the chosen backend\&. There are three options available for all domains: 3975 ID mapping in Samba is the mapping between Windows SIDs and Unix user and group IDs\&. This is performed by Winbindd with a configurable plugin interface\&. Samba\'s ID mapping is configured by options starting with the 3976 \m[blue]\fBidmap config\fR\m[] 3977 prefix\&. An idmap option consists of the 3978 \m[blue]\fBidmap config\fR\m[] 3979 prefix, followed by a domain name or the asterisk character (*), a colon, and the name of an idmap setting for the chosen domain\&. 3980 .sp 3981 The idmap configuration is hence divided into groups, one group for each domain to be configured, and one group with the the asterisk instead of a proper domain name, which speifies the default configuration that is used to catch all domains that do not have an explicit idmap configuration of their own\&. 3982 .sp 3983 There are three general options available: 3987 3984 .PP 3988 3985 backend = backend_name 3989 3986 .RS 4 3990 Specifies the name of the idmap plugin to use as the SID/uid/gid backend for this domain\&. 3987 This specifies the name of the idmap plugin to use as the SID/uid/gid backend for this domain\&. The standard backends are tdb (\fBidmap_tdb\fR(8)), tdb2 (\fBidmap_tdb2\fR(8)), ldap (\fBidmap_ldap\fR(8)), , rid (\fBidmap_rid\fR(8)), , hash (\fBidmap_hash\fR(8)), , autorid (\fBidmap_autorid\fR(8)), , ad (\fBidmap_ad\fR(8)), , adex (\fBidmap_adex\fR(8)), , and nss\&. (\fBidmap_nss\fR(8)), The corresponding manual pages contain the details, but here is a summary\&. 3988 .sp 3989 The first three of these create mappings of their own using internal unixid counters and store the mappings in a database\&. These are suitable for use in the default idmap configuration\&. The rid and hash backends use a pure algorithmic calculation to determine the unixid for a SID\&. The autorid module is a mixture of the tdb and rid backend\&. It creates ranges for each domain encountered and then uses the rid algorithm for each of these automatically configured domains individually\&. The ad and adex backends both use unix IDs stored in Active Directory via the standard schema extensions\&. The nss backend reverses the standard winbindd setup and gets the unixids via names from nsswitch which can be useful in an ldap setup\&. 3991 3990 .RE 3992 3991 .PP 3993 3992 range = low \- high 3994 3993 .RS 4 3995 Defines the available matching uid and gid range for which the backend is authoritative\&. Note that the range commonly matches the allocation range due to the fact that the same backend will store and retrieve SID/uid/gid mapping entries\&. 3996 .sp 3997 winbind uses this parameter to find the backend that is authoritative for a unix ID to SID mapping, so it must be set for each individually configured domain, and it must be disjoint from the ranges set via 3998 \m[blue]\fBidmap uid\fR\m[] 3999 and 4000 \m[blue]\fBidmap gid\fR\m[]\&. 3994 Defines the available matching uid and gid range for which the backend is authoritative\&. For allocating backends, this also defines the start and the end of the range for allocating new unid IDs\&. 3995 .sp 3996 winbind uses this parameter to find the backend that is authoritative for a unix ID to SID mapping, so it must be set for each individually configured domain and for the default configuration\&. The configured ranges must be mutually disjoint\&. 3997 .RE 3998 .PP 3999 read only = yes|no 4000 .RS 4 4001 This option can be used to turn the writing backends tdb, tdb2, and ldap into read only mode\&. This can be useful e\&.g\&. in cases where a pre\-filled database exists that should not be extended automatically\&. 4001 4002 .RE 4002 4003 .sp 4003 4004 The following example illustrates how to configure the 4004 4005 \fBidmap_ad\fR(8) 4005 for the CORP domain and the4006 backend for the CORP domain and the 4006 4007 \fBidmap_tdb\fR(8) 4007 4008 backend for all other domains\&. This configuration assumes that the admin of CORP assigns unix ids below 1000000 via the SFU extensions, and winbind is supposed to use the next million entries for its own mappings from trusted domains and for local groups for example\&. … … 4011 4012 .\} 4012 4013 .nf 4013 idmap backend = tdb 4014 idmap uid = 1000000\-1999999 4015 idmap gid = 1000000\-1999999 4014 idmap config * : backend = tdb 4015 idmap config * : range = 1000000\-1999999 4016 4016 4017 4017 idmap config CORP : backend = ad … … 4038 4038 .PP 4039 4039 .RS 4 4040 The idmap gid parameter specifies the range of group ids that are allocated for the purpose of mapping UNX groups to NT group SIDs\&. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise\&.4041 .sp 4042 See also the 4043 \m[blue]\fBidmap backend\fR\m[], and 4040 The idmap gid parameter specifies the range of group ids for the default idmap configuration\&. It is now deprecated in favour of 4041 \m[blue]\fBidmap config * : range\fR\m[]\&. 4042 .sp 4043 See the 4044 4044 \m[blue]\fBidmap config\fR\m[] 4045 option s\&.4045 option\&. 4046 4046 .sp 4047 4047 Default: … … 4074 4074 .PP 4075 4075 .RS 4 4076 The idmap uid parameter specifies the range of user ids that are allocated for use in mapping UNIX users to NT user SIDs\&. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\&. 4077 .sp 4078 See also the 4079 \m[blue]\fBidmap backend\fR\m[] 4080 and 4076 The idmap uid parameter specifies the range of user ids for the default idmap configuration\&. It is now deprecated in favour of 4077 \m[blue]\fBidmap config * : range\fR\m[]\&. 4078 .sp 4079 See the 4081 4080 \m[blue]\fBidmap config\fR\m[] 4082 option s\&.4081 option\&. 4083 4082 .sp 4084 4083 Default: … … 4247 4246 .\} 4248 4247 a broadcast/mask pair\&. 4248 .RE 4249 4249 .sp 4250 4250 .RE … … 4377 4377 .\} 4378 4378 secrets and keytab \- use the secrets\&.tdb first, then the system keytab 4379 .RE 4379 4380 .sp 4380 4381 .RE … … 4694 4695 \fIOnly\fR 4695 4696 = Only update the LDAP password and let the LDAP server do the rest\&. 4697 .RE 4696 4698 .sp 4697 4699 .RE … … 4890 4892 \fIstart tls\fR 4891 4893 = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server\&. 4894 .RE 4892 4895 .sp 4893 4896 .RE … … 5392 5395 .\} 5393 5396 \fIregistry\fR 5397 .RE 5394 5398 .sp 5395 5399 .RE … … 5572 5576 .RE 5573 5577 5578 log writeable files on exit (G) 5579 .\" log writeable files on exit 5580 .PP 5581 .RS 4 5582 When the network connection between a CIFS client and Samba dies, Samba has no option but to simply shut down the server side of the network connection\&. If this happens, there is a risk of data corruption because the Windows client did not complete all write operations that the Windows application requested\&. Setting this option to "yes" makes smbd log with a level 0 message a list of all files that have been opened for writing when the network connection died\&. Those are the files that are potentially corrupted\&. It is meant as an aid for the administrator to give him a list of files to do consistency checks on\&. 5583 .sp 5584 Default: 5585 \fI\fIlog writeable files on exit\fR\fR\fI = \fR\fIno\fR\fI \fR 5586 .RE 5587 5574 5588 lppause command (S) 5575 5589 .\" lppause command … … 5872 5886 .\} 5873 5887 Files whose UNIX name begins with a dot will be presented as DOS hidden files\&. The mangled name will be created as for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that\'s three underscores)\&. 5888 .RE 5874 5889 .sp 5875 5890 .RE … … 6032 6047 \m[blue]\fBstore dos attributes\fR\m[] 6033 6048 method\&. This may be useful for exporting mounted CDs\&. 6049 .RE 6034 6050 .sp 6035 6051 .RE … … 6126 6142 \fBBad Uid\fR 6127 6143 \- Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account\&. This was the default behavior of Samba 2\&.x releases\&. Note that if a member server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS via the Name Service Switch interface\&. 6144 .RE 6128 6145 .sp 6129 6146 .RE … … 6342 6359 .\} 6343 6360 \fBSMB2\fR: Re\-implementation of the SMB protocol\&. Used by Windows Vista and newer\&. The Samba implementation of SMB2 is currently marked experimental! 6361 .RE 6344 6362 .sp 6345 6363 .RE … … 6504 6522 \fI%f\fR 6505 6523 = who the message is from\&. 6524 .RE 6506 6525 .sp 6507 6526 .RE … … 6636 6655 .RE 6637 6656 6657 multicast dns register (G) 6658 .\" multicast dns register 6659 .PP 6660 .RS 4 6661 If compiled with proper support for it, Samba will announce itself with multicast DNS services like for example provided by the Avahi daemon\&. 6662 .sp 6663 This parameter allows disabling Samba to register itself\&. 6664 .sp 6665 Default: 6666 \fI\fImulticast dns register\fR\fR\fI = \fR\fIyes\fR\fI \fR 6667 .RE 6668 6638 6669 name cache timeout (G) 6639 6670 .\" name cache timeout … … 6712 6743 \m[blue]\fBinterfaces\fR\m[] 6713 6744 parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. 6745 .RE 6714 6746 .sp 6715 6747 .RE … … 6728 6760 Example: 6729 6761 \fI\fIname resolve order\fR\fR\fI = \fR\fIlmhosts bcast host\fR\fI \fR 6762 .RE 6763 6764 ncalrpc dir (G) 6765 .\" ncalrpc dir 6766 .PP 6767 .RS 4 6768 This directory will hold a series of named pipes to allow RPC over inter\-process communication\&. 6769 .sp 6770 \&. 6771 This will allow Samba and other unix processes to interact over DCE/RPC without using TCP/IP\&. Additionally a sub\-directory \'np\' has restricted permissions, and allows a trusted communication channel between Samba processes 6772 .sp 6773 Default: 6774 \fI\fIncalrpc dir\fR\fR\fI = \fR\fI${prefix}/var/ncalrpc\fR\fI \fR 6775 .sp 6776 Example: 6777 \fI\fIncalrpc dir\fR\fR\fI = \fR\fI/var/run/samba/ncalrpc\fR\fI \fR 6730 6778 .RE 6731 6779 … … 7116 7164 .sp 7117 7165 Multiple servers may also be specified in double\-quotes\&. Whether multiple servers are supported or not and the exact syntax depends on the LDAP library you use\&. 7166 .RE 7118 7167 .sp 7119 7168 .RE … … 7279 7328 Some client/server combinations have difficulty with mixed\-case passwords\&. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems\&. These clients upper case clear text passwords even when NT LM 0\&.12 selected by the protocol negotiation request/response\&. 7280 7329 .sp 7281 This parameter defines the maximum number of characters that may be upper case in passwords\&.7330 This deprecated parameter defines the maximum number of characters that may be upper case in passwords\&. 7282 7331 .sp 7283 7332 For example, say the password given was "FRED"\&. If … … 7316 7365 security = [ads|domain|server] 7317 7366 it is possible to get Samba to do all its username/password validation using a specific remote server\&. 7318 .sp7319 This option sets the name or IP address of the password server to use\&. New syntax has been added to support defining the port to use when connecting to the server the case of an ADS realm\&. To define a port other than the default LDAP port of 389, add the port number using a colon after the name or IP address (e\&.g\&. 192\&.168\&.1\&.100:389)\&. If you do not specify a port, Samba will use the standard LDAP port of tcp/389\&. Note that port numbers have no effect on password servers for Windows NT 4\&.0 domains or netbios connections\&.7320 .sp7321 If parameter is a name, it is looked up using the parameter7322 \m[blue]\fBname resolve order\fR\m[]7323 and so may resolved by any method and order described in that parameter\&.7324 .sp7325 The password server must be a machine capable of using the "LM1\&.2X002" or the "NT LM 0\&.12" protocol, and it must be in user level security mode\&.7326 .if n \{\7327 .sp7328 .\}7329 .RS 47330 .it 1 an-trap7331 .nr an-no-space-flag 17332 .nr an-break-flag 17333 .br7334 .ps +17335 \fBNote\fR7336 .ps -17337 .br7338 Using a password server means your UNIX box (running Samba) is only as secure as your password server\&.7339 \fIDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON\'T COMPLETELY TRUST\fR\&.7340 .sp .5v7341 .RE7342 Never point a Samba server at itself for password serving\&. This will cause a loop and could lock up your Samba server!7343 .sp7344 The name of the password server takes the standard substitutions, but probably the only useful one is7345 \fI%m \fR, which means the Samba server will use the incoming client as the password server\&. If you use this then you better trust your clients, and you had better restrict them with hosts allow!7346 7367 .sp 7347 7368 If the … … 7350 7371 \fBdomain\fR 7351 7372 or 7352 \fBads\fR, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character \'*\', as the Samba server is effectively in that domain, and will use cryptographically authenticated RPC calls to authenticate the user logging on\&. The advantage of using 7353 security = domain 7354 is that if you list several hosts in the 7373 \fBads\fR, then this option 7374 \fIshould not\fR 7375 be used, as the default \'*\' indicates to Samba to determine the best DC to contact dynamically, just as all other hosts in an AD domain do\&. This allows the domain to be maintained without modification to the smb\&.conf file\&. The cryptograpic protection on the authenticated RPC calls used to verify passwords ensures that this default is safe\&. 7376 .sp 7377 \fIIt is strongly recommended that you use the default of \'*\'\fR, however if in your particular environment you have reason to specify a particular DC list, then the list of machines in this option must be a list of names or IP addresses of Domain controllers for the Domain\&. If you use the default of \'*\', or list several hosts in the 7355 7378 \fIpassword server\fR 7356 7379 option then … … 7358 7381 will try each in turn till it finds one that responds\&. This is useful in case your primary server goes down\&. 7359 7382 .sp 7360 If the7361 \fIpassword server\fR7362 option is set to the character \'*\', then Samba will attempt to auto\-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name7363 \fBWORKGROUP<1C>\fR7364 and then contacting each server returned in the list of IP addresses from the name resolution source\&.7365 .sp7366 7383 If the list of servers contains both names/IP\'s and the \'*\' character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC\'s will be added to the list as well\&. Samba will not attempt to optimize this list by locating the closest DC\&. 7384 .sp 7385 If parameter is a name, it is looked up using the parameter 7386 \m[blue]\fBname resolve order\fR\m[] 7387 and so may resolved by any method and order described in that parameter\&. 7367 7388 .sp 7368 7389 If the 7369 7390 \fIsecurity\fR 7370 7391 parameter is set to 7371 \fBserver\fR, then there are different restrictions that 7372 security = domain 7373 doesn\'t suffer from: 7392 \fBserver\fR, these additional restrictions apply: 7374 7393 .sp 7375 7394 .RS 4 … … 7399 7418 .IP \(bu 2.3 7400 7419 .\} 7401 If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in7420 You will have to ensure that your users are able to login from the Samba server, as when in 7402 7421 security = server 7403 mode the network logon will appear to come from there rather than from the users workstation\&. 7422 mode the network logon will appear to come from the Samba server rather than from the users workstation\&. 7423 .RE 7424 .sp 7425 .RS 4 7426 .ie n \{\ 7427 \h'-04'\(bu\h'+03'\c 7428 .\} 7429 .el \{\ 7430 .sp -1 7431 .IP \(bu 2.3 7432 .\} 7433 The client must not select NTLMv2 authentication\&. 7434 .RE 7435 .sp 7436 .RS 4 7437 .ie n \{\ 7438 \h'-04'\(bu\h'+03'\c 7439 .\} 7440 .el \{\ 7441 .sp -1 7442 .IP \(bu 2.3 7443 .\} 7444 The password server must be a machine capable of using the "LM1\&.2X002" or the "NT LM 0\&.12" protocol, and it must be in user level security mode\&. 7445 .RE 7446 .sp 7447 .RS 4 7448 .ie n \{\ 7449 \h'-04'\(bu\h'+03'\c 7450 .\} 7451 .el \{\ 7452 .sp -1 7453 .IP \(bu 2.3 7454 .\} 7455 Using a password server means your UNIX box (running Samba) is only as secure as (a host masqurading as) your password server\&. 7456 \fIDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON\'T COMPLETELY TRUST\fR\&. 7457 .RE 7458 .sp 7459 .RS 4 7460 .ie n \{\ 7461 \h'-04'\(bu\h'+03'\c 7462 .\} 7463 .el \{\ 7464 .sp -1 7465 .IP \(bu 2.3 7466 .\} 7467 Never point a Samba server at itself for password serving\&. This will cause a loop and could lock up your Samba server! 7468 .RE 7469 .sp 7470 .RS 4 7471 .ie n \{\ 7472 \h'-04'\(bu\h'+03'\c 7473 .\} 7474 .el \{\ 7475 .sp -1 7476 .IP \(bu 2.3 7477 .\} 7478 The name of the password server takes the standard substitutions, but probably the only useful one is 7479 \fI%m \fR, which means the Samba server will use the incoming client as the password server\&. If you use this then you better trust your clients, and you had better restrict them with hosts allow! 7480 .RE 7404 7481 .sp 7405 7482 .RE … … 7475 7552 The 7476 7553 \fBsmbd\fR(8) 7477 daemon maintains an database of file locks obtained by SMB clients\&. The default behavior is to map this internal database to POSIX locks\&. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non\-SMB method (e\&.g\&. NFS or local file access)\&. You should never need to disable this parameter\&.7554 daemon maintains an database of file locks obtained by SMB clients\&. The default behavior is to map this internal database to POSIX locks\&. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non\-SMB method (e\&.g\&. NFS or local file access)\&. It is very unlikely that you need to set this parameter to "no", unless you are sharing from an NFS mount, which is not a good idea in the first place\&. 7478 7555 .sp 7479 7556 Default: … … 7653 7730 .PP 7654 7731 .RS 4 7655 This option specifies the number of seconds before the printing subsystem is again asked for the known printers\&. If the value is greater than 60 the initial waiting time is set to 60 seconds to allow an earlier first rescan of the printing subsystem\&.7732 This option specifies the number of seconds before the printing subsystem is again asked for the known printers\&. 7656 7733 .sp 7657 7734 Setting this parameter to 0 disables any rescanning for new or removed printers after the initial startup\&. … … 7917 7994 .RE 7918 7995 7996 print notify backchannel (S) 7997 .\" print notify backchannel 7998 .PP 7999 .RS 4 8000 Windows print clients can update print queue status by expecting the server to open a backchannel SMB connection to them\&. Due to client firewall settings this can cause considerable timeouts and will often fail, as there is no guarantee the client is even running an SMB server\&. By setting this parameter to 8001 \fBno\fR 8002 the Samba print server will not try to connect back to clients and treat corresponding requests as if the connection back to the client failed\&. The default setting of 8003 \fByes\fR 8004 causes smbd to attempt this connection\&. 8005 .sp 8006 Default: 8007 \fI\fIprint notify backchannel\fR\fR\fI = \fR\fIyes\fR\fI \fR 8008 .RE 8009 7919 8010 private dir (G) 7920 8011 .\" private dir … … 8316 8407 .RE 8317 8408 8409 rpc_server (G) 8410 .\" rpc_server 8411 .PP 8412 .RS 4 8413 Defines what kind of rpc server to use for a named pipe\&. The rpc_server prefix must be followed by the pipe name, and a value\&. 8414 .sp 8415 Three possible values are currently supported: 8416 embedded 8417 daemon 8418 external 8419 .sp 8420 The classic method is to run every pipe as an internal function 8421 \fIembedded\fR 8422 in smbd\&. 8423 .sp 8424 An alternative method is to fork a 8425 \fIdaemon\fR 8426 early on at smbd startup time\&. This is supported only for selected pipes\&. 8427 .sp 8428 Choosing the 8429 \fIexternal\fR 8430 option allows to run a completely independent (3rd party) server capable of interfacing with samba via the MS\-RPC interface over named pipes\&. 8431 .sp 8432 Currently only the spoolss pipe can be configured in 8433 \fIdaemon\fR 8434 mode like this: 8435 .sp 8436 .if n \{\ 8437 .RS 4 8438 .\} 8439 .nf 8440 rpc_server:spoolss = daemon 8441 8442 .fi 8443 .if n \{\ 8444 .RE 8445 .\} 8446 .sp 8447 Default: 8448 \fI\fIrpc_server\fR\fR\fI = \fR\fInone\fR\fI \fR 8449 .RE 8450 8318 8451 security mask (S) 8319 8452 .\" security mask … … 8356 8489 .sp 8357 8490 The alternatives are 8358 security = share, 8359 security = server 8491 security = ads 8360 8492 or 8361 security = domain\&. 8493 security = domain, which support joining Samba to a Windows domain, along with 8494 security = share 8495 and 8496 security = server, both of which are deprecated\&. 8362 8497 .sp 8363 8498 In versions of Samba prior to 2\&.0\&.0, the default was … … 8365 8500 mainly because that was the only option at one stage\&. 8366 8501 .sp 8367 There is a bug in WfWg that has relevance to this setting\&. When in user or server level security a WfWg client will totally ignore the username and password you type in the "connect drive" dialog box\&. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as\&. 8368 .sp 8369 If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use 8370 security = user\&. If you mostly use usernames that don\'t exist on the UNIX box then use 8371 security = share\&. 8372 .sp 8373 You should also use 8374 security = share 8375 if you want to mainly setup shares without a password (guest shares)\&. This is commonly used for a shared printer server\&. It is more difficult to setup guest shares with 8376 security = user, see the 8502 You should use 8503 security = user 8504 and 8377 8505 \m[blue]\fBmap to guest\fR\m[] 8378 parameter for details\&.8506 if you want to mainly setup shares without a password (guest shares)\&. This is commonly used for a shared printer server\&. 8379 8507 .sp 8380 8508 It is possible to use … … 8387 8515 The different settings will now be explained\&. 8388 8516 .sp 8389 \fISECURITY = SHARE\fR8390 .sp8391 When clients connect to a share level security server, they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a8392 security = share8393 server)\&. Instead, the clients send authentication information (passwords) on a per\-share basis, at the time they attempt to connect to that share\&.8394 .sp8395 Note that8396 smbd8397 \fIALWAYS\fR8398 uses a valid UNIX user to act on behalf of the client, even in8399 security = share8400 level security\&.8401 .sp8402 As clients are not required to send a username to the server in share level security,8403 smbd8404 uses several techniques to determine the correct UNIX user to use on behalf of the client\&.8405 .sp8406 A list of possible UNIX usernames to match with the given client password is constructed using the following methods :8407 .sp8408 .RS 48409 .ie n \{\8410 \h'-04'\(bu\h'+03'\c8411 .\}8412 .el \{\8413 .sp -18414 .IP \(bu 2.38415 .\}8416 If the8417 \m[blue]\fBguest only\fR\m[]8418 parameter is set, then all the other stages are missed and only the8419 \m[blue]\fBguest account\fR\m[]8420 username is checked\&.8421 .RE8422 .sp8423 .RS 48424 .ie n \{\8425 \h'-04'\(bu\h'+03'\c8426 .\}8427 .el \{\8428 .sp -18429 .IP \(bu 2.38430 .\}8431 Is a username is sent with the share connection request, then this username (after mapping \- see8432 \m[blue]\fBusername map\fR\m[]), is added as a potential username\&.8433 .RE8434 .sp8435 .RS 48436 .ie n \{\8437 \h'-04'\(bu\h'+03'\c8438 .\}8439 .el \{\8440 .sp -18441 .IP \(bu 2.38442 .\}8443 If the client did a previous8444 \fIlogon \fR8445 request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username\&.8446 .RE8447 .sp8448 .RS 48449 .ie n \{\8450 \h'-04'\(bu\h'+03'\c8451 .\}8452 .el \{\8453 .sp -18454 .IP \(bu 2.38455 .\}8456 The name of the service the client requested is added as a potential username\&.8457 .RE8458 .sp8459 .RS 48460 .ie n \{\8461 \h'-04'\(bu\h'+03'\c8462 .\}8463 .el \{\8464 .sp -18465 .IP \(bu 2.38466 .\}8467 The NetBIOS name of the client is added to the list as a potential username\&.8468 .RE8469 .sp8470 .RS 48471 .ie n \{\8472 \h'-04'\(bu\h'+03'\c8473 .\}8474 .el \{\8475 .sp -18476 .IP \(bu 2.38477 .\}8478 Any users on the8479 \m[blue]\fBuser\fR\m[]8480 list are added as potential usernames\&.8481 .sp8482 .RE8483 If the8484 \fIguest only\fR8485 parameter is not set, then this list is then tried with the supplied password\&. The first user for whom the password matches will be used as the UNIX user\&.8486 .sp8487 If the8488 \fIguest only\fR8489 parameter is set, or no username can be determined then if the share is marked as available to the8490 \fIguest account\fR, then this guest user will be used, otherwise access is denied\&.8491 .sp8492 Note that it can be8493 \fIvery\fR8494 confusing in share\-level security as to which UNIX username will eventually be used in granting access\&.8495 .sp8496 See also the section8497 NOTE ABOUT USERNAME/PASSWORD VALIDATION\&.8498 .sp8499 8517 \fISECURITY = USER\fR 8500 8518 .sp 8501 This is the default security setting in Samba 3\&.0\&. With user\-level security a client must first "log\-on" with a valid username and password (which can be mapped using the8519 This is the default security setting in Samba\&. With user\-level security a client must first "log\-on" with a valid username and password (which can be mapped using the 8502 8520 \m[blue]\fBusername map\fR\m[] 8503 8521 parameter)\&. Encrypted passwords (see the … … 8555 8573 parameter\&. 8556 8574 .sp 8557 \fISECURITY = SERVER\fR 8558 .sp 8559 In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box\&. If this fails it will revert to 8560 security = user\&. It expects the 8561 \m[blue]\fBencrypted passwords\fR\m[] 8562 parameter to be set to 8563 \fByes\fR, unless the remote server does not support them\&. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid 8564 smbpasswd 8565 file to check users against\&. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up\&. 8575 \fISECURITY = SHARE\fR 8566 8576 .if n \{\ 8567 8577 .sp … … 8576 8586 .ps -1 8577 8587 .br 8578 This mode of operation has significant pitfalls since it is more vulnerable to man\-in\-the\-middle attacks and server impersonation\&. In particular, this mode of operation can cause significant resource consuption on the PDC, as it must maintain an active connection for the duration of the user\'s session\&. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authentications to the Samba server may fail (from a single client, till it disconnects)\&. 8588 This option is deprecated as it is incompatible with SMB2 8589 .sp .5v 8590 .RE 8591 When clients connect to a share level security server, they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a 8592 security = share 8593 server)\&. Instead, the clients send authentication information (passwords) on a per\-share basis, at the time they attempt to connect to that share\&. 8594 .sp 8595 Note that 8596 smbd 8597 \fIALWAYS\fR 8598 uses a valid UNIX user to act on behalf of the client, even in 8599 security = share 8600 level security\&. 8601 .sp 8602 As clients are not required to send a username to the server in share level security, 8603 smbd 8604 uses several techniques to determine the correct UNIX user to use on behalf of the client\&. 8605 .sp 8606 A list of possible UNIX usernames to match with the given client password is constructed using the following methods : 8607 .sp 8608 .RS 4 8609 .ie n \{\ 8610 \h'-04'\(bu\h'+03'\c 8611 .\} 8612 .el \{\ 8613 .sp -1 8614 .IP \(bu 2.3 8615 .\} 8616 If the 8617 \m[blue]\fBguest only\fR\m[] 8618 parameter is set, then all the other stages are missed and only the 8619 \m[blue]\fBguest account\fR\m[] 8620 username is checked\&. 8621 .RE 8622 .sp 8623 .RS 4 8624 .ie n \{\ 8625 \h'-04'\(bu\h'+03'\c 8626 .\} 8627 .el \{\ 8628 .sp -1 8629 .IP \(bu 2.3 8630 .\} 8631 Is a username is sent with the share connection request, then this username (after mapping \- see 8632 \m[blue]\fBusername map\fR\m[]), is added as a potential username\&. 8633 .RE 8634 .sp 8635 .RS 4 8636 .ie n \{\ 8637 \h'-04'\(bu\h'+03'\c 8638 .\} 8639 .el \{\ 8640 .sp -1 8641 .IP \(bu 2.3 8642 .\} 8643 If the client did a previous 8644 \fIlogon \fR 8645 request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username\&. 8646 .RE 8647 .sp 8648 .RS 4 8649 .ie n \{\ 8650 \h'-04'\(bu\h'+03'\c 8651 .\} 8652 .el \{\ 8653 .sp -1 8654 .IP \(bu 2.3 8655 .\} 8656 The name of the service the client requested is added as a potential username\&. 8657 .RE 8658 .sp 8659 .RS 4 8660 .ie n \{\ 8661 \h'-04'\(bu\h'+03'\c 8662 .\} 8663 .el \{\ 8664 .sp -1 8665 .IP \(bu 2.3 8666 .\} 8667 The NetBIOS name of the client is added to the list as a potential username\&. 8668 .RE 8669 .sp 8670 .RS 4 8671 .ie n \{\ 8672 \h'-04'\(bu\h'+03'\c 8673 .\} 8674 .el \{\ 8675 .sp -1 8676 .IP \(bu 2.3 8677 .\} 8678 Any users on the 8679 \m[blue]\fBuser\fR\m[] 8680 list are added as potential usernames\&. 8681 .RE 8682 .sp 8683 .RE 8684 If the 8685 \fIguest only\fR 8686 parameter is not set, then this list is then tried with the supplied password\&. The first user for whom the password matches will be used as the UNIX user\&. 8687 .sp 8688 If the 8689 \fIguest only\fR 8690 parameter is set, or no username can be determined then if the share is marked as available to the 8691 \fIguest account\fR, then this guest user will be used, otherwise access is denied\&. 8692 .sp 8693 Note that it can be 8694 \fIvery\fR 8695 confusing in share\-level security as to which UNIX username will eventually be used in granting access\&. 8696 .sp 8697 See also the section 8698 NOTE ABOUT USERNAME/PASSWORD VALIDATION\&. 8699 .sp 8700 \fISECURITY = SERVER\fR 8701 .sp 8702 In this depicted mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box\&. If this fails it will revert to 8703 security = user\&. It expects the 8704 \m[blue]\fBencrypted passwords\fR\m[] 8705 parameter to be set to 8706 \fByes\fR, unless the remote server does not support them\&. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid 8707 smbpasswd 8708 file to check users against\&. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up\&. 8709 .if n \{\ 8710 .sp 8711 .\} 8712 .RS 4 8713 .it 1 an-trap 8714 .nr an-no-space-flag 1 8715 .nr an-break-flag 1 8716 .br 8717 .ps +1 8718 \fBNote\fR 8719 .ps -1 8720 .br 8721 This mode of operation has significant pitfalls since it is more vulnerable to man\-in\-the\-middle attacks and server impersonation\&. In particular, this mode of operation can cause significant resource consumption on the PDC, as it must maintain an active connection for the duration of the user\'s session\&. Furthermore, if this connection is lost, there is no way to reestablish it, and further authentications to the Samba server may fail (from a single client, till it disconnects)\&. 8722 .sp .5v 8723 .RE 8724 .if n \{\ 8725 .sp 8726 .\} 8727 .RS 4 8728 .it 1 an-trap 8729 .nr an-no-space-flag 1 8730 .nr an-break-flag 1 8731 .br 8732 .ps +1 8733 \fBNote\fR 8734 .ps -1 8735 .br 8736 If the client selects NTLMv2 authentication, then this mode of operation 8737 \fIwill fail\fR 8579 8738 .sp .5v 8580 8739 .RE … … 8597 8756 .sp .5v 8598 8757 .RE 8758 .if n \{\ 8759 .sp 8760 .\} 8761 .RS 4 8762 .it 1 an-trap 8763 .nr an-no-space-flag 1 8764 .nr an-break-flag 1 8765 .br 8766 .ps +1 8767 \fBNote\fR 8768 .ps -1 8769 .br 8770 This option is deprecated, and may be removed in future 8771 .sp .5v 8772 .RE 8599 8773 \fINote\fR 8600 8774 that the name of the resource being requested is … … 8629 8803 .RE 8630 8804 8805 send spnego principal (G) 8806 .\" send spnego principal 8807 .PP 8808 .RS 4 8809 This parameter determines whether or not 8810 \fBsmbd\fR(8) 8811 will send the server\-supplied principal sometimes given in the SPNEGO exchange\&. 8812 .sp 8813 If enabled, Samba can attempt to help clients to use Kerberos to contact it, even when known only by IP address or a name not registered with our KDC as a service principal name\&. Kerberos relies on names, so ordinarily cannot function in this situation\&. 8814 .sp 8815 If disabled, Samba will send the string not_defined_in_RFC4178@please_ignore as the \'rfc4178 hint\', following the updated RFC and Windows 2008 behaviour in this area\&. 8816 .sp 8817 Note that Windows XP SP2 and later versions already ignored this value in all circumstances\&. 8818 .sp 8819 Default: 8820 \fI\fIsend spnego principal\fR\fR\fI = \fR\fIno\fR\fI \fR 8821 .RE 8822 8631 8823 server schannel (G) 8632 8824 .\" server schannel … … 8796 8988 .\} 8797 8989 4 \- group default quotas (gid = \-1) 8990 .RE 8798 8991 .sp 8799 8992 .RE … … 8875 9068 .\} 8876 9069 8(optional) \- block size, defaults to 1024 9070 .RE 8877 9071 .sp 8878 9072 .RE … … 9031 9225 will be substituted with the switch 9032 9226 \fI\-f\fR\&. It means force the shutdown even if applications do not respond for NT\&. 9227 .RE 9033 9228 .sp 9034 9229 .RE … … 9059 9254 Example: 9060 9255 \fI\fIshutdown script\fR\fR\fI = \fR\fI/usr/local/samba/sbin/shutdown %m %t %r %f\fR\fI \fR 9256 .RE 9257 9258 smb2 max credits (G) 9259 .\" smb2 max credits 9260 .PP 9261 .RS 4 9262 This option controls the maximum number of outstanding simultaneous SMB2 operations that Samba tells the client it will allow\&. This is similar to the 9263 \m[blue]\fBmax mux\fR\m[] 9264 parameter for SMB1\&. You should never need to set this parameter\&. 9265 .sp 9266 The default is 8192 credits, which is the same as a Windows 2008R2 SMB2 server\&. 9267 .sp 9268 Default: 9269 \fI\fIsmb2 max credits\fR\fR\fI = \fR\fI128\fR\fI \fR 9270 .RE 9271 9272 smb2 max read (G) 9273 .\" smb2 max read 9274 .PP 9275 .RS 4 9276 This option specifies the protocol value that 9277 \fBsmbd\fR(8) 9278 will return to a client, informing the client of the largest size that may be returned by a single SMB2 read call\&. 9279 .sp 9280 The default is 1048576 bytes (1MB), which is the same as a Windows7 SMB2 server\&. 9281 .sp 9282 Default: 9283 \fI\fIsmb2 max read\fR\fR\fI = \fR\fI1048576\fR\fI \fR 9284 .RE 9285 9286 smb2 max trans (G) 9287 .\" smb2 max trans 9288 .PP 9289 .RS 4 9290 This option specifies the protocol value that 9291 \fBsmbd\fR(8) 9292 will return to a client, informing the client of the largest size of buffer that may be used in querying file meta\-data via QUERY_INFO and related SMB2 calls\&. 9293 .sp 9294 The default is 1048576 bytes (1MB), which is the same as a Windows7 SMB2 server\&. 9295 .sp 9296 Default: 9297 \fI\fIsmb2 max trans\fR\fR\fI = \fR\fI1048576\fR\fI \fR 9298 .RE 9299 9300 smb2 max write (G) 9301 .\" smb2 max write 9302 .PP 9303 .RS 4 9304 This option specifies the protocol value that 9305 \fBsmbd\fR(8) 9306 will return to a client, informing the client of the largest size that may be sent to the server by a single SMB2 write call\&. 9307 .sp 9308 The default is 1048576 bytes (1MB), which is the same as a Windows7 SMB2 server\&. 9309 .sp 9310 Default: 9311 \fI\fIsmb2 max write\fR\fR\fI = \fR\fI1048576\fR\fI \fR 9061 9312 .RE 9062 9313 … … 9261 9512 .\} 9262 9513 SO_RCVLOWAT * 9514 .RE 9263 9515 .sp 9264 9516 .RE … … 9346 9598 This is a boolean that controls the handling of disk space allocation in the server\&. When this is set to 9347 9599 \fByes\fR 9348 the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size\&. In UNIX terminology this means that Samba will stop creating sparse files\&. This can be slow on some systems\&. When you work with large files like >100MB or so you may even run into problems with clients running into timeouts\&. 9600 the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size\&. In UNIX terminology this means that Samba will stop creating sparse files\&. 9601 .sp 9602 This option is really desgined for file systems that support fast allocation of large numbers of blocks such as extent\-based file systems\&. On file systems that don\'t support extents (most notably ext3) this can make Samba slower\&. When you work with large files over >100MB on file systems without extents you may even run into problems with clients running into timeouts\&. 9349 9603 .sp 9350 9604 When you have an extent based filesystem it\'s likely that we can make use of unwritten extents which allows Samba to allocate even large amounts of space very fast and you will not see any timeout problems caused by strict allocate\&. With strict allocate in use you will also get much better out of quota messages in case you use quotas\&. Another advantage of activating this setting is that it will help to reduce file fragmentation\&. … … 9491 9745 .PP 9492 9746 .RS 4 9493 This parameter is a setting in minutes to add to the normal GMT to local time conversion\&. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling\&. 9494 .sp 9747 This deprecated parameter is a setting in minutes to add to the normal GMT to local time conversion\&. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling\&. 9748 .if n \{\ 9749 .sp 9750 .\} 9751 .RS 4 9752 .it 1 an-trap 9753 .nr an-no-space-flag 1 9754 .nr an-break-flag 1 9755 .br 9756 .ps +1 9757 \fBNote\fR 9758 .ps -1 9759 .br 9760 This option is deprecated, and will be removed in the next major release 9761 .sp .5v 9762 .RE 9495 9763 Default: 9496 9764 \fI\fItime offset\fR\fR\fI = \fR\fI0\fR\fI \fR … … 9557 9825 .RE 9558 9826 9559 update encrypted (G)9560 .\" update encrypted9561 .PP9562 .RS 49563 This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on\&. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the wire, and are checked against a UNIX account database) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re\-enter their passwords via smbpasswd at the time the change is made\&. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period\&. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to9564 \fBno\fR\&.9565 .sp9566 In order for this parameter to be operative the9567 \m[blue]\fBencrypt passwords\fR\m[]9568 parameter must be set to9569 \fBno\fR\&. The default value of9570 \m[blue]\fBencrypt passwords = Yes\fR\m[]\&. Note: This must be set to9571 \fBno\fR9572 for this9573 \m[blue]\fBupdate encrypted\fR\m[]9574 to work\&.9575 .sp9576 Note that even when this parameter is set, a user authenticating to9577 smbd9578 must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords\&.9579 .sp9580 Default:9581 \fI\fIupdate encrypted\fR\fR\fI = \fR\fIno\fR\fI \fR9582 .RE9583 9584 9827 use client driver (S) 9585 9828 .\" use client driver … … 9626 9869 Example: 9627 9870 \fI\fIusername level\fR\fR\fI = \fR\fI5\fR\fI \fR 9871 .RE 9872 9873 username map cache time (G) 9874 .\" username map cache time 9875 .PP 9876 .RS 4 9877 Mapping usernames with the 9878 \m[blue]\fBusername map\fR\m[] 9879 or 9880 \m[blue]\fBusername map script\fR\m[] 9881 features of Samba can be relatively expensive\&. During login of a user, the mapping is done several times\&. In particular, calling the 9882 \m[blue]\fBusername map script\fR\m[] 9883 can slow down logins if external databases have to be queried from the script being called\&. 9884 .sp 9885 The parameter 9886 \m[blue]\fBusername map cache time\fR\m[] 9887 controls a mapping cache\&. It specifies the number of seconds a mapping from the username map file or script is to be efficiently cached\&. The default of 0 means no caching is done\&. 9888 .sp 9889 Default: 9890 \fI\fIusername map cache time\fR\fR\fI = \fR\fI0\fR\fI \fR 9891 .sp 9892 Example: 9893 \fI\fIusername map cache time\fR\fR\fI = \fR\fI60\fR\fI \fR 9628 9894 .RE 9629 9895 … … 9788 10054 Multiple users may be specified in a comma\-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\&. 9789 10055 .sp 9790 The 10056 The deprecated 9791 10057 \fIusername\fR 9792 10058 line is needed only when the PC is unable to supply its own username\&. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\&. In both these cases you may also be better using the \e\eserver\eshare%user syntax instead\&. … … 9945 10211 .PP 9946 10212 .RS 4 9947 This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism\&.10213 This deprecated variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism\&. 9948 10214 .sp 9949 10215 Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled\&. … … 10240 10506 .RE 10241 10507 10508 winbind max clients (G) 10509 .\" winbind max clients 10510 .PP 10511 .RS 4 10512 This parameter specifies the maximum number of clients the 10513 \fBwinbindd\fR(8) 10514 daemon can connect with\&. 10515 .sp 10516 Default: 10517 \fI\fIwinbind max clients\fR\fR\fI = \fR\fI200\fR\fI \fR 10518 .RE 10519 10520 winbind max domain connections (G) 10521 .\" winbind max domain connections 10522 .PP 10523 .RS 4 10524 This parameter specifies the maximum number of simultaneous connections that the 10525 \fBwinbindd\fR(8) 10526 daemon should open to the domain controller of one domain\&. Setting this parameter to a value greater than 1 can improve scalability with many simultaneous winbind requests, some of which might be slow\&. 10527 .sp 10528 Note that if 10529 \m[blue]\fBwinbind offline logon\fR\m[] 10530 is set to 10531 \fBYes\fR, then only one DC connection is allowed per domain, regardless of this setting\&. 10532 .sp 10533 Default: 10534 \fI\fIwinbind max domain connections\fR\fR\fI = \fR\fI1\fR\fI \fR 10535 .sp 10536 Example: 10537 \fI\fIwinbind max domain connections\fR\fR\fI = \fR\fI10\fR\fI \fR 10538 .RE 10539 10242 10540 winbind nested groups (G) 10243 10541 .\" winbind nested groups … … 10298 10596 \fIidmap config DOMAIN:backend\fR 10299 10597 = ad as well\&. 10598 .RE 10300 10599 .sp 10301 10600 .RE … … 10404 10703 This parameter specifies whether the 10405 10704 \fBwinbindd\fR(8) 10406 daemon should operate on users without domain component in their username\&. Users without a domain component are treated as is part of the winbindd server\'s own domain\&. While this does not benifit Windows users, it makes SSH, FTP and e\-mail function in a way much closer to the way they would in a native unix system\&. 10705 daemon should operate on users without domain component in their username\&. Users without a domain component are treated as is part of the winbindd server\'s own domain\&. While this does not benefit Windows users, it makes SSH, FTP and e\-mail function in a way much closer to the way they would in a native unix system\&. 10706 .sp 10707 This option should be avoided if possible\&. It can cause confusion about responsibilities for a user or group\&. In many situations it is not clear whether winbind or /etc/passwd should be seen as authoritative for a user, likewise for groups\&. 10407 10708 .sp 10408 10709 Default: … … 10476 10777 .\} 10477 10778 The fifth and subsequent arguments are the IP addresses currently registered for that name\&. If this list is empty then the name should be deleted\&. 10779 .RE 10478 10780 .sp 10479 10781 .RE -
trunk/server/docs/manpages/smbcacls.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBCACLS" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBCACLS" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 23 23 .SH "SYNOPSIS" 24 24 .HP \w'\ 'u 25 smbcacls {//server/share} {filename} [\-D \ acls] [\-M\ acls] [\-a\ acls] [\-S\ acls] [\-C\ name] [\-G\ name] [\-\-numeric] [\-t] [\-U\ username] [\-h] [\-d]25 smbcacls {//server/share} {filename} [\-D|\-\-delete\ acls] [\-M|\-\-modify\ acls] [\-a|\-\-add\ acls] [\-S|\-\-set\ acls] [\-C|\-\-chown\ name] [\-G|\-\-chgrp\ name] [\-I\ allow|romove|copy] [\-\-numeric] [\-t] [\-U\ username] [\-h] [\-d] 26 26 .SH "DESCRIPTION" 27 27 .PP … … 75 75 .sp 76 76 This command is a shortcut for \-M GROUP:name\&. 77 .RE 78 .PP 79 \-I|\-\-inherit allow|remove|copy 80 .RS 4 81 Set or unset the windows "Allow inheritable permissions" check box using the 82 \fI\-I\fR 83 option\&. To set the check box pass allow\&. To unset the check box pass either remove or copy\&. Remove will remove all inherited acls\&. Copy will copy all the inherited acls\&. 77 84 .RE 78 85 .PP … … 255 262 .\} 256 263 \fB#define SEC_ACE_FLAG_INHERIT_ONLY 0x8\fR 264 .RE 257 265 .sp 258 266 .RE … … 332 340 \fIO\fR 333 341 \- Take ownership 342 .RE 334 343 .sp 335 344 .RE … … 371 380 \fIFULL\fR 372 381 \- Equivalent to \'RWXDPO\' permissions 382 .RE 373 383 .SH "EXIT STATUS" 374 384 .PP -
trunk/server/docs/manpages/smbclient.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBCLIENT" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBCLIENT" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 133 133 \fIinterfaces\fR 134 134 parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. 135 .RE 135 136 .sp 136 137 .RE … … 191 192 .RE 192 193 .PP 193 \-P 194 \-P|\-\-machine\-pass 194 195 .RS 4 195 196 Make queries to the external server using the machine account of the local server\&. … … 234 235 .RE 235 236 .PP 236 \-e 237 \-e|\-\-encrypt 237 238 .RS 4 238 239 This command line parameter requires the remote server support the UNIX extensions\&. Request that the connection be encrypted\&. This is new for Samba 3\&.2 and will only work with Samba 3\&.2 or above servers\&. Negotiates SMB encryption using GSSAPI\&. Uses the given credentials for the encryption negotiaion (either kerberos or NTLMv1/v2 if given domain/username/password triple\&. Fails the connection if encryption cannot be negotiated\&. … … 522 523 \fIc\fR 523 524 flags\&. 525 .RE 524 526 .sp 525 527 .RE … … 570 572 .RE 571 573 .PP 572 \-c|\-\-com and command string574 \-c|\-\-command command string 573 575 .RS 4 574 576 command string is a semicolon\-separated list of commands to be executed instead of prompting from stdin\&. -
trunk/server/docs/manpages/smbcontrol.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBCONTROL" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBCONTROL" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 236 236 \fBwinbindd\fR\&. 237 237 .RE 238 .PP 239 idmap 240 .RS 4 241 Notify about changes of id mapping\&. Can be sent to 242 \fBsmbd\fR 243 or (not implemented yet) 244 \fBwinbindd\fR\&. 245 .PP 246 flush [uid|gid] 247 .RS 4 248 Flush caches for sid <\-> gid and/or sid <\-> uid mapping\&. 249 .RE 250 .PP 251 delete <ID> 252 .RS 4 253 Remove a mapping from cache\&. The mapping is given by <ID> which may either be a sid: S\-x\-\&.\&.\&., a gid: "GID number" or a uid: "UID number"\&. 254 .RE 255 .PP 256 kill <ID> 257 .RS 4 258 Remove a mapping from cache\&. Terminate 259 \fBsmbd\fR 260 if the id is currently in use\&. 261 .RE 262 .RE 238 263 .SH "VERSION" 239 264 .PP -
trunk/server/docs/manpages/smbcquotas.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBCQUOTAS" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBCQUOTAS" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/smbd.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "SMBD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 223 223 .\} 224 224 \fISession Management\fR: When not using share level secuirty, users must pass PAM\'s session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&. 225 .RE 225 226 .SH "VERSION" 226 227 .PP -
trunk/server/docs/manpages/smbget.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBGET" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBGET" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 98 98 \-f, \-\-rcfile 99 99 .RS 4 100 Use specified rcfile\&. This will be loaded in the order it was specified \- e\&.g\&. if you specify any options before this one, they might get overrid en by the contents of the rcfile\&.100 Use specified rcfile\&. This will be loaded in the order it was specified \- e\&.g\&. if you specify any options before this one, they might get overridden by the contents of the rcfile\&. 101 101 .RE 102 102 .PP -
trunk/server/docs/manpages/smbgetrc.5
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: File Formats and Conventions 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBGETRC" "5" "08/0 2/2011" "Samba 3\&.5" "File Formats and Conventions"10 .TH "SMBGETRC" "5" "08/08/2011" "Samba 3\&.6" "File Formats and Conventions" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/smbpasswd.5
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: File Formats and Conventions 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBPASSWD" "5" "08/0 2/2011" "Samba 3\&.5" "File Formats and Conventions"10 .TH "SMBPASSWD" "5" "08/08/2011" "Samba 3\&.6" "File Formats and Conventions" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 140 140 \fIW\fR 141 141 \- This means this account is a "Workstation Trust" account\&. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC\&. 142 .RE 142 143 .sp 143 144 .RE -
trunk/server/docs/manpages/smbpasswd.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBPASSWD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "SMBPASSWD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 206 206 \fIinterfaces\fR 207 207 parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. 208 .RE 208 209 .sp 209 210 .RE -
trunk/server/docs/manpages/smbspool.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBSPOOL" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "SMBSPOOL" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 78 78 .\} 79 79 smb://username:password@workgroup/server[:port]/printer 80 .RE 80 81 .sp 81 82 .RE … … 159 160 .\} 160 161 The filename argument (argv[6]) contains the name of the file to print\&. If this argument is not specified then the print file is read from the standard input\&. 162 .RE 161 163 .SH "VERSION" 162 164 .PP -
trunk/server/docs/manpages/smbstatus.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBSTATUS" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBSTATUS" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/smbtar.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBTAR" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBTAR" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/smbtree.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMBTREE" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "SMBTREE" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/swat.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SWAT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "SWAT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 153 153 .\} 154 154 /usr/local/samba/swat/help/* 155 .RE 155 156 .sp 156 157 .RE -
trunk/server/docs/manpages/tdbbackup.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "TDBBACKUP" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "TDBBACKUP" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 105 105 *\&.tdb 106 106 located in the /usr/local/samba/var directory or on some systems in the /var/cache or /var/lib/samba directories\&. 107 .RE 107 108 .SH "VERSION" 108 109 .PP -
trunk/server/docs/manpages/tdbdump.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "TDBDUMP" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "TDBDUMP" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/tdbtool.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "TDBTOOL" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "TDBTOOL" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/testparm.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "TESTPARM" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "TESTPARM" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 23 23 .SH "SYNOPSIS" 24 24 .HP \w'\ 'u 25 testparm [\-s] [\-h] [\-v] [\- L\ <servername>] [\-t\ <encoding>] {config\ filename} [hostname\ hostIP]25 testparm [\-s] [\-h] [\-v] [\-t\ <encoding>] {config\ filename} [hostname\ hostIP] 26 26 .SH "DESCRIPTION" 27 27 .PP … … 66 66 .RS 4 67 67 Prints the program version number\&. 68 .RE69 .PP70 \-L servername71 .RS 472 Sets the value of the %L macro to73 \fIservername\fR\&. This is useful for testing include files specified with the %L macro\&.74 68 .RE 75 69 .PP -
trunk/server/docs/manpages/vfs_acl_tdb.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_ACL_TDB" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_ACL_TDB" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_acl_xattr.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_ACL_XATTR" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_ACL_XATTR" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_audit.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_AUDIT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_AUDIT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_cacheprime.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_CACHEPRIME" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_CACHEPRIME" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 81 81 G 82 82 \- BYTES is a number of gigabytes 83 .RE 83 84 .sp 84 85 .RE -
trunk/server/docs/manpages/vfs_cap.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_CAP" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_CAP" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_catia.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_CATIA" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_CATIA" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_commit.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_COMMIT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_COMMIT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 80 80 G 81 81 \- BYTES is a number of gigabytes 82 .RE 82 83 .sp 83 84 .RE -
trunk/server/docs/manpages/vfs_default_quota.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_DEFAULT_QUOTA" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_DEFAULT_QUOTA" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_dirsort.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_DIRSORT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_DIRSORT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_extd_audit.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_EXTD_AUDIT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_EXTD_AUDIT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_fake_perms.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_FAKE_PERMS" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_FAKE_PERMS" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_fileid.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_FILEID" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_FILEID" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_full_audit.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_FULL_AUDIT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_FULL_AUDIT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 386 386 FILE 387 387 \- the name of the file or directory the operation was performed on 388 .RE 388 389 .sp 389 390 .RE … … 400 401 vfs_full_audit:success = LIST 401 402 .RS 4 402 LIST is a list of VFS operations that should be recorded if they succeed\&. Operations are specified using the names listed above\&. 403 LIST is a list of VFS operations that should be recorded if they succeed\&. Operations are specified using the names listed above\&. Operations can be unset by prefixing the names with "!"\&. 403 404 .RE 404 405 .PP 405 406 vfs_full_audit:failure = LIST 406 407 .RS 4 407 LIST is a list of VFS operations that should be recorded if they failed\&. Operations are specified using the names listed above\&. 408 LIST is a list of VFS operations that should be recorded if they failed\&. Operations are specified using the names listed above\&. Operations can be unset by prefixing the names with "!"\&. 408 409 .RE 409 410 .PP … … 423 424 .SH "EXAMPLES" 424 425 .PP 425 Log file and directory open operations on the [records] share using the LOCAL7 facility and ALERT priority, including the username and IP address :426 Log file and directory open operations on the [records] share using the LOCAL7 facility and ALERT priority, including the username and IP address\&. Logging excludes the open VFS function on failures: 426 427 .sp 427 428 .if n \{\ … … 434 435 \m[blue]\fBfull_audit:prefix = %u|%I\fR\m[] 435 436 \m[blue]\fBfull_audit:success = open opendir\fR\m[] 436 \m[blue]\fBfull_audit:failure = all \fR\m[]437 \m[blue]\fBfull_audit:failure = all !open\fR\m[] 437 438 \m[blue]\fBfull_audit:facility = LOCAL7\fR\m[] 438 439 \m[blue]\fBfull_audit:priority = ALERT\fR\m[] -
trunk/server/docs/manpages/vfs_gpfs.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_GPFS" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_GPFS" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 67 67 .\} 68 68 Lease support on GPFS 69 .RE 69 70 .sp 70 71 .RE … … 75 76 .SH "OPTIONS" 76 77 .PP 78 gpfs:sharemodes = [ yes | no ] 79 .RS 4 80 Enable/Disable cross node sharemode handling for GPFS\&. 81 .sp 82 .RS 4 83 .ie n \{\ 84 \h'-04'\(bu\h'+03'\c 85 .\} 86 .el \{\ 87 .sp -1 88 .IP \(bu 2.3 89 .\} 90 91 yes(default) 92 \- propagate sharemodes across all GPFS nodes\&. 93 .RE 94 .sp 95 .RS 4 96 .ie n \{\ 97 \h'-04'\(bu\h'+03'\c 98 .\} 99 .el \{\ 100 .sp -1 101 .IP \(bu 2.3 102 .\} 103 104 no 105 \- do not propagate sharemodes across all GPFS nodes\&. This should only be used if the GPFS file system is exclusively exported by Samba\&. Access by local unix application or NFS exports could lead to corrupted files\&. 106 .RE 107 .sp 108 .RE 109 .RE 110 .PP 111 gpfs:leases = [ yes | no ] 112 .RS 4 113 Enable/Disable cross node leases (oplocks) for GPFS\&. You should also set the 114 oplocks 115 and 116 kernel oplocks 117 options to the same value\&. 118 .sp 119 .RS 4 120 .ie n \{\ 121 \h'-04'\(bu\h'+03'\c 122 .\} 123 .el \{\ 124 .sp -1 125 .IP \(bu 2.3 126 .\} 127 128 yes(default) 129 \- propagate leases across all GPFS nodes\&. 130 .RE 131 .sp 132 .RS 4 133 .ie n \{\ 134 \h'-04'\(bu\h'+03'\c 135 .\} 136 .el \{\ 137 .sp -1 138 .IP \(bu 2.3 139 .\} 140 141 no 142 \- do not propagate leases across all GPFS nodes\&. This should only be used if the GPFS file system is exclusively exported by Samba\&. Access by local unix application or NFS exports could lead to corrupted files\&. 143 .RE 144 .sp 145 .RE 146 .RE 147 .PP 148 gpfs:hsm = [ yes | no ] 149 .RS 4 150 Enable/Disable announcing if this FS has HSM enabled\&. 151 .sp 152 .RS 4 153 .ie n \{\ 154 \h'-04'\(bu\h'+03'\c 155 .\} 156 .el \{\ 157 .sp -1 158 .IP \(bu 2.3 159 .\} 160 161 no(default) 162 \- Do not announce HSM\&. 163 .RE 164 .sp 165 .RS 4 166 .ie n \{\ 167 \h'-04'\(bu\h'+03'\c 168 .\} 169 .el \{\ 170 .sp -1 171 .IP \(bu 2.3 172 .\} 173 174 no 175 \- Announce HSM\&. 176 .RE 177 .sp 178 .RE 179 .RE 180 .PP 181 gpfs:getrealfilename = [ yes | no ] 182 .RS 4 183 Enable/Disable usage of the 184 gpfs_get_realfilename_path() 185 function\&. This improves the casesensitive wildcard file name access\&. 186 .sp 187 .RS 4 188 .ie n \{\ 189 \h'-04'\(bu\h'+03'\c 190 .\} 191 .el \{\ 192 .sp -1 193 .IP \(bu 2.3 194 .\} 195 196 yes(default) 197 \- use 198 gpfs_get_realfilename_path()\&. 199 .RE 200 .sp 201 .RS 4 202 .ie n \{\ 203 \h'-04'\(bu\h'+03'\c 204 .\} 205 .el \{\ 206 .sp -1 207 .IP \(bu 2.3 208 .\} 209 210 no 211 \- do not use 212 gpfs_get_realfilename_path()\&. It seems that 213 gpfs_get_realfilename_path() 214 doesn\'t work on AIX\&. 215 .RE 216 .sp 217 .RE 218 .RE 219 .PP 220 gpfs:winattr = [ yes | no ] 221 .RS 4 222 Enable/Disable usage of the windows attributes in GPFS\&. GPFS is able to store windows file attributes e\&.g\&. HIDDEN, READONLY, SYSTEM and others natively\&. That means Samba doesn\'t need to map them to permission bits or extended attributes\&. 223 .sp 224 .RS 4 225 .ie n \{\ 226 \h'-04'\(bu\h'+03'\c 227 .\} 228 .el \{\ 229 .sp -1 230 .IP \(bu 2.3 231 .\} 232 233 no(default) 234 \- do not use GPFS windows attributes\&. 235 .RE 236 .sp 237 .RS 4 238 .ie n \{\ 239 \h'-04'\(bu\h'+03'\c 240 .\} 241 .el \{\ 242 .sp -1 243 .IP \(bu 2.3 244 .\} 245 246 yes 247 \- use GPFS windows attributes\&. 248 .RE 249 .sp 250 .RE 251 .RE 252 .PP 253 gpfs:merge_writeappend = [ yes | no ] 254 .RS 4 255 GPFS ACLs doesn\'t know about the \'APPEND\' right\&. This optionen lets Samba map the \'APPEND\' right to \'WRITE\'\&. 256 .sp 257 .RS 4 258 .ie n \{\ 259 \h'-04'\(bu\h'+03'\c 260 .\} 261 .el \{\ 262 .sp -1 263 .IP \(bu 2.3 264 .\} 265 266 yes(default) 267 \- map \'APPEND\' to \'WRITE\'\&. 268 .RE 269 .sp 270 .RS 4 271 .ie n \{\ 272 \h'-04'\(bu\h'+03'\c 273 .\} 274 .el \{\ 275 .sp -1 276 .IP \(bu 2.3 277 .\} 278 279 no 280 \- do not map \'APPEND\' to \'WRITE\'\&. 281 .RE 282 .sp 283 .RE 284 .RE 285 .PP 286 gpfs:refuse_dacl_protected = [ yes | no ] 287 .RS 4 288 As GPFS does not support the ACE4_FLAG_NO_PROPAGATE NFSv4 flag (which would be the mapping for the DESC_DACL_PROTECTED flag), the status of this flag is currently silently ignored by Samba\&. That means that if you deselect the "Allow inheritable permissions\&.\&.\&." checkbox in Windows\' ACL dialog and then apply the ACL, the flag will be back immediately\&. 289 .sp 290 To make sure that automatic migration with e\&.g\&. robocopy does not lead to ACLs silently (and unintentionally) changed, you can set 291 gpfs:refuse_dacl_protected = yes 292 to enable an explicit check for this flag and if set, it will return NT_STATUS_NOT_SUPPORTED so errors are shown up on the Windows side and the Administrator is aware of the ACLs not being settable like intended 293 .sp 294 .RS 4 295 .ie n \{\ 296 \h'-04'\(bu\h'+03'\c 297 .\} 298 .el \{\ 299 .sp -1 300 .IP \(bu 2.3 301 .\} 302 303 no(default) 304 \- ignore the DESC_DACL_PROTECTED flags\&. 305 .RE 306 .sp 307 .RS 4 308 .ie n \{\ 309 \h'-04'\(bu\h'+03'\c 310 .\} 311 .el \{\ 312 .sp -1 313 .IP \(bu 2.3 314 .\} 315 316 yes 317 \- reject ACLs with DESC_DACL_PROTECTED\&. 318 .RE 319 .sp 320 .RE 321 .RE 322 .PP 77 323 nfs4:mode = [ simple | special ] 78 324 .RS 4 … … 103 349 special 104 350 \- use special IDs in GPFS ACEs\&. 351 .RE 105 352 .sp 106 353 .RE … … 159 406 merge 160 407 \- bitwise OR the 2 ace\&.flag fields and 2 ace\&.mask fields of the 2 duplicate ACEs into 1 ACE 408 .RE 161 409 .sp 162 410 .RE … … 193 441 no (default) 194 442 \- Disable chown 443 .RE 444 .sp 445 .RE 446 .RE 447 .PP 448 gpfs:syncio = [yes|no] 449 .RS 4 450 This parameter makes Samba open all files with O_SYNC\&. This triggers optimizations in GPFS for workloads that heavily share files\&. 451 .sp 452 Following is the behaviour of Samba for different values: 453 .sp 454 .RS 4 455 .ie n \{\ 456 \h'-04'\(bu\h'+03'\c 457 .\} 458 .el \{\ 459 .sp -1 460 .IP \(bu 2.3 461 .\} 462 yesOpen files with O_SYNC 463 .RE 464 .sp 465 .RS 4 466 .ie n \{\ 467 \h'-04'\(bu\h'+03'\c 468 .\} 469 .el \{\ 470 .sp -1 471 .IP \(bu 2.3 472 .\} 473 no (default)Open files as normal Samba would do 474 .RE 195 475 .sp 196 476 .RE … … 215 495 .SH "CAVEATS" 216 496 .PP 217 The gpfs gpl libraries are required by 497 Depending on the version of gpfs, the 498 libgpfs_gpl 499 library or the 500 libgpfs 501 library is needed at runtime by the 218 502 gpfs 219 VFS module during both compilation and runtime\&. Also this VFS module is tested to work on SLES 9/10 and RHEL 4\&.4 503 VFS module: Starting with gpfs 3\&.2\&.1 PTF8, the complete 504 libgpfs 505 is available as open source and 506 libgpfs_gpl 507 does no longer exist\&. With earlier versions of gpfs, only the 508 libgpfs_gpl 509 library was open source and could be used at run time\&. 510 .PP 511 At build time, only the header file 512 gpfs_gpl\&.h 513 is required , which is a symlink to 514 gpfs\&.h 515 in gpfs versions newer than 3\&.2\&.1 PTF8\&. 220 516 .SH "VERSION" 221 517 .PP -
trunk/server/docs/manpages/vfs_netatalk.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_NETATALK" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_NETATALK" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_notify_fam.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_NOTIFY_FAM" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_NOTIFY_FAM" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_prealloc.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_PREALLOC" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_PREALLOC" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 77 77 G 78 78 \- BYTES is a number of gigabytes 79 .RE 79 80 .sp 80 81 .RE -
trunk/server/docs/manpages/vfs_preopen.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_PREOPEN" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_PREOPEN" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_readahead.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_READAHEAD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_READAHEAD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 91 91 G 92 92 \- BYTES is a number of gigabytes 93 .RE 93 94 .SH "EXAMPLES" 94 95 .sp -
trunk/server/docs/manpages/vfs_readonly.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_READONLY" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_READONLY" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_recycle.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_RECYCLE" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_RECYCLE" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_scannedonly.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_SCANNEDONLY" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_SCANNEDONLY" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 150 150 .SH "VERSION" 151 151 .PP 152 This man page is correct for version 3\&. 5\&.0 of the Samba suite\&.152 This man page is correct for version 3\&.6\&.0 of the Samba suite\&. 153 153 .SH "AUTHOR" 154 154 .PP -
trunk/server/docs/manpages/vfs_shadow_copy.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_SHADOW_COPY" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_SHADOW_COPY" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 115 115 ss 116 116 is the 2 digit second\&. 117 .RE 117 118 .sp 118 119 .RE -
trunk/server/docs/manpages/vfs_shadow_copy2.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_SHADOW_COPY2" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_SHADOW_COPY2" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 141 141 ss 142 142 is the 2 digit second\&. 143 .RE 143 144 .sp 144 145 .RE … … 170 171 .RS 4 171 172 Path to the base directory that snapshots are from\&. 173 .RE 174 .PP 175 shadow:sort = asc/desc, or not specified for unsorted (default) 176 .RS 4 177 By this parameter one can specify that the shadow copy directories should be sorted before they are sent to the client\&. This can be beneficial as unix filesystems are usually not listed alphabetically sorted\&. If enabled, you typically want to specify descending order\&. 178 .RE 179 .PP 180 shadow:localtime = yes/no 181 .RS 4 182 This is an optional parameter that indicates whether the snapshot names are in UTC/GMT or in local time\&. By default UTC is expected\&. 183 .RE 184 .PP 185 shadow:format = format specification for snapshot names 186 .RS 4 187 This is an optional parameter that specifies the format specification for the naming of snapshots\&. The format must be compatible with the conversion specifications recognized by str[fp]time\&. The default value is "@GMT\-%Y\&.%m\&.%d\-%H\&.%M\&.%S"\&. 172 188 .RE 173 189 .PP … … 190 206 \m[blue]\fBshadow:snapdir = /data/snaphots\fR\m[] 191 207 \m[blue]\fBshadow:basedir = /data/home\fR\m[] 208 \m[blue]\fBshadow:sort = desc\fR\m[] 192 209 .fi 193 210 .if n \{\ -
trunk/server/docs/manpages/vfs_smb_traffic_analyzer.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMB_TRAFFIC_ANALYZER" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "SMB_TRAFFIC_ANALYZER" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 32 32 The 33 33 vfs_smb_traffic_analyzer 34 VFS module logs client write and read operations on a Samba server and sends this data over a socket to a helper program, which feeds a SQL database\&. More information on the helper programs can be obtained from the homepage of the project at: http://holger123\&.wordpress\&.com/smb\-traffic\-analyzer/ 34 VFS module logs client file operations on a Samba server and sends this data over a socket to a helper program (in the following the "Receiver"), which feeds a SQL database\&. More information on the helper programs can be obtained from the homepage of the project at: http://holger123\&.wordpress\&.com/smb\-traffic\-analyzer/ Since the VFS module depends on a receiver that is doing something with the data, it is evolving in it\'s development\&. Therefore, the module works with different protocol versions, and the receiver has to be able to decode the protocol that is used\&. The protocol version 1 was introduced to Samba at September 25, 2008\&. It was a very simple protocol, supporting only a small list of VFS operations, and had several drawbacks\&. The protocol version 2 is a try to solve the problems version 1 had while at the same time adding new features\&. With the release of Samba 3\&.6\&.0, the module will run protocol version 2 by default\&. 35 .SH "PROTOCOL VERSION 1 DOCUMENTATION" 35 36 .PP 36 37 vfs_smb_traffic_analyzer 37 currentlyis aware of the following VFS operations:38 protocol version 1 is aware of the following VFS operations: 38 39 .RS 4 39 40 write … … 147 148 TIMESTAMP 148 149 \- a timestamp, formatted as "yyyy\-mm\-dd hh\-mm\-ss\&.ms" indicating when the VFS operation occured 150 .RE 151 .sp 152 .RS 4 153 .ie n \{\ 154 \h'-04'\(bu\h'+03'\c 155 .\} 156 .el \{\ 157 .sp -1 158 .IP \(bu 2.3 159 .\} 160 IP 161 \- The IP Address (v4 or v6) of the client machine that initiated the VFS operation\&. 162 .RE 149 163 .sp 150 164 .RE 151 165 .PP 152 166 This module is stackable\&. 153 .SH "OPTIONS" 167 .SH "DRAWBACKS OF PROTOCOL VERSION 1" 168 .PP 169 Several drawbacks have been seen with protocol version 1 over time\&. 170 .sp 171 .RS 4 172 .ie n \{\ 173 \h'-04'\(bu\h'+03'\c 174 .\} 175 .el \{\ 176 .sp -1 177 .IP \(bu 2.3 178 .\} 179 180 Problematic parsing \- 181 Protocol version 1 uses hyphen and comma to seperate blocks of data\&. Once there is a filename with a hyphen, you will run into problems because the receiver decodes the data in a wrong way\&. 182 .RE 183 .sp 184 .RS 4 185 .ie n \{\ 186 \h'-04'\(bu\h'+03'\c 187 .\} 188 .el \{\ 189 .sp -1 190 .IP \(bu 2.3 191 .\} 192 193 Insecure network transfer \- 194 Protocol version 1 sends all it\'s data as plaintext over the network\&. 195 .RE 196 .sp 197 .RS 4 198 .ie n \{\ 199 \h'-04'\(bu\h'+03'\c 200 .\} 201 .el \{\ 202 .sp -1 203 .IP \(bu 2.3 204 .\} 205 206 Limited set of supported VFS operations \- 207 Protocol version 1 supports only four VFS operations\&. 208 .RE 209 .sp 210 .RS 4 211 .ie n \{\ 212 \h'-04'\(bu\h'+03'\c 213 .\} 214 .el \{\ 215 .sp -1 216 .IP \(bu 2.3 217 .\} 218 219 No subreleases of the protocol \- 220 Protocol version 1 is fixed on it\'s version, making it unable to introduce new features or bugfixes through compatible sub\-releases\&. 221 .RE 222 .SH "VERSION 2 OF THE PROTOCOL" 223 .PP 224 Protocol version 2 is an approach to solve the problems introduced with protcol v1\&. From the users perspective, the following changes are most prominent among other enhancements: 225 .sp 226 .RS 4 227 .ie n \{\ 228 \h'-04'\(bu\h'+03'\c 229 .\} 230 .el \{\ 231 .sp -1 232 .IP \(bu 2.3 233 .\} 234 The data from the module may be send encrypted, with a key stored in secrets\&.tdb\&. The Receiver then has to use the same key\&. The module does AES block encryption over the data to send\&. 235 .RE 236 .sp 237 .RS 4 238 .ie n \{\ 239 \h'-04'\(bu\h'+03'\c 240 .\} 241 .el \{\ 242 .sp -1 243 .IP \(bu 2.3 244 .\} 245 The module now can identify itself against the receiver with a sub\-release number, where the receiver may run with a different sub\-release number than the module\&. However, as long as both run on the V2\&.x protocol, the receiver will not crash, even if the module uses features only implemented in the newer subrelease\&. If the module uses a new feature from a newer subrelease, and the receiver runs an older protocol, it is just ignoring the functionality\&. Of course it is best to have both the receiver and the module running the same subrelease of the protocol\&. 246 .RE 247 .sp 248 .RS 4 249 .ie n \{\ 250 \h'-04'\(bu\h'+03'\c 251 .\} 252 .el \{\ 253 .sp -1 254 .IP \(bu 2.3 255 .\} 256 The parsing problems of protocol V1 can no longer happen, because V2 is marshalling the data packages in a proper way\&. 257 .RE 258 .sp 259 .RS 4 260 .ie n \{\ 261 \h'-04'\(bu\h'+03'\c 262 .\} 263 .el \{\ 264 .sp -1 265 .IP \(bu 2.3 266 .\} 267 The module now potientially has the ability to create data on every VFS function\&. As of protocol V2\&.0, there is support for 8 VFS functions, namely write,read,pread,pwrite, rename,chdir,mkdir and rmdir\&. Supporting more VFS functions is one of the targets for the upcoming sub\-releases\&. 268 .RE 269 .sp 270 .RE 271 .PP 272 To enable protocol V2, the protocol_version vfs option has to be used (see OPTIONS)\&. 273 .SH "OPTIONS WITH PROTOCOL V1 AND V2.X" 154 274 .PP 155 275 smb_traffic_analyzer:mode = STRING … … 170 290 smb_traffic_analyzer:anonymize_prefix = STRING 171 291 .RS 4 172 The module will replace the user names with a prefix given by STRING and a simple hash number\&. 292 The module will replace the user names with a prefix given by STRING and a simple hash number\&. In version 2\&.x of the protocol, the users SID will also be anonymized\&. 173 293 .RE 174 294 .PP 175 295 smb_traffic_analyzer:total_anonymization = STRING 176 296 .RS 4 177 If STRING matches to \'yes\', the module will replace any user name with the string given by the option smb_traffic_analyzer:anonymize_prefix, without generating an additional hash number\&. This means that any transfer data will be mapped to a single user, leading to a total anonymization of user related data\&. 297 If STRING matches to \'yes\', the module will replace any user name with the string given by the option smb_traffic_analyzer:anonymize_prefix, without generating an additional hash number\&. This means that any transfer data will be mapped to a single user, leading to a total anonymization of user related data\&. In version 2\&.x of the protocol, the users SID will also be anonymized\&. 298 .RE 299 .PP 300 smb_traffic_analyzer:protocol_version = STRING 301 .RS 4 302 If STRING matches to V1, the module will use version 1 of the protocol\&. If STRING is not given, the module will use version 2 of the protocol, which is the default\&. 178 303 .RE 179 304 .SH "EXAMPLES" 305 .PP 306 Running protocol V2 on share "example_share", using an internet socket\&. 307 .sp 308 .if n \{\ 309 .RS 4 310 .\} 311 .nf 312 \fI[example_share]\fR 313 \m[blue]\fBpath = /data/example\fR\m[] 314 \m[blue]\fBvfs_objects = smb_traffic_analyzer\fR\m[] 315 \m[blue]\fBsmb_traffic_analyzer:host = examplehost\fR\m[] 316 \m[blue]\fBsmb_traffic_analyzer:port = 3491\fR\m[] 317 318 .fi 319 .if n \{\ 320 .RE 321 .\} 180 322 .PP 181 323 The module running on share "example_share", using a unix domain socket -
trunk/server/docs/manpages/vfs_streams_depot.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_STREAMS_DEPOT" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_STREAMS_DEPOT" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_streams_xattr.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_STREAMS_XATTR" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_STREAMS_XATTR" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfs_xattr_tdb.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_XATTR_TDB" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "VFS_XATTR_TDB" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/vfstest.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFSTEST" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "VFSTEST" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 519 519 realpath 520 520 \- VFS realpath() 521 .RE 521 522 .sp 522 523 .RE … … 582 583 exit 583 584 \- Exit vfstest 585 .RE 584 586 .SH "VERSION" 585 587 .PP -
trunk/server/docs/manpages/wbinfo.1
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: User Commands 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "WBINFO" "1" "08/0 2/2011" "Samba 3\&.5" "User Commands"10 .TH "WBINFO" "1" "08/08/2011" "Samba 3\&.6" "User Commands" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 23 23 .SH "SYNOPSIS" 24 24 .HP \w'\ 'u 25 wbinfo [\-a\ user%password] [\-\-all\-domains] [\-\-allocate\-gid] [\-\-allocate\-uid] [\-c] [\-\-ccache\-save] [\-\-change\-user\-password] [\-D\ domain] [\-\-domain\ domain] [\-\-dsgetdcname\ domain] [\-g] [\-\-getdcname\ domain] [\-\-get\-auth\-user] [\-G\ gid] [\-\-gid\-info] [\-\-group\-info] [\-\-help|\-?] [\-i\ user] [\-I\ ip] [\-K\ user%password] [\-\-lanman] [\-m] [\-n\ name] [\-N\ netbios\-name] [\-\-ntlmv2] [\-\-online\-status] [\-\-own\-domain] [\-p] [\-P|\-\-ping\-dc] [\-r\ user] [\-R|\-\-lookup\-rids] [\- \-remove\-uid\-mapping\ uid,sid] [\-\-remove\-gid\-mapping\ gid,sid] [\-s\ sid] [\-\-separator] [\-\-sequence] [\-\-set\-auth\-user\ user%password] [\-\-set\-uid\-mapping\ uid,sid] [\-\-set\-gid\-mapping\ gid,sid] [\-S\ sid] [\-\-sid\-aliases] [\-\-sid\-to\-fullname] [\-t] [\-u] [\-\-uid\-info\ uid] [\-\-usage] [\-\-user\-domgroups\ sid] [\-\-user\-sids\ sid] [\-U\ uid] [\-V] [\-\-verbose] [\-Y\ sid]25 wbinfo [\-a\ user%password] [\-\-all\-domains] [\-\-allocate\-gid] [\-\-allocate\-uid] [\-c] [\-\-ccache\-save] [\-\-change\-user\-password] [\-D\ domain] [\-\-domain\ domain] [\-\-dsgetdcname\ domain] [\-g] [\-\-getdcname\ domain] [\-\-get\-auth\-user] [\-G\ gid] [\-\-gid\-info] [\-\-group\-info] [\-\-help|\-?] [\-i\ user] [\-I\ ip] [\-K\ user%password] [\-\-lanman] [\-m] [\-n\ name] [\-N\ netbios\-name] [\-\-ntlmv2] [\-\-online\-status] [\-\-own\-domain] [\-p] [\-P|\-\-ping\-dc] [\-r\ user] [\-R|\-\-lookup\-rids] [\-s\ sid] [\-\-separator] [\-\-set\-auth\-user\ user%password] [\-S\ sid] [\-\-sid\-aliases] [\-\-sid\-to\-fullname] [\-t] [\-u] [\-\-uid\-info\ uid] [\-\-usage] [\-\-user\-domgroups\ sid] [\-\-user\-sids\ sid] [\-U\ uid] [\-V] [\-\-verbose] [\-Y\ sid] 26 26 .SH "DESCRIPTION" 27 27 .PP … … 102 102 \fBwinbindd\fR(8) 103 103 belongs\&. Currently only the 104 \fB\-\-sequence\fR,105 104 \fB\-u\fR, and 106 105 \fB\-g\fR … … 235 234 \fBwinbindd\fR(8) 236 235 is still alive\&. Prints out either \'succeeded\' or \'failed\'\&. 236 .RE 237 .PP 238 \-P|\-\-ping\-dc 239 .RS 4 240 Issue a no\-effect command to our DC\&. This checks if our secure channel connection to our domain controller is still alive\&. It has much less impact than wbinfo \-t\&. 237 241 .RE 238 242 .PP … … 261 265 .RE 262 266 .PP 263 \-\-sequence264 .RS 4265 Show sequence numbers of all known domains\&.266 .RE267 .PP268 267 \-\-set\-auth\-user \fIusername%password\fR 269 268 .RS 4 … … 328 327 \-U|\-\-uid\-to\-sid \fIuid\fR 329 328 .RS 4 330 Try to convert a UNIX user id to a Windows NT SID\&. If the uid specified does not refer to one within the idmap uidrange then the operation will fail\&.329 Try to convert a UNIX user id to a Windows NT SID\&. If the uid specified does not refer to one within the idmap range then the operation will fail\&. 331 330 .RE 332 331 .PP … … 341 340 \fBwinbindd\fR(8) 342 341 then the operation will fail\&. 343 .RE344 .PP345 \-\-remove\-uid\-mapping uid,sid346 .RS 4347 Remove an existing uid to sid mapping entry from the IDmap backend\&.348 .RE349 .PP350 \-\-remove\-gid\-mapping gid,sid351 .RS 4352 Remove an existing gid to sid mapping entry from the IDmap backend\&.353 .RE354 .PP355 \-\-set\-uid\-mapping uid,sid356 .RS 4357 Create a new or modify an existing uid to sid mapping in the IDmap backend\&.358 .RE359 .PP360 \-\-set\-gid\-mapping gid,sid361 .RS 4362 Create a new or modify an existing gid to sid mapping in the IDmap backend\&.363 342 .RE 364 343 .PP -
trunk/server/docs/manpages/winbind_krb5_locator.7
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: 7 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "WINBIND_KRB5_LOCATOR" "7" "08/0 2/2011" "Samba 3\&.5" "7"10 .TH "WINBIND_KRB5_LOCATOR" "7" "08/08/2011" "Samba 3\&.6" "7" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting -
trunk/server/docs/manpages/winbindd.8
r620 r745 3 3 .\" Author: [see the "AUTHOR" section] 4 4 .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> 5 .\" Date: 08/0 2/20115 .\" Date: 08/08/2011 6 6 .\" Manual: System Administration tools 7 .\" Source: Samba 3. 57 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "WINBINDD" "8" "08/0 2/2011" "Samba 3\&.5" "System Administration tools"10 .TH "WINBINDD" "8" "08/08/2011" "Samba 3\&.6" "System Administration tools" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * set default formatting … … 40 40 and the 41 41 pam_winbind\&.so 42 PAM module, by managing connections to domain controllers\&. In this configuraiton the 43 \m[blue]\fBidmap uid\fR\m[] 44 and 45 \m[blue]\fBidmap gid\fR\m[] 46 parameters are not required\&. (This is known as `netlogon proxy only mode\'\&.) 42 PAM module, by managing connections to domain controllers\&. In this configuration the 43 \m[blue]\fBidmap config * : range\fR\m[] 44 parameter is not required\&. (This is known as `netlogon proxy only mode\'\&.) 47 45 .PP 48 46 The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS\&. The exact behaviour can be configured through the … … 266 264 .\} 267 265 268 \m[blue]\fBidmap uid\fR\m[] 269 .RE 270 .sp 271 .RS 4 272 .ie n \{\ 273 \h'-04'\(bu\h'+03'\c 274 .\} 275 .el \{\ 276 .sp -1 277 .IP \(bu 2.3 278 .\} 279 280 \m[blue]\fBidmap gid\fR\m[] 281 .RE 282 .sp 283 .RS 4 284 .ie n \{\ 285 \h'-04'\(bu\h'+03'\c 286 .\} 287 .el \{\ 288 .sp -1 289 .IP \(bu 2.3 290 .\} 291 292 \m[blue]\fBidmap backend\fR\m[] 266 \m[blue]\fBidmap config * : range\fR\m[] 267 .RE 268 .sp 269 .RS 4 270 .ie n \{\ 271 \h'-04'\(bu\h'+03'\c 272 .\} 273 .el \{\ 274 .sp -1 275 .IP \(bu 2.3 276 .\} 277 278 \m[blue]\fBidmap config * : backend\fR\m[] 293 279 .RE 294 280 .sp … … 376 362 \m[blue]\fBwinbind: rpc only\fR\m[] 377 363 Setting this parameter forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers\&. 364 .RE 378 365 .SH "EXAMPLE SETUP" 379 366 .PP … … 478 465 template shell = /bin/bash 479 466 template homedir = /home/%D/%U 480 idmap uid = 10000\-20000 481 idmap gid = 10000\-20000 467 idmap config * : range = 10000\-20000 482 468 workgroup = DOMAIN 483 469 security = domain … … 507 493 If more than one UNIX machine is running 508 494 winbindd, then in general the user and groups ids allocated by winbindd will not be the same\&. The user and group ids will only be valid for the local machine, unless a shared 509 \m[blue]\fBidmap backend\fR\m[]495 \m[blue]\fBidmap config * : backend\fR\m[] 510 496 is configured\&. 511 497 .PP
Note:
See TracChangeset
for help on using the changeset viewer.