Changeset 860 for vendor/current/docs/manpages/smb.conf.5
- Timestamp:
- May 12, 2014, 8:58:38 PM (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs/manpages/smb.conf.5
r746 r860 2 2 .\" Title: smb.conf 3 3 .\" Author: [see the "AUTHOR" section] 4 .\" Generator: DocBook XSL Stylesheets v1.7 5.2<http://docbook.sf.net/>5 .\" Date: 10/29/20124 .\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/> 5 .\" Date: 09/18/2013 6 6 .\" Manual: File Formats and Conventions 7 7 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "SMB\&.CONF" "5" "10/29/2012" "Samba 3\&.6" "File Formats and Conventions" 10 .TH "SMB\&.CONF" "5" "09/18/2013" "Samba 3\&.6" "File Formats and Conventions" 11 .\" ----------------------------------------------------------------- 12 .\" * Define some portability stuff 13 .\" ----------------------------------------------------------------- 14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 15 .\" http://bugs.debian.org/507673 16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html 17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 18 .ie \n(.g .ds Aq \(aq 19 .el .ds Aq ' 11 20 .\" ----------------------------------------------------------------- 12 21 .\" * set default formatting … … 148 157 .IP \(bu 2.3 149 158 .\} 150 If no path was given, the path is set to the user\ 's home directory\&.159 If no path was given, the path is set to the user\*(Aqs home directory\&. 151 160 .RE 152 161 .sp … … 200 209 This section works like [homes], but for printers\&. 201 210 .PP 202 If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host\ 's printcap file\&.211 If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host\*(Aqs printcap file\&. 203 212 .PP 204 213 When a connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, but a [homes] section exists, it is used as described above\&. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name\&. If a match is found, a new printer share is created by cloning the [printers] section\&. … … 258 267 .\} 259 268 .PP 260 All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned\&. If your printing subsystem doesn\ 't work like that, you will have to set up a pseudo\-printcap\&. This is a file consisting of one or more lines like this:269 All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned\&. If your printing subsystem doesn\*(Aqt work like that, you will have to set up a pseudo\-printcap\&. This is a file consisting of one or more lines like this: 261 270 .sp 262 271 .if n \{\ … … 533 542 %p 534 543 .RS 4 535 the path of the service\ 's home directory, obtained from your NIS auto\&.map entry\&. The NIS auto\&.map entry is split up as544 the path of the service\*(Aqs home directory, obtained from your NIS auto\&.map entry\&. The NIS auto\&.map entry is split up as 536 545 %N:%p\&. 537 546 .RE … … 544 553 Samba supports 545 554 name mangling 546 so that DOS and Windows clients can use files that don\ 't conform to the 8\&.3 format\&. It can also be set to adjust the case of 8\&.3 format filenames\&.555 so that DOS and Windows clients can use files that don\*(Aqt conform to the 8\&.3 format\&. It can also be set to adjust the case of 8\&.3 format filenames\&. 547 556 .PP 548 557 There are several options that control the way mangling is performed, and they are grouped here rather than listed separately\&. For the defaults look at the output of the testparm program\&. … … 554 563 case sensitive = yes/no/auto 555 564 .RS 4 556 controls whether filenames are case sensitive\&. If they aren\ 't, Samba must do a filename search and match on passed names\&. The default setting of auto allows clients that support case sensitive filenames (Linux CIFSVFS and smbclient 3\&.0\&.5 and above currently) to tell the Samba server on a per\-packet basis that they wish to access the file system in a case\-sensitive manner (to support UNIX case sensitive semantics)\&. No Windows or DOS system supports case\-sensitive filename so setting this option to auto is that same as setting it to no for them\&. Default565 controls whether filenames are case sensitive\&. If they aren\*(Aqt, Samba must do a filename search and match on passed names\&. The default setting of auto allows clients that support case sensitive filenames (Linux CIFSVFS and smbclient 3\&.0\&.5 and above currently) to tell the Samba server on a per\-packet basis that they wish to access the file system in a case\-sensitive manner (to support UNIX case sensitive semantics)\&. No Windows or DOS system supports case\-sensitive filename so setting this option to auto is that same as setting it to no for them\&. Default 557 566 \fIauto\fR\&. 558 567 .RE … … 560 569 default case = upper/lower 561 570 .RS 4 562 controls what the default case is for new filenames (ie\&. files that don\ 't currently exist in the filesystem)\&. Default571 controls what the default case is for new filenames (ie\&. files that don\*(Aqt currently exist in the filesystem)\&. Default 563 572 \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 573 \m[blue]\fBcase sensitive = yes\fR\m[], … … 572 581 preserve case = yes/no 573 582 .RS 4 574 controls whether new files (ie\&. files that don\ 't currently exist in the filesystem) are created with the case that the client passes, or if they are forced to be the583 controls whether new files (ie\&. files that don\*(Aqt currently exist in the filesystem) are created with the case that the client passes, or if they are forced to be the 575 584 default 576 585 case\&. Default … … 580 589 short preserve case = yes/no 581 590 .RS 4 582 controls if new files (ie\&. files that don\ 't currently exist in the filesystem) which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the591 controls if new files (ie\&. files that don\*(Aqt currently exist in the filesystem) which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the 583 592 default 584 593 case\&. This option can be used with … … 605 614 .IP " 1." 4.2 606 615 .\} 607 If the client has passed a username/password pair and that username/password pair is validated by the UNIX system\ 's password programs, the connection is made as that username\&. This includes the616 If the client has passed a username/password pair and that username/password pair is validated by the UNIX system\*(Aqs password programs, the connection is made as that username\&. This includes the 608 617 \e\eserver\eservice%\fIusername\fR 609 618 method of passing a username\&. … … 629 638 .IP " 3." 4.2 630 639 .\} 631 The client\ 's NetBIOS name and any previously used usernames are checked against the supplied password\&. If they match, the connection is allowed as the corresponding user\&.640 The client\*(Aqs NetBIOS name and any previously used usernames are checked against the supplied password\&. If they match, the connection is allowed as the corresponding user\&. 632 641 .RE 633 642 .sp … … 655 664 field is given in the 656 665 smb\&.conf 657 file for the service and the client has supplied a password, and that password matches (according to the UNIX system\ 's password checking) with one of the usernames from the666 file for the service and the client has supplied a password, and that password matches (according to the UNIX system\*(Aqs password checking) with one of the usernames from the 658 667 user = 659 668 field, the connection is made as the username in the … … 787 796 .RS 4 788 797 This boolean parameter controls what 789 \fBsmbd\fR(8)does on receiving a protocol request of "open for delete" from a Windows client\&. If a Windows client doesn\ 't have permissions to delete a file then they expect this to be denied at open time\&. POSIX systems normally only detect restrictions on delete by actually attempting to delete the file or directory\&. As Windows clients can (and do) "back out" a delete request by unsetting the "delete on close" bit Samba cannot delete the file immediately on "open for delete" request as we cannot restore such a deleted file\&. With this parameter set to true (the default) then smbd checks the file system permissions directly on "open for delete" and denies the request without actually deleting the file if the file system permissions would seem to deny it\&. This is not perfect, as it\'s possible a user could have deleted a file without Samba being able to check the permissions correctly, but it is close enough to Windows semantics for mostly correct behaviour\&. Samba will correctly check POSIX ACL semantics in this case\&.790 .sp 791 If this parameter is set to "false" Samba doesn\ 't check permissions on "open for delete" and allows the open\&. If the user doesn\'t have permission to delete the file this will only be discovered at close time, which is too late for the Windows user tools to display an error message to the user\&. The symptom of this is files that appear to have been deleted "magically" re\-appearing on a Windows explorer refresh\&. This is an extremely advanced protocol option which should not need to be changed\&. This parameter was introduced in its final form in 3\&.0\&.21, an earlier version with slightly different semantics was introduced in 3\&.0\&.20\&. That older version is not documented here\&.798 \fBsmbd\fR(8)does on receiving a protocol request of "open for delete" from a Windows client\&. If a Windows client doesn\*(Aqt have permissions to delete a file then they expect this to be denied at open time\&. POSIX systems normally only detect restrictions on delete by actually attempting to delete the file or directory\&. As Windows clients can (and do) "back out" a delete request by unsetting the "delete on close" bit Samba cannot delete the file immediately on "open for delete" request as we cannot restore such a deleted file\&. With this parameter set to true (the default) then smbd checks the file system permissions directly on "open for delete" and denies the request without actually deleting the file if the file system permissions would seem to deny it\&. This is not perfect, as it\*(Aqs possible a user could have deleted a file without Samba being able to check the permissions correctly, but it is close enough to Windows semantics for mostly correct behaviour\&. Samba will correctly check POSIX ACL semantics in this case\&. 799 .sp 800 If this parameter is set to "false" Samba doesn\*(Aqt check permissions on "open for delete" and allows the open\&. If the user doesn\*(Aqt have permission to delete the file this will only be discovered at close time, which is too late for the Windows user tools to display an error message to the user\&. The symptom of this is files that appear to have been deleted "magically" re\-appearing on a Windows explorer refresh\&. This is an extremely advanced protocol option which should not need to be changed\&. This parameter was introduced in its final form in 3\&.0\&.21, an earlier version with slightly different semantics was introduced in 3\&.0\&.20\&. That older version is not documented here\&. 792 801 .sp 793 802 Default: … … 877 886 This is the full pathname to a script that will be run by 878 887 \fBsmbd\fR(8) 879 when a machine is added to Samba\ 's domain and a Unix account matching the machine\'s name appended with a "$" does not already exist\&.888 when a machine is added to Samba\*(Aqs domain and a Unix account matching the machine\*(Aqs name appended with a "$" does not already exist\&. 880 889 .sp 881 890 This option is very similar to the … … 1025 1034 The 1026 1035 \fIaddprinter command\fR 1027 program can output a single line of text, which Samba will set as the port the new printer is connected to\&. If this line isn\ 't output, Samba won\'t reload its printer shares\&.1036 program can output a single line of text, which Samba will set as the port the new printer is connected to\&. If this line isn\*(Aqt output, Samba won\*(Aqt reload its printer shares\&. 1028 1037 .sp 1029 1038 Default: … … 1338 1347 Setting this option to a larger value could be useful to sites transitioning from WinNT and Win2k, as existing user and group rids would otherwise clash with sytem users etc\&. 1339 1348 .sp 1340 All UIDs and GIDs must be able to be resolved into SIDs for the correct operation of ACLs on the server\&. As such the algorithmic mapping can\ 't be \'turned off\', but pushing it \'out of the way\' should resolve the issues\&. Users and groups can then be assigned \'low\'RIDs in arbitrary\-rid supporting backends\&.1349 All UIDs and GIDs must be able to be resolved into SIDs for the correct operation of ACLs on the server\&. As such the algorithmic mapping can\*(Aqt be \*(Aqturned off\*(Aq, but pushing it \*(Aqout of the way\*(Aq should resolve the issues\&. Users and groups can then be assigned \*(Aqlow\*(Aq RIDs in arbitrary\-rid supporting backends\&. 1341 1350 .sp 1342 1351 Default: … … 1509 1518 is set then 1510 1519 nmbd 1511 will check the source address of any packets coming in on the broadcast sockets and discard any that don\ 't match the broadcast addresses of the interfaces in the1520 will check the source address of any packets coming in on the broadcast sockets and discard any that don\*(Aqt match the broadcast addresses of the interfaces in the 1512 1521 \m[blue]\fBinterfaces\fR\m[] 1513 1522 parameter list\&. As unicast packets are received on the other sockets it allows … … 1550 1559 parameter list then 1551 1560 smbpasswd 1552 will fail to connect in it\ 's default mode\&.1561 will fail to connect in it\*(Aqs default mode\&. 1553 1562 smbpasswd 1554 1563 can be forced to use the primary IP interface of the local host by using its … … 1696 1705 .PP 1697 1706 .RS 4 1698 This parameter specifies whether Samba should reply to a client\ 's file change notify requests\&.1707 This parameter specifies whether Samba should reply to a client\*(Aqs file change notify requests\&. 1699 1708 .sp 1700 1709 You should never need to change this parameter … … 1803 1812 .PP 1804 1813 .RS 4 1805 The name of a program that can be used to check password complexity\&. The password is sent to the program\ 's standard input\&.1814 The name of a program that can be used to check password complexity\&. The password is sent to the program\*(Aqs standard input\&. 1806 1815 .sp 1807 1816 The program must return 0 on a good password, or any other value if the password is bad\&. In case the password is considered weak (the program does not return 0) the user will be notified and the password change will fail\&. … … 1896 1905 client lanman auth\&. 1897 1906 .sp 1898 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\&.1907 Note that Windows Vista and later versions already use NTLMv2 by default, and some sites (particularly those following \*(Aqbest practice\*(Aq security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM\&. 1899 1908 .sp 1900 1909 Default: … … 1959 1968 If disabled, Samba will use the name used to look up the server when asking the KDC for a ticket\&. This avoids situations where a server may impersonate another, soliciting authentication as one principal while being known on the network as another\&. 1960 1969 .sp 1961 Note that Windows XP SP2 and later versions already follow this behaviour, and Windows Vista and later servers no longer supply this \ 'rfc4178 hint\'principal on the server side\&.1970 Note that Windows XP SP2 and later versions already follow this behaviour, and Windows Vista and later servers no longer supply this \*(Aqrfc4178 hint\*(Aq principal on the server side\&. 1962 1971 .sp 1963 1972 Default: … … 2018 2027 .sp 2019 2028 Example: 2020 \fI\fIcomment\fR\fR\fI = \fR\fIFred\ 's Files\fR\fI \fR2029 \fI\fIcomment\fR\fR\fI = \fR\fIFred\*(Aqs Files\fR\fI \fR 2021 2030 .RE 2022 2031 … … 2056 2065 This option takes the usual substitutions, which can be very useful\&. 2057 2066 .sp 2058 If the config file doesn\ 't exist then it won\'t be loaded (allowing you to special case the config files of just a few clients)\&.2067 If the config file doesn\*(Aqt exist then it won\*(Aqt be loaded (allowing you to special case the config files of just a few clients)\&. 2059 2068 .sp 2060 2069 \fINo default\fR … … 2068 2077 .PP 2069 2078 .RS 4 2070 This parameter allows you to "clone" service entries\&. The specified service is simply duplicated under the current service\ 's name\&. Any parameters specified in the current section will override those in the section being copied\&.2071 .sp 2072 This feature lets you set up a \ 'template\'service and create similar services easily\&. Note that the service being copied must occur earlier in the configuration file than the service doing the copying\&.2079 This parameter allows you to "clone" service entries\&. The specified service is simply duplicated under the current service\*(Aqs name\&. Any parameters specified in the current section will override those in the section being copied\&. 2080 .sp 2081 This feature lets you set up a \*(Aqtemplate\*(Aq service and create similar services easily\&. Note that the service being copied must occur earlier in the configuration file than the service doing the copying\&. 2073 2082 .sp 2074 2083 Default: … … 2105 2114 .PP 2106 2115 .RS 4 2107 When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \ 'AND\'ed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a file\&. Any bit2116 When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \*(AqAND\*(Aqed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a file\&. Any bit 2108 2117 \fInot\fR 2109 2118 set here will be removed from the modes set on a file when it is created\&. … … 2115 2124 write and execute bits from the UNIX modes\&. 2116 2125 .sp 2117 Following this Samba will bit\-wise \ 'OR\'the UNIX mode created from this parameter with the value of the2126 Following this Samba will bit\-wise \*(AqOR\*(Aq the UNIX mode created from this parameter with the value of the 2118 2127 \m[blue]\fBforce create mode\fR\m[] 2119 2128 parameter which is set to 000 by default\&. … … 2246 2255 \fBcups\fR\&. Its value is a free form string of options passed directly to the cups library\&. 2247 2256 .sp 2248 You can pass any generic print option known to CUPS (as listed in the CUPS "Software Users\ 'Manual")\&. You can also pass any printer specific option (as listed in "lpoptions \-d printername \-l") valid for the target queue\&. Multiple parameters should be space\-delimited name/value pairs according to the PAPI text option ABNF specification\&. Collection values ("name={a=\&.\&.\&. b=\&.\&.\&. c=\&.\&.\&.}") are stored with the curley brackets intact\&.2257 You can pass any generic print option known to CUPS (as listed in the CUPS "Software Users\*(Aq Manual")\&. You can also pass any printer specific option (as listed in "lpoptions \-d printername \-l") valid for the target queue\&. Multiple parameters should be space\-delimited name/value pairs according to the PAPI text option ABNF specification\&. Collection values ("name={a=\&.\&.\&. b=\&.\&.\&. c=\&.\&.\&.}") are stored with the curley brackets intact\&. 2249 2258 .sp 2250 2259 You should set this parameter to … … 2252 2261 if your CUPS server 2253 2262 error_log 2254 file contains messages such as "Unsupported format \ 'application/octet\-stream\'" when printing from a Windows client through Samba\&. It is no longer necessary to enable system wide raw printing in2263 file contains messages such as "Unsupported format \*(Aqapplication/octet\-stream\*(Aq" when printing from a Windows client through Samba\&. It is no longer necessary to enable system wide raw printing in 2255 2264 /etc/cups/mime\&.{convs,types}\&. 2256 2265 .sp … … 2292 2301 The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected\&. The deadtime only takes effect if the number of open files is zero\&. 2293 2302 .sp 2294 This is useful to stop a server\ 's resources being exhausted by a large number of inactive connections\&.2303 This is useful to stop a server\*(Aqs resources being exhausted by a large number of inactive connections\&. 2295 2304 .sp 2296 2305 Most clients have an auto\-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users\&. … … 2435 2444 services\&. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings\&. The device mode can only correctly be generated by the printer driver itself (which can only be executed on a Win32 platform)\&. Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL\&. 2436 2445 .sp 2437 Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode\&. Certain drivers will do things such as crashing the client\ 's Explorer\&.exe with a NULL devmode\&. However, other printer drivers can cause the client\'s spooler service (spoolsv\&.exe) to die if the devmode was not created by the driver itself (i\&.e\&. smbd generates a default devmode)\&.2446 Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode\&. Certain drivers will do things such as crashing the client\*(Aqs Explorer\&.exe with a NULL devmode\&. However, other printer drivers can cause the client\*(Aqs spooler service (spoolsv\&.exe) to die if the devmode was not created by the driver itself (i\&.e\&. smbd generates a default devmode)\&. 2438 2447 .sp 2439 2448 This parameter should be used with care and tested with the printer driver in question\&. It is better to leave the device mode to NULL and let the Windows client set the correct values\&. Because drivers do not do this all the time, setting … … 2645 2654 when managing users with remote RPC (NT) tools\&. 2646 2655 .sp 2647 This script is called when a remote client removes a user from the server, normally using \ 'User Manager for Domains\'or2656 This script is called when a remote client removes a user from the server, normally using \*(AqUser Manager for Domains\*(Aq or 2648 2657 rpcclient\&. 2649 2658 .sp … … 2728 2737 2729 2738 #!/bin/sh 2730 df $1 | tail \-1 | awk \ '{print $(NF\-4),$(NF\-2)}\'2739 df $1 | tail \-1 | awk \*(Aq{print $(NF\-4),$(NF\-2)}\*(Aq 2731 2740 .fi 2732 2741 .if n \{\ … … 2742 2751 2743 2752 #!/bin/sh 2744 /usr/bin/df \-k $1 | tail \-1 | awk \ '{print $3" "$5}\'2753 /usr/bin/df \-k $1 | tail \-1 | awk \*(Aq{print $3" "$5}\*(Aq 2745 2754 .fi 2746 2755 .if n \{\ … … 2772 2781 This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&. 2773 2782 .sp 2774 When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \ 'AND\'ed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a directory\&. Any bit2783 When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \*(AqAND\*(Aqed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a directory\&. Any bit 2775 2784 \fInot\fR 2776 2785 set here will be removed from the modes set on a directory when it is created\&. 2777 2786 .sp 2778 The default value of this parameter removes the \ 'group\' and \'other\'write bits from the UNIX mode, allowing only the user who owns the directory to modify it\&.2779 .sp 2780 Following this Samba will bit\-wise \ 'OR\'the UNIX mode created from this parameter with the value of the2787 The default value of this parameter removes the \*(Aqgroup\*(Aq and \*(Aqother\*(Aq write bits from the UNIX mode, allowing only the user who owns the directory to modify it\&. 2788 .sp 2789 Following this Samba will bit\-wise \*(AqOR\*(Aq the UNIX mode created from this parameter with the value of the 2781 2790 \m[blue]\fBforce directory mode\fR\m[] 2782 2791 parameter\&. This parameter is set to 000 by default (i\&.e\&. no extra mode bits are added)\&. … … 2808 2817 This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&. 2809 2818 .sp 2810 This parameter is applied as a mask (AND\ 'ed with) to the incoming permission bits, thus resetting any bits not in this mask\&. Make sure not to mix up this parameter with2819 This parameter is applied as a mask (AND\*(Aqed with) to the incoming permission bits, thus resetting any bits not in this mask\&. Make sure not to mix up this parameter with 2811 2820 \m[blue]\fBforce directory security mode\fR\m[], which works similar like this one but uses logical OR instead of AND\&. Essentially, zero bits in this mask are a set of bits that will always be set to zero\&. 2812 2821 .sp … … 2843 2852 .ps -1 2844 2853 .br 2845 Clients that only support netbios won\ 't be able to see your samba server when netbios support is disabled\&.2854 Clients that only support netbios won\*(Aqt be able to see your samba server when netbios support is disabled\&. 2846 2855 .sp .5v 2847 2856 .RE … … 2854 2863 .PP 2855 2864 .RS 4 2856 Enabling this parameter will disable Samba\ 's support for the SPOOLSS set of MS\-RPC\'s and will yield identical behavior as Samba 2\&.0\&.x\&. Windows NT/2000 clients will downgrade to using Lanman style printing commands\&. Windows 9x/ME will be unaffected by the parameter\&. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window\&. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand\&.2865 Enabling this parameter will disable Samba\*(Aqs support for the SPOOLSS set of MS\-RPC\*(Aqs and will yield identical behavior as Samba 2\&.0\&.x\&. Windows NT/2000 clients will downgrade to using Lanman style printing commands\&. Windows 9x/ME will be unaffected by the parameter\&. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window\&. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand\&. 2857 2866 \fIBe very careful about enabling this parameter\&.\fR 2858 2867 .sp … … 2958 2967 \m[blue]\fBdomain logons = Yes\fR\m[] 2959 2968 the default setting for this parameter is Yes, with the result that Samba will be a PDC\&. If 2960 \m[blue]\fBdomain master = No\fR\m[], Samba will function as a BDC\&. In general, this parameter should be set to \ 'No\'only on a BDC\&.2969 \m[blue]\fBdomain master = No\fR\m[], Samba will function as a BDC\&. In general, this parameter should be set to \*(AqNo\*(Aq only on a BDC\&. 2961 2970 .sp 2962 2971 Default: … … 3180 3189 This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. Visual C++ generated makefiles have the object directory as a dependency for each object file, and a make rule to create the directory\&. Also, when NMAKE compares timestamps it uses the creation time when examining a directory\&. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains\&. 3181 3190 .sp 3182 However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or or deleted in the directory\&. NMAKE finds all object files in the object directory\&. The timestamp of the last one built is then compared to the timestamp of the object directory\&. If the directory\ 's timestamp if newer, then all object files will be rebuilt\&. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected\&.3191 However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or or deleted in the directory\&. NMAKE finds all object files in the object directory\&. The timestamp of the last one built is then compared to the timestamp of the object directory\&. If the directory\*(Aqs timestamp if newer, then all object files will be rebuilt\&. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected\&. 3183 3192 .sp 3184 3193 Default: … … 3233 3242 This parameter specifies a set of UNIX mode bit permissions that will 3234 3243 \fIalways\fR 3235 be set on a file created by Samba\&. This is done by bitwise \ 'OR\'ing these bits onto the mode bits of a file that is being created\&. The default for this parameter is (in octal) 000\&. The modes in this parameter are bitwise \'OR\'ed onto the file mode after the mask set in the3244 be set on a file created by Samba\&. This is done by bitwise \*(AqOR\*(Aqing these bits onto the mode bits of a file that is being created\&. The default for this parameter is (in octal) 000\&. The modes in this parameter are bitwise \*(AqOR\*(Aqed onto the file mode after the mask set in the 3236 3245 \fIcreate mask\fR 3237 3246 parameter is applied\&. 3238 3247 .sp 3239 The example below would force all newly created files to have read and execute permissions set for \ 'group\' and \'other\' as well as the read/write/execute bits set for the \'user\'\&.3248 The example below would force all newly created files to have read and execute permissions set for \*(Aqgroup\*(Aq and \*(Aqother\*(Aq as well as the read/write/execute bits set for the \*(Aquser\*(Aq\&. 3240 3249 .sp 3241 3250 Default: … … 3252 3261 This parameter specifies a set of UNIX mode bit permissions that will 3253 3262 \fIalways\fR 3254 be set on a directory created by Samba\&. This is done by bitwise \ 'OR\'ing these bits onto the mode bits of a directory that is being created\&. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory\&. This operation is done after the mode mask in the parameter3263 be set on a directory created by Samba\&. This is done by bitwise \*(AqOR\*(Aqing these bits onto the mode bits of a directory that is being created\&. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory\&. This operation is done after the mode mask in the parameter 3255 3264 \fIdirectory mask\fR 3256 3265 is applied\&. 3257 3266 .sp 3258 The example below would force all created directories to have read and execute permissions set for \ 'group\' and \'other\' as well as the read/write/execute bits set for the \'user\'\&.3267 The example below would force all created directories to have read and execute permissions set for \*(Aqgroup\*(Aq and \*(Aqother\*(Aq as well as the read/write/execute bits set for the \*(Aquser\*(Aq\&. 3259 3268 .sp 3260 3269 Default: … … 3271 3280 This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&. 3272 3281 .sp 3273 This parameter is applied as a mask (OR\ 'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Make sure not to mix up this parameter with3282 This parameter is applied as a mask (OR\*(Aqed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Make sure not to mix up this parameter with 3274 3283 \m[blue]\fBdirectory security mask\fR\m[], which works in a similar manner to this one, but uses a logical AND instead of an OR\&. 3275 3284 .sp … … 3313 3322 This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service\&. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking\&. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files\&. 3314 3323 .sp 3315 In Samba 2\&.0\&.5 and above this parameter has extended functionality in the following way\&. If the group name listed here has a \ '+\'character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group\&. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group\&. This gives a finer granularity of ownership assignment\&. For example, the setting3324 In Samba 2\&.0\&.5 and above this parameter has extended functionality in the following way\&. If the group name listed here has a \*(Aq+\*(Aq character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group\&. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group\&. This gives a finer granularity of ownership assignment\&. For example, the setting 3316 3325 force group = +sys 3317 3326 means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share\&. All other users will retain their ordinary primary group\&. … … 3341 3350 option)\&. 3342 3351 .sp 3343 When assigning a new driver to a printer on a remote Windows compatible print server such as Samba, the Windows client will rename the printer to match the driver name just uploaded\&. This can result in confusion for users when multiple printers are bound to the same driver\&. To prevent Samba from allowing the printer\ 's printername to differ from the sharename defined in smb\&.conf, set3352 When assigning a new driver to a printer on a remote Windows compatible print server such as Samba, the Windows client will rename the printer to match the driver name just uploaded\&. This can result in confusion for users when multiple printers are bound to the same driver\&. To prevent Samba from allowing the printer\*(Aqs printername to differ from the sharename defined in smb\&.conf, set 3344 3353 \fIforce printername = yes\fR\&. 3345 3354 .sp 3346 3355 Be aware that enabling this parameter may affect migrating printers from a Windows server to Samba since Windows has no way to force the sharename and printername to match\&. 3347 3356 .sp 3348 It is recommended that this parameter\ 's value not be changed once the printer is in use by clients as this could cause a user not be able to delete printer connections from their local Printers folder\&.3357 It is recommended that this parameter\*(Aqs value not be changed once the printer is in use by clients as this could cause a user not be able to delete printer connections from their local Printers folder\&. 3349 3358 .sp 3350 3359 Default: … … 3358 3367 This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&. 3359 3368 .sp 3360 This parameter is applied as a mask (OR\ 'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Make sure not to mix up this parameter with3369 This parameter is applied as a mask (OR\*(Aqed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Make sure not to mix up this parameter with 3361 3370 \m[blue]\fBsecurity mask\fR\m[], which works similar like this one but uses logical AND instead of OR\&. 3362 3371 .sp … … 3729 3738 .PP 3730 3739 .RS 4 3731 This is a list of files or directories that are not visible but are accessible\&. The DOS \ 'hidden\'attribute is applied to any files or directories that match\&.3732 .sp 3733 Each entry in the list must be separated by a \ '/\', which allows spaces to be included in the entry\&. \'*\' and \'?\'can be used to specify multiple files or directories as in DOS wildcards\&.3734 .sp 3735 Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator \ '/\'\&.3740 This is a list of files or directories that are not visible but are accessible\&. The DOS \*(Aqhidden\*(Aq attribute is applied to any files or directories that match\&. 3741 .sp 3742 Each entry in the list must be separated by a \*(Aq/\*(Aq, which allows spaces to be included in the entry\&. \*(Aq*\*(Aq and \*(Aq?\*(Aq can be used to specify multiple files or directories as in DOS wildcards\&. 3743 .sp 3744 Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator \*(Aq/\*(Aq\&. 3736 3745 .sp 3737 3746 Note that the case sensitivity option is applicable in hiding files\&. … … 3763 3772 .PP 3764 3773 .RS 4 3765 This parameter prevents clients from seeing special files such as sockets, devices and fifo\ 's in directory listings\&.3774 This parameter prevents clients from seeing special files such as sockets, devices and fifo\*(Aqs in directory listings\&. 3766 3775 .sp 3767 3776 Default: … … 3800 3809 is also acting as a Win95/98 3801 3810 \fIlogon server\fR 3802 then this parameter specifies the NIS (or YP) map from which the server for the user\ 's home directory should be extracted\&. At present, only the Sun auto\&.home map format is understood\&. The form of the map is:3811 then this parameter specifies the NIS (or YP) map from which the server for the user\*(Aqs home directory should be extracted\&. At present, only the Sun auto\&.home map format is understood\&. The form of the map is: 3803 3812 .sp 3804 3813 .if n \{\ … … 3812 3821 .\} 3813 3822 .sp 3814 and the program will extract the servername from before the first \ ':\'\&. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\&.3823 and the program will extract the servername from before the first \*(Aq:\*(Aq\&. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\&. 3815 3824 .if n \{\ 3816 3825 .sp … … 3989 3998 .PP 3990 3999 .RS 4 3991 This parameter specifies the number of seconds that Winbind\ 's idmap interface will cache positive SID/uid/gid query results\&.4000 This parameter specifies the number of seconds that Winbind\*(Aqs idmap interface will cache positive SID/uid/gid query results\&. 3992 4001 .sp 3993 4002 Default: … … 3999 4008 .PP 4000 4009 .RS 4 4001 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 the4010 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\*(Aqs ID mapping is configured by options starting with the 4002 4011 \m[blue]\fBidmap config\fR\m[] 4003 4012 prefix\&. An idmap option consists of the … … 4082 4091 .PP 4083 4092 .RS 4 4084 This parameter specifies the number of seconds that Winbind\ 's idmap interface will cache negative SID/uid/gid query results\&.4093 This parameter specifies the number of seconds that Winbind\*(Aqs idmap interface will cache negative SID/uid/gid query results\&. 4085 4094 .sp 4086 4095 Default: … … 4157 4166 The ownership of new files and directories is normally governed by effective uid of the connected user\&. This option allows the Samba administrator to specify that the ownership for new files and directories should be controlled by the ownership of the parent directory\&. 4158 4167 .sp 4159 Common scenarios where this behavior is useful is in implementing drop\-boxes where users can create and edit files but not delete them and to ensure that newly create files in a user\ 's roaming profile directory are actually owner by the user\&.4168 Common scenarios where this behavior is useful is in implementing drop\-boxes where users can create and edit files but not delete them and to ensure that newly create files in a user\*(Aqs roaming profile directory are actually owner by the user\&. 4160 4169 .sp 4161 4170 Default: … … 4277 4286 The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form\&. 4278 4287 .sp 4279 The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS\ 's normal hostname resolution mechanisms\&.4288 The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS\*(Aqs normal hostname resolution mechanisms\&. 4280 4289 .sp 4281 4290 By default Samba enables all active interfaces that are broadcast capable except the loopback adaptor (IP address 127\&.0\&.0\&.1)\&. … … 4298 4307 check to absolutely ensure an improper setting does not breach your security\&. 4299 4308 .sp 4300 A name starting with a \ '@\'is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database\&.4301 .sp 4302 A name starting with \ '+\' is interpreted only by looking in the UNIX group database via the NSS getgrnam() interface\&. A name starting with \'&\' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\&. The characters \'+\' and \'&\'may be used at the start of the name in either order so the value4309 A name starting with a \*(Aq@\*(Aq is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database\&. 4310 .sp 4311 A name starting with \*(Aq+\*(Aq is interpreted only by looking in the UNIX group database via the NSS getgrnam() interface\&. A name starting with \*(Aq&\*(Aq is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\&. The characters \*(Aq+\*(Aq and \*(Aq&\*(Aq may be used at the start of the name in either order so the value 4303 4312 \fI+&group\fR 4304 4313 means check the UNIX group database, followed by the NIS netgroup database, and the value 4305 4314 \fI&+group\fR 4306 means check the NIS netgroup database, followed by the UNIX group database (the same as the \ '@\'prefix)\&.4315 means check the NIS netgroup database, followed by the UNIX group database (the same as the \*(Aq@\*(Aq prefix)\&. 4307 4316 .sp 4308 4317 The current servicename is substituted for … … 4463 4472 When this parameter is set to 4464 4473 no 4465 this will also result in sambaLMPassword in Samba\ 's passdb being blanked after the next password change\&. As a result of that lanman clients won\'t be able to authenticate, even if lanman auth is reenabled later on\&.4474 this will also result in sambaLMPassword in Samba\*(Aqs passdb being blanked after the next password change\&. As a result of that lanman clients won\*(Aqt be able to authenticate, even if lanman auth is reenabled later on\&. 4466 4475 .sp 4467 4476 Unlike the … … 4469 4478 option, this parameter cannot alter client behaviour, and the LANMAN response will still be sent over the network\&. See the 4470 4479 client lanman auth 4471 to disable this for Samba\ 's clients (such as smbclient)4480 to disable this for Samba\*(Aqs clients (such as smbclient) 4472 4481 .sp 4473 4482 If this option, and … … 4539 4548 for tracing function calls\&. 4540 4549 .sp 4541 The debug ouput from the LDAP libraries appears with the prefix [LDAP] in Samba\ 's logging output\&. The level at which LDAP logging is printed is controlled by the parameter4550 The debug ouput from the LDAP libraries appears with the prefix [LDAP] in Samba\*(Aqs logging output\&. The level at which LDAP logging is printed is controlled by the parameter 4542 4551 \fIldap debug threshold\fR\&. 4543 4552 .sp … … 4602 4611 \fIoff\fR 4603 4612 to disable this, and 4604 \fIauto\fR, to use the libldap default settings\&. libldap\ 's choice of following referrals or not is set in /etc/openldap/ldap\&.conf with the REFERRALS parameter as documented in ldap\&.conf(5)\&.4613 \fIauto\fR, to use the libldap default settings\&. libldap\*(Aqs choice of following referrals or not is set in /etc/openldap/ldap\&.conf with the REFERRALS parameter as documented in ldap\&.conf(5)\&. 4605 4614 .sp 4606 4615 Default: … … 4732 4741 .PP 4733 4742 .RS 4 4734 When Samba is asked to write to a read\-only LDAP replica, we are redirected to talk to the read\-write master server\&. This server then replicates our changes back to the \ 'local\' server, however the replication might take some seconds, especially over slow links\&. Certain client activities, particularly domain joins, can become confused by the \'success\' that does not immediately change the LDAP back\-end\'s data\&.4743 When Samba is asked to write to a read\-only LDAP replica, we are redirected to talk to the read\-write master server\&. This server then replicates our changes back to the \*(Aqlocal\*(Aq server, however the replication might take some seconds, especially over slow links\&. Certain client activities, particularly domain joins, can become confused by the \*(Aqsuccess\*(Aq that does not immediately change the LDAP back\-end\*(Aqs data\&. 4735 4744 .sp 4736 4745 This option simply causes Samba to wait a short time, to allow the LDAP server to catch up\&. If you have a particularly high\-latency network, you may wish to time the LDAP replication with a network sniffer, and increase this value accordingly\&. Be aware that no checking is performed that the data has actually replicated\&. … … 4856 4865 This option is used to define whether or not Samba should use SSL when connecting to the ldap server using 4857 4866 \fIads\fR 4858 methods\&. Rpc methods are not affected by this parameter\&. Please note, that this parameter won\ 't have any effect if4867 methods\&. Rpc methods are not affected by this parameter\&. Please note, that this parameter won\*(Aqt have any effect if 4859 4868 \m[blue]\fBldap ssl\fR\m[] 4860 4869 is set to … … 4876 4885 This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is 4877 4886 \fINOT\fR 4878 related to Samba\ 's previous SSL support which was enabled by specifying the4887 related to Samba\*(Aqs previous SSL support which was enabled by specifying the 4879 4888 \-\-with\-ssl 4880 4889 option to the … … 5079 5088 \fByes\fR\&. Setting this value to 5080 5089 \fByes\fR 5081 doesn\ 't mean that Samba will5090 doesn\*(Aqt mean that Samba will 5082 5091 \fIbecome\fR 5083 5092 the local master browser on a subnet, just that … … 5460 5469 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. 5461 5470 .sp 5462 This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user\ 's home directory\&. This is done in the following way:5471 This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user\*(Aqs home directory\&. This is done in the following way: 5463 5472 .sp 5464 5473 … … 5618 5627 This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job\&. 5619 5628 .sp 5620 This command should be a program or script which takes a printer name and job number to pause the print job\&. One way of implementing this is by using job priorities, where jobs having a too low priority won\ 't be sent to the printer\&.5629 This command should be a program or script which takes a printer name and job number to pause the print job\&. One way of implementing this is by using job priorities, where jobs having a too low priority won\*(Aqt be sent to the printer\&. 5621 5630 .sp 5622 5631 If a … … 5648 5657 command used by the system, so if you use different 5649 5658 lpq 5650 commands for different users then they won\ 't share cache information\&.5659 commands for different users then they won\*(Aqt share cache information\&. 5651 5660 .sp 5652 5661 The cache files are stored in … … 5900 5909 Note that the character to use may be specified using the 5901 5910 \m[blue]\fBmangling char\fR\m[] 5902 option, if you don\ 't like \'~\'\&.5903 .RE 5904 .sp 5905 .RS 4 5906 .ie n \{\ 5907 \h'-04'\(bu\h'+03'\c 5908 .\} 5909 .el \{\ 5910 .sp -1 5911 .IP \(bu 2.3 5912 .\} 5913 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)\&.5911 option, if you don\*(Aqt like \*(Aq~\*(Aq\&. 5912 .RE 5913 .sp 5914 .RS 4 5915 .ie n \{\ 5916 \h'-04'\(bu\h'+03'\c 5917 .\} 5918 .el \{\ 5919 .sp -1 5920 .IP \(bu 2.3 5921 .\} 5922 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\*(Aqs three underscores)\&. 5914 5923 .RE 5915 5924 .sp … … 5947 5956 \fImagic\fR 5948 5957 character in 5949 \m[blue]\fBname mangling\fR\m[]\&. The default is a \ '~\'but this may interfere with some software\&. Use this option to set it to whatever you prefer\&. This is effective only when mangling method is hash\&.5958 \m[blue]\fBname mangling\fR\m[]\&. The default is a \*(Aq~\*(Aq but this may interfere with some software\&. Use this option to set it to whatever you prefer\&. This is effective only when mangling method is hash\&. 5950 5959 .sp 5951 5960 Default: … … 5975 5984 This boolean parameter controls whether 5976 5985 \fBsmbd\fR(8) 5977 will attempt to map the \ 'inherit\' and \'protected\'access control entry flags stored in Windows ACLs into an extended attribute called user\&.SAMBA_PAI\&. This parameter only takes effect if Samba is being run on a platform that supports extended attributes (Linux and IRIX so far) and allows the Windows 2000 ACL editor to correctly use inheritance with the Samba POSIX ACL mapping code\&.5986 will attempt to map the \*(Aqinherit\*(Aq and \*(Aqprotected\*(Aq access control entry flags stored in Windows ACLs into an extended attribute called user\&.SAMBA_PAI\&. This parameter only takes effect if Samba is being run on a platform that supports extended attributes (Linux and IRIX so far) and allows the Windows 2000 ACL editor to correctly use inheritance with the Samba POSIX ACL mapping code\&. 5978 5987 .sp 5979 5988 Default: … … 6112 6121 This parameter can take four different values, which tell 6113 6122 \fBsmbd\fR(8) 6114 what to do with user login requests that don\ 't match a valid UNIX user in some way\&.6123 what to do with user login requests that don\*(Aqt match a valid UNIX user in some way\&. 6115 6124 .sp 6116 6125 The four settings are : … … 6194 6203 .PP 6195 6204 .RS 4 6196 If a client connects to smbd using an untrusted domain name, such as BOGUS\euser, smbd replaces the BOGUS domain with it\ 's SAM name before attempting to authenticate that user\&. In the case where smbd is acting as a PDC this will be DOMAIN\euser\&. In the case where smbd is acting as a domain member server or a standalone server this will be WORKSTATION\euser\&.6205 If a client connects to smbd using an untrusted domain name, such as BOGUS\euser, smbd replaces the BOGUS domain with it\*(Aqs SAM name before attempting to authenticate that user\&. In the case where smbd is acting as a PDC this will be DOMAIN\euser\&. In the case where smbd is acting as a domain member server or a standalone server this will be WORKSTATION\euser\&. 6197 6206 .sp 6198 6207 In previous versions of Samba (pre 3\&.4), if smbd was acting as a domain member server, the BOGUS domain name would instead be replaced by the primary domain which smbd was a member of\&. In this case authentication would be deferred off to a DC using the credentials DOMAIN\euser\&. … … 6234 6243 \fImax disk size\fR\&. 6235 6244 .sp 6236 This option is primarily useful to work around bugs in some pieces of software that can\ 't handle very large disks, particularly disks over 1GB in size\&.6245 This option is primarily useful to work around bugs in some pieces of software that can\*(Aqt handle very large disks, particularly disks over 1GB in size\&. 6237 6246 .sp 6238 6247 A … … 6384 6393 .IP \(bu 2.3 6385 6394 .\} 6386 \fBSMB2\fR: Re\-implementation of the SMB protocol\&. Used by Windows Vista and newer\&. The Samba implementation of SMB2 is currently marked experimental!6395 \fBSMB2\fR: Re\-implementation of the SMB protocol\&. Used by Windows Vista and newer\&. 6387 6396 .RE 6388 6397 .sp … … 6448 6457 This option tells 6449 6458 \fBnmbd\fR(8) 6450 what the default \ 'time to live\'of NetBIOS names should be (in seconds) when6459 what the default \*(Aqtime to live\*(Aq of NetBIOS names should be (in seconds) when 6451 6460 nmbd 6452 6461 is requesting a name using either a broadcast packet or from a WINS server\&. You should never need to change this parameter\&. The default is 3 days\&. … … 6462 6471 This option tells 6463 6472 \fBsmbd\fR(8) 6464 when acting as a WINS server (\m[blue]\fBwins support = yes\fR\m[]) what the maximum \ 'time to live\'of NetBIOS names that6473 when acting as a WINS server (\m[blue]\fBwins support = yes\fR\m[]) what the maximum \*(Aqtime to live\*(Aq of NetBIOS names that 6465 6474 nmbd 6466 6475 will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 days (518400 seconds)\&. … … 6497 6506 .\} 6498 6507 .nf 6499 message command = csh \-c \ 'xedit %s;rm %s\'&6508 message command = csh \-c \*(Aqxedit %s;rm %s\*(Aq & 6500 6509 .fi 6501 6510 .if n \{\ … … 6505 6514 This delivers the message using 6506 6515 xedit, then removes it afterwards\&. 6507 \fINOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR\&. That\ 's why I have the \'&\' on the end\&. If it doesn\'t return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully)\&.6516 \fINOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR\&. That\*(Aqs why I have the \*(Aq&\*(Aq on the end\&. If it doesn\*(Aqt return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully)\&. 6508 6517 .sp 6509 6518 All messages are delivered as the global guest user\&. The command takes the standard substitutions, although 6510 6519 \fI %u\fR 6511 won\ 't work (\fI%U\fR6520 won\*(Aqt work (\fI%U\fR 6512 6521 may be better in this case)\&. 6513 6522 .sp … … 6553 6562 You could make this command send mail, or whatever else takes your fancy\&. Please let us know of any really interesting ideas you have\&. 6554 6563 .sp 6555 Here\ 's a way of sending the messages as mail to root:6564 Here\*(Aqs a way of sending the messages as mail to root: 6556 6565 .sp 6557 6566 .if n \{\ … … 6559 6568 .\} 6560 6569 .nf 6561 message command = /bin/mail \-s \ 'message from %f on %m\'root < %s; rm %s6570 message command = /bin/mail \-s \*(Aqmessage from %f on %m\*(Aq root < %s; rm %s 6562 6571 .fi 6563 6572 .if n \{\ … … 6565 6574 .\} 6566 6575 .sp 6567 If you don\ 't have a message command then the message won\'t be delivered and Samba will tell the sender there was an error\&. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered\&.6576 If you don\*(Aqt have a message command then the message won\*(Aqt be delivered and Samba will tell the sender there was an error\&. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered\&. 6568 6577 .sp 6569 6578 If you want to silently delete it then try: … … 6583 6592 .sp 6584 6593 Example: 6585 \fI\fImessage command\fR\fR\fI = \fR\fIcsh \-c \ 'xedit %s; rm %s\'&\fR\fI \fR6594 \fI\fImessage command\fR\fR\fI = \fR\fIcsh \-c \*(Aqxedit %s; rm %s\*(Aq &\fR\fI \fR 6586 6595 .RE 6587 6596 … … 6642 6651 This option tells 6643 6652 \fBnmbd\fR(8) 6644 when acting as a WINS server (\m[blue]\fBwins support = yes\fR\m[]) what the minimum \ 'time to live\'of NetBIOS names that6653 when acting as a WINS server (\m[blue]\fBwins support = yes\fR\m[]) what the minimum \*(Aqtime to live\*(Aq of NetBIOS names that 6645 6654 nmbd 6646 6655 will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 hours (21600 seconds)\&. … … 6697 6706 .PP 6698 6707 .RS 4 6699 Specifies the number of seconds it takes before entries in samba\ 's hostname resolve cache time out\&. If the timeout is set to 0\&. the caching is disabled\&.6708 Specifies the number of seconds it takes before entries in samba\*(Aqs hostname resolve cache time out\&. If the timeout is set to 0\&. the caching is disabled\&. 6700 6709 .sp 6701 6710 Default: … … 6795 6804 .sp 6796 6805 \&. 6797 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 processes6806 This will allow Samba and other unix processes to interact over DCE/RPC without using TCP/IP\&. Additionally a sub\-directory \*(Aqnp\*(Aq has restricted permissions, and allows a trusted communication channel between Samba processes 6798 6807 .sp 6799 6808 Default: … … 6821 6830 .PP 6822 6831 .RS 4 6823 This sets the NetBIOS name by which a Samba server is known\&. By default it is the same as the first component of the host\ 's DNS name\&. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under\&.6832 This sets the NetBIOS name by which a Samba server is known\&. By default it is the same as the first component of the host\*(Aqs DNS name\&. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under\&. 6824 6833 .sp 6825 6834 There is a bug in Samba\-3 that breaks operation of browsing and access to shares if the netbios name is set to the literal name … … 6848 6857 .PP 6849 6858 .RS 4 6850 Get the home share server from a NIS map\&. For UNIX systems that use an automounter, the user\ 's home directory will often be mounted on a workstation on demand from a remote server\&.6859 Get the home share server from a NIS map\&. For UNIX systems that use an automounter, the user\*(Aqs home directory will often be mounted on a workstation on demand from a remote server\&. 6851 6860 .sp 6852 6861 When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS)\&. This can be very slow\&. … … 6951 6960 .PP 6952 6961 .RS 4 6953 When Samba 3\&.0 is configured to enable PAM support (i\&.e\&. \-\-with\-pam), this parameter will control whether or not Samba should obey PAM\ 's account and session management directives\&. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management\&. Note that Samba always ignores PAM for authentication in the case of6962 When Samba 3\&.0 is configured to enable PAM support (i\&.e\&. \-\-with\-pam), this parameter will control whether or not Samba should obey PAM\*(Aqs account and session management directives\&. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management\&. Note that Samba always ignores PAM for authentication in the case of 6954 6963 \m[blue]\fBencrypt passwords = yes\fR\m[]\&. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption\&. 6955 6964 .sp … … 6970 6979 level security\&. 6971 6980 .sp 6972 Note that this also means Samba won\ 't try to deduce usernames from the service name\&. This can be annoying for the [homes] section\&. To get around this you could use6981 Note that this also means Samba won\*(Aqt try to deduce usernames from the service name\&. This can be annoying for the [homes] section\&. To get around this you could use 6973 6982 user = %S 6974 6983 which means your … … 7098 7107 .PP 7099 7108 .RS 4 7100 With the addition of better PAM support in Samba 2\&.2, this parameter, it is possible to use PAM\ 's password change control flag for Samba\&. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in7109 With the addition of better PAM support in Samba 2\&.2, this parameter, it is possible to use PAM\*(Aqs password change control flag for Samba\&. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in 7101 7110 \m[blue]\fBpasswd program\fR\m[]\&. It should be possible to enable this without changing your 7102 7111 \m[blue]\fBpasswd chat\fR\m[] … … 7142 7151 This option allows the administrator to chose which backend will be used for storing user and possibly group information\&. This allows you to swap between different storage mechanisms without recompile\&. 7143 7152 .sp 7144 The parameter value is divided into two parts, the backend\ 's name, and a \'location\'string that has meaning only to that particular backed\&. These are separated by a : character\&.7153 The parameter value is divided into two parts, the backend\*(Aqs name, and a \*(Aqlocation\*(Aq string that has meaning only to that particular backed\&. These are separated by a : character\&. 7145 7154 .sp 7146 7155 Available backends can include: … … 7222 7231 .PP 7223 7232 .RS 4 7224 This parameter controls whether Samba substitutes %\-macros in the passdb fields if they are explicitly set\&. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user\ 's primary group\&.7233 This parameter controls whether Samba substitutes %\-macros in the passdb fields if they are explicitly set\&. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user\*(Aqs primary group\&. 7225 7234 .sp 7226 7235 Default: … … 7270 7279 conversation that takes places between 7271 7280 \fBsmbd\fR(8) 7272 and the local password changing program to change the user\ 's password\&. The string describes a sequence of response\-receive pairs that7281 and the local password changing program to change the user\*(Aqs password\&. The string describes a sequence of response\-receive pairs that 7273 7282 \fBsmbd\fR(8) 7274 7283 uses to determine what to send to the … … 7283 7292 \fByes\fR\&. This sequence is then called 7284 7293 \fIAS ROOT\fR 7285 when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext\&. This means that root must be able to reset the user\ 's password without knowing the text of the previous password\&. In the presence of NIS/YP, this means that the7294 when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext\&. This means that root must be able to reset the user\*(Aqs password without knowing the text of the previous password\&. In the presence of NIS/YP, this means that the 7286 7295 \m[blue]\fBpasswd program\fR\m[] 7287 7296 must be executed on the NIS master\&. … … 7291 7300 which is substituted for the new password\&. The old passsword (\fI%o\fR) is only available when 7292 7301 \m[blue]\fBencrypt passwords\fR\m[] 7293 has been disabled\&. The chat sequence can also contain the standard macros \en, \er, \et and \es to give line\-feed, carriage\-return, tab and space\&. The chat sequence string can also contain a \ '*\'which matches any sequence of characters\&. Double quotes can be used to collect strings with spaces in them into a single string\&.7302 has been disabled\&. The chat sequence can also contain the standard macros \en, \er, \et and \es to give line\-feed, carriage\-return, tab and space\&. The chat sequence string can also contain a \*(Aq*\*(Aq which matches any sequence of characters\&. Double quotes can be used to collect strings with spaces in them into a single string\&. 7294 7303 .sp 7295 7304 If the send string in any part of the chat sequence is a full stop "\&.", then no string is sent\&. Similarly, if the expect string is a full stop then no string is expected\&. … … 7399 7408 \fBads\fR, then this option 7400 7409 \fIshould not\fR 7401 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\&.7402 .sp 7403 \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 the7410 be used, as the default \*(Aq*\*(Aq 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\&. 7411 .sp 7412 \fIIt is strongly recommended that you use the default of \*(Aq*\*(Aq\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 \*(Aq*\*(Aq, or list several hosts in the 7404 7413 \fIpassword server\fR 7405 7414 option then … … 7407 7416 will try each in turn till it finds one that responds\&. This is useful in case your primary server goes down\&. 7408 7417 .sp 7409 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\&.7418 If the list of servers contains both names/IP\*(Aqs and the \*(Aq*\*(Aq character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC\*(Aqs will be added to the list as well\&. Samba will not attempt to optimize this list by locating the closest DC\&. 7410 7419 .sp 7411 7420 If parameter is a name, it is looked up using the parameter … … 7480 7489 .\} 7481 7490 Using a password server means your UNIX box (running Samba) is only as secure as (a host masqurading as) your password server\&. 7482 \fIDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON\ 'T COMPLETELY TRUST\fR\&.7491 \fIDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON\*(AqT COMPLETELY TRUST\fR\&. 7483 7492 .RE 7484 7493 .sp … … 7531 7540 This parameter specifies a directory to which the user of the service is to be given access\&. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing\&. 7532 7541 .sp 7533 For a printable service offering guest access, the service should be readonly and the path should be world\-writeable and have the sticky bit set\&. This is not mandatory of course, but you probably won\ 't get the results you expect if you do otherwise\&.7542 For a printable service offering guest access, the service should be readonly and the path should be world\-writeable and have the sticky bit set\&. This is not mandatory of course, but you probably won\*(Aqt get the results you expect if you do otherwise\&. 7534 7543 .sp 7535 7544 Any occurrences of … … 7630 7639 .sp 7631 7640 7632 preexec = csh \-c \ 'echo \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient \-M %m \-I %I\'&7641 preexec = csh \-c \*(Aqecho \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient \-M %m \-I %I\*(Aq & 7633 7642 .sp 7634 7643 Of course, this could get annoying after a while :\-) … … 7819 7828 .\} 7820 7829 .sp 7821 where the \ '|\' separates aliases of a printer\&. The fact that the second alias has a space in it gives a hint to Samba that it\'s a comment\&.7830 where the \*(Aq|\*(Aq separates aliases of a printer\&. The fact that the second alias has a space in it gives a hint to Samba that it\*(Aqs a comment\&. 7822 7831 .if n \{\ 7823 7832 .sp … … 7853 7862 After a print job has finished spooling to a service, this command will be used via a 7854 7863 system() 7855 call to process the spool file\&. Typically the command specified will submit the spool file to the host\ 's printing subsystem, but there is no requirement that this be the case\&. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\&.7864 call to process the spool file\&. Typically the command specified will submit the spool file to the host\*(Aqs printing subsystem, but there is no requirement that this be the case\&. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\&. 7856 7865 .sp 7857 7866 The print command is simply a text string\&. It will be used verbatim after macro substitutions have been made: … … 7889 7898 in the [global] section\&. 7890 7899 .sp 7891 You can form quite complex print commands by realizing that they are just passed to a shell\&. For example the following will log a print job, print the file, then remove it\&. Note that \ ';\'is the usual separator for command in shell scripts\&.7900 You can form quite complex print commands by realizing that they are just passed to a shell\&. For example the following will log a print job, print the file, then remove it\&. Note that \*(Aq;\*(Aq is the usual separator for command in shell scripts\&. 7892 7901 .sp 7893 7902 print command = echo Printing %s >> /tmp/print\&.log; lpr \-P %p %s; rm %s … … 8137 8146 .sp 8138 8147 If this parameter is 8139 \fByes\fR, then users of a service may not create or modify files in the service\ 's directory\&.8148 \fByes\fR, then users of a service may not create or modify files in the service\*(Aqs directory\&. 8140 8149 .sp 8141 8150 Note that a printable service (printable = yes) will … … 8208 8217 to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name\&. 8209 8218 .sp 8210 This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don\ 't work\&. The remote workgroup can be anywhere that you can send IP packets to\&.8219 This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don\*(Aqt work\&. The remote workgroup can be anywhere that you can send IP packets to\&. 8211 8220 .sp 8212 8221 For example: … … 8244 8253 to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment\&. This option will allow you to gain browse lists for multiple workgroups across routed networks\&. This is done in a manner that does not work with any non\-Samba servers\&. 8245 8254 .sp 8246 This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don\ 't work\&. The remote workgroup can be anywhere that you can send IP packets to\&.8255 This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don\*(Aqt work\&. The remote workgroup can be anywhere that you can send IP packets to\&. 8247 8256 .sp 8248 8257 For example: … … 8483 8492 This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&. 8484 8493 .sp 8485 This parameter is applied as a mask (AND\ 'ed with) to the incoming permission bits, thus resetting any bits not in this mask\&. Make sure not to mix up this parameter with8494 This parameter is applied as a mask (AND\*(Aqed with) to the incoming permission bits, thus resetting any bits not in this mask\&. Make sure not to mix up this parameter with 8486 8495 \m[blue]\fBforce security mode\fR\m[], which works in a manner similar to this one but uses a logical OR instead of an AND\&. 8487 8496 .sp … … 8558 8567 that the name of the resource being requested is 8559 8568 \fInot\fR 8560 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\ 't work in user level security without allowing the server to automatically map unknown users into the8569 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\*(Aqt work in user level security without allowing the server to automatically map unknown users into the 8561 8570 \m[blue]\fBguest account\fR\m[]\&. See the 8562 8571 \m[blue]\fBmap to guest\fR\m[] … … 8579 8588 .sp 8580 8589 \fINote\fR 8581 that from the client\ 's point of view8590 that from the client\*(Aqs point of view 8582 8591 security = domain 8583 8592 is the same as … … 8587 8596 that the name of the resource being requested is 8588 8597 \fInot\fR 8589 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\ 't work in user level security without allowing the server to automatically map unknown users into the8598 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\*(Aqt work in user level security without allowing the server to automatically map unknown users into the 8590 8599 \m[blue]\fBguest account\fR\m[]\&. See the 8591 8600 \m[blue]\fBmap to guest\fR\m[] … … 8747 8756 .ps -1 8748 8757 .br 8749 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)\&.8758 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\*(Aqs 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)\&. 8750 8759 .sp .5v 8751 8760 .RE … … 8778 8787 .ps -1 8779 8788 .br 8780 From the client\ 's point of view,8789 From the client\*(Aqs point of view, 8781 8790 security = server 8782 8791 is the same as … … 8802 8811 that the name of the resource being requested is 8803 8812 \fInot\fR 8804 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\ 't work in user level security without allowing the server to automatically map unknown users into the8813 sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don\*(Aqt work in user level security without allowing the server to automatically map unknown users into the 8805 8814 \m[blue]\fBguest account\fR\m[]\&. See the 8806 8815 \m[blue]\fBmap to guest\fR\m[] … … 8841 8850 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\&. 8842 8851 .sp 8843 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\&.8852 If disabled, Samba will send the string not_defined_in_RFC4178@please_ignore as the \*(Aqrfc4178 hint\*(Aq, following the updated RFC and Windows 2008 behaviour in this area\&. 8844 8853 .sp 8845 8854 Note that Windows XP SP2 and later versions already ignored this value in all circumstances\&. … … 8949 8958 .sp 8950 8959 Example: 8951 \fI\fIset primary group script\fR\fR\fI = \fR\fI/usr/sbin/usermod \-g \ '%g\' \'%u\'\fR\fI \fR8960 \fI\fIset primary group script\fR\fR\fI = \fR\fI/usr/sbin/usermod \-g \*(Aq%g\*(Aq \*(Aq%u\*(Aq\fR\fI \fR 8952 8961 .RE 8953 8962 … … 9550 9559 .RE 9551 9560 Those marked with a 9552 \fI\ '*\'\fR9553 take an integer argument\&. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don\ 't specify 1 or 0\&.9561 \fI\*(Aq*\*(Aq\fR 9562 take an integer argument\&. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don\*(Aqt specify 1 or 0\&. 9554 9563 .sp 9555 9564 To specify an argument use the syntax SOME_OPTION = VALUE for example … … 9634 9643 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\&. 9635 9644 .sp 9636 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\&.9637 .sp 9638 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\&.9645 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\*(Aqt 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\&. 9646 .sp 9647 When you have an extent based filesystem it\*(Aqs 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\&. 9639 9648 .sp 9640 9649 To give you an idea on which filesystems this setting might currently be a good option for you: XFS, ext4, btrfs, ocfs2 on Linux and JFS2 on AIX support unwritten extents\&. On Filesystems that do not support it, preallocation is probably an expensive operation where you will see reduced performance and risk to let clients run into timeouts when creating large files\&. Examples are ext3, ZFS, HFS+ and most others, so be aware if you activate this setting on those filesystems\&. … … 9687 9696 The administrator must create a directory name 9688 9697 svcctl 9689 in Samba\ 's $(libdir) and create symbolic links to the init scripts in9698 in Samba\*(Aqs $(libdir) and create symbolic links to the init scripts in 9690 9699 /etc/init\&.d/\&. The name of the links must match the names given as part of the 9691 9700 \fIsvcctl list\fR\&. … … 9704 9713 This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns\&. If this is 9705 9714 \fBno\fR 9706 then the server will be guided by the client\ 's request in each write call (clients can set a bit indicating that a particular write should be synchronous)\&. If this is9715 then the server will be guided by the client\*(Aqs request in each write call (clients can set a bit indicating that a particular write should be synchronous)\&. If this is 9707 9716 \fByes\fR 9708 9717 then every write will be followed by a … … 9756 9765 daemon uses this parameter to fill in the home directory for that user\&. If the string 9757 9766 \fI%D\fR 9758 is present it is substituted with the user\ 's Windows NT domain name\&. If the string9767 is present it is substituted with the user\*(Aqs Windows NT domain name\&. If the string 9759 9768 \fI%U\fR 9760 is present it is substituted with the user\ 's Windows NT user name\&.9769 is present it is substituted with the user\*(Aqs Windows NT user name\&. 9761 9770 .sp 9762 9771 Default: … … 9895 9904 .PP 9896 9905 .RS 4 9897 This option helps Samba to try and \ 'guess\'at the real UNIX username, as many DOS clients send an all\-uppercase username\&. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine\&.9906 This option helps Samba to try and \*(Aqguess\*(Aq at the real UNIX username, as many DOS clients send an all\-uppercase username\&. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine\&. 9898 9907 .sp 9899 9908 If this parameter is set to non\-zero the behavior changes\&. This parameter is a number that specifies the number of uppercase combinations to try while trying to determine the UNIX user name\&. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be\&. Use this parameter when you have strange usernames on your UNIX machine, such as … … 9956 9965 DOMAIN\efoo)\&. 9957 9966 .sp 9958 The map file is parsed line by line\&. Each line should contain a single UNIX username on the left then a \ '=\' followed by a list of usernames on the right\&. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group\&. The special client name \'*\'is a wildcard and matches any name\&. Each line of the map file may be up to 1023 characters long\&.9959 .sp 9960 The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the \ '=\'signs\&. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left\&. Processing then continues with the next line\&.9961 .sp 9962 If any line begins with a \ '#\' or a \';\'then it is ignored\&.9963 .sp 9964 If any line begins with an \ '!\' then the processing will stop after that line if a mapping was done by the line\&. Otherwise mapping continues with every line being processed\&. Using \'!\'is most useful when you have a wildcard mapping line later in the file\&.9967 The map file is parsed line by line\&. Each line should contain a single UNIX username on the left then a \*(Aq=\*(Aq followed by a list of usernames on the right\&. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group\&. The special client name \*(Aq*\*(Aq is a wildcard and matches any name\&. Each line of the map file may be up to 1023 characters long\&. 9968 .sp 9969 The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the \*(Aq=\*(Aq signs\&. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left\&. Processing then continues with the next line\&. 9970 .sp 9971 If any line begins with a \*(Aq#\*(Aq or a \*(Aq;\*(Aq then it is ignored\&. 9972 .sp 9973 If any line begins with an \*(Aq!\*(Aq then the processing will stop after that line if a mapping was done by the line\&. Otherwise mapping continues with every line being processed\&. Using \*(Aq!\*(Aq is most useful when you have a wildcard mapping line later in the file\&. 9965 9974 .sp 9966 9975 For example to map from the name … … 10018 10027 would map the windows username "Andrew Tridgell" to the unix username "tridge"\&. 10019 10028 .sp 10020 The following example would map mary and fred to the unix user sys, and map the rest to guest\&. Note the use of the \ '!\'to tell Samba to stop processing if it gets a match on that line:10029 The following example would map mary and fred to the unix user sys, and map the rest to guest\&. Note the use of the \*(Aq!\*(Aq to tell Samba to stop processing if it gets a match on that line: 10021 10030 .sp 10022 10031 .if n \{\ … … 10042 10051 (if you have one)\&. The password server will receive whatever username the client supplies without modification\&. 10043 10052 .sp 10044 Also note that no reverse mapping is done\&. The main effect this has is with printing\&. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don\ 't own the print job\&.10053 Also note that no reverse mapping is done\&. The main effect this has is with printing\&. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don\*(Aqt own the print job\&. 10045 10054 .sp 10046 10055 Samba versions prior to 3\&.0\&.8 would only support reading the fully qualified username (e\&.g\&.: … … 10108 10117 parameter\&. 10109 10118 .sp 10110 If any of the usernames begin with a \ '@\'then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&.10111 .sp 10112 If any of the usernames begin with a \ '+\'then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&.10113 .sp 10114 If any of the usernames begin with a \ '&\'then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\&.10119 If any of the usernames begin with a \*(Aq@\*(Aq then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&. 10120 .sp 10121 If any of the usernames begin with a \*(Aq+\*(Aq then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&. 10122 .sp 10123 If any of the usernames begin with a \*(Aq&\*(Aq then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\&. 10115 10124 .sp 10116 10125 Note that searching though a groups database can take quite some time, and some clients may time out during the search\&. … … 10191 10200 .PP 10192 10201 .RS 4 10193 This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions\&. If the pathname to be exported doesn\ 't start with one of the strings in this list, the user defined share will not be allowed\&. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares\&.10202 This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions\&. If the pathname to be exported doesn\*(Aqt start with one of the strings in this list, the user defined share will not be allowed\&. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares\&. 10194 10203 .sp 10195 10204 If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation\&. … … 10239 10248 \fByes\fR, and the 10240 10249 \fBsendfile()\fR 10241 system call is supported by the underlying operating system, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\&. This may make more efficient use of the system CPU\ 's and cause Samba to be faster\&. Samba automatically turns this off for clients that use protocol levels lower than NT LM 0\&.12 and when it detects a client is Windows 9x (using sendfile from Linux will cause these clients to fail)\&.10250 system call is supported by the underlying operating system, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\&. This may make more efficient use of the system CPU\*(Aqs and cause Samba to be faster\&. Samba automatically turns this off for clients that use protocol levels lower than NT LM 0\&.12 and when it detects a client is Windows 9x (using sendfile from Linux will cause these clients to fail)\&. 10242 10251 .sp 10243 10252 Default: … … 10292 10301 .PP 10293 10302 .RS 4 10294 This is a list of users that should be allowed to login to this service\&. Names starting with \ '@\', \'+\' and \'&\'are interpreted using the same rules as described in the10303 This is a list of users that should be allowed to login to this service\&. Names starting with \*(Aq@\*(Aq, \*(Aq+\*(Aq and \*(Aq&\*(Aq are interpreted using the same rules as described in the 10295 10304 \fIinvalid users\fR 10296 10305 parameter\&. … … 10326 10335 .PP 10327 10336 .RS 4 10328 This is a list of files and directories that are neither visible nor accessible\&. Each entry in the list must be separated by a \ '/\', which allows spaces to be included in the entry\&. \'*\' and \'?\'can be used to specify multiple files or directories as in DOS wildcards\&.10337 This is a list of files and directories that are neither visible nor accessible\&. Each entry in the list must be separated by a \*(Aq/\*(Aq, which allows spaces to be included in the entry\&. \*(Aq*\*(Aq and \*(Aq?\*(Aq can be used to specify multiple files or directories as in DOS wildcards\&. 10329 10338 .sp 10330 10339 Each entry must be a unix path, not a DOS path and must 10331 10340 \fInot\fR 10332 include the unix directory separator \ '/\'\&.10341 include the unix directory separator \*(Aq/\*(Aq\&. 10333 10342 .sp 10334 10343 Note that the … … 10336 10345 option is applicable in vetoing files\&. 10337 10346 .sp 10338 One feature of the veto files parameter that it is important to be aware of is Samba\ 's behaviour when trying to delete a directory\&. If a directory that is to be deleted contains nothing but veto files this deletion will10347 One feature of the veto files parameter that it is important to be aware of is Samba\*(Aqs behaviour when trying to delete a directory\&. If a directory that is to be deleted contains nothing but veto files this deletion will 10339 10348 \fIfail\fR 10340 10349 unless you also set the … … 10584 10593 .PP 10585 10594 .RS 4 10586 If set to yes, this parameter activates the support for nested groups\&. Nested groups are also called local groups or aliases\&. They work like their counterparts in Windows: Nested groups are defined locally on any machine (they are shared between DC\ 's through their SAM) and can contain users and global groups from any trusted SAM\&. To be able to use nested groups, you need to run nss_winbind\&.10595 If set to yes, this parameter activates the support for nested groups\&. Nested groups are also called local groups or aliases\&. They work like their counterparts in Windows: Nested groups are defined locally on any machine (they are shared between DC\*(Aqs through their SAM) and can contain users and global groups from any trusted SAM\&. To be able to use nested groups, you need to run nss_winbind\&. 10587 10596 .sp 10588 10597 Default: … … 10609 10618 .PP 10610 10619 .RS 4 10611 This parameter is designed to control how Winbind retrieves Name Service Information to construct a user\ 's home directory and login shell\&. Currently the following settings are available:10620 This parameter is designed to control how Winbind retrieves Name Service Information to construct a user\*(Aqs home directory and login shell\&. Currently the following settings are available: 10612 10621 .sp 10613 10622 .RS 4 … … 10717 10726 .sp 10718 10727 Default: 10719 \fI\fIwinbind separator\fR\fR\fI = \fR\fI\ '\e\'\fR\fI \fR10728 \fI\fIwinbind separator\fR\fR\fI = \fR\fI\*(Aq\e\*(Aq\fR\fI \fR 10720 10729 .sp 10721 10730 Example: … … 10727 10736 .PP 10728 10737 .RS 4 10729 This parameter is designed to allow Samba servers that are members of a Samba controlled domain to use UNIX accounts distributed via NIS, rsync, or LDAP as the uid\ 's for winbindd users in the hosts primary domain\&. Therefore, the user10738 This parameter is designed to allow Samba servers that are members of a Samba controlled domain to use UNIX accounts distributed via NIS, rsync, or LDAP as the uid\*(Aqs for winbindd users in the hosts primary domain\&. Therefore, the user 10730 10739 DOMAIN\euser1 10731 10740 would be mapped to the account user1 in /etc/passwd instead of allocating a new uid for him or her\&. … … 10745 10754 This parameter specifies whether the 10746 10755 \fBwinbindd\fR(8) 10747 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\&.10756 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\*(Aqs 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\&. 10748 10757 .sp 10749 10758 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\&. … … 10849 10858 This specifies the IP address (or DNS name: IP address for preference) of the WINS server that 10850 10859 \fBnmbd\fR(8) 10851 should register with\&. If you have a WINS server on your network then you should set this to the WINS server\ 's IP\&.10860 should register with\&. If you have a WINS server on your network then you should set this to the WINS server\*(Aqs IP\&. 10852 10861 .sp 10853 10862 You should point this at your WINS server if you have a multi\-subnetted network\&. 10854 10863 .sp 10855 If you want to work in multiple namespaces, you can give every wins server a \ 'tag\'\&. For each tag, only one (working) server will be queried for a name\&. The tag should be separated from the ip address by a colon\&.10864 If you want to work in multiple namespaces, you can give every wins server a \*(Aqtag\*(Aq\&. For each tag, only one (working) server will be queried for a name\&. The tag should be separated from the ip address by a colon\&. 10856 10865 .if n \{\ 10857 10866 .sp … … 10875 10884 .sp 10876 10885 Example: 10877 \fI\fIwins server\fR\fR\fI = \fR\fImary:192\&.9\&.200\&.1 fred:192\&.168\&.3\&.199 mary:192\&.168\&.2\&.61 # For this example when querying a certain name, 192\&.19\&.200\&.1 will be asked first and if that doesn\ 't respond 192\&.168\&.2\&.61\&. If either of those doesn\'t know the name 192\&.168\&.3\&.199 will be queried\&.\fR\fI \fR10886 \fI\fIwins server\fR\fR\fI = \fR\fImary:192\&.9\&.200\&.1 fred:192\&.168\&.3\&.199 mary:192\&.168\&.2\&.61 # For this example when querying a certain name, 192\&.19\&.200\&.1 will be asked first and if that doesn\*(Aqt respond 192\&.168\&.2\&.61\&. If either of those doesn\*(Aqt know the name 192\&.168\&.3\&.199 will be queried\&.\fR\fI \fR 10878 10887 .sp 10879 10888 Example: … … 10979 10988 .PP 10980 10989 .RS 4 10981 This parameter controls whether or not the server will support raw write SMB\ 's when transferring data from clients\&. You should never need to change this parameter\&.10990 This parameter controls whether or not the server will support raw write SMB\*(Aqs when transferring data from clients\&. You should never need to change this parameter\&. 10982 10991 .sp 10983 10992 Default: … … 11004 11013 .SH "WARNINGS" 11005 11014 .PP 11006 Although the configuration file permits service names to contain spaces, your client software may not\&. Spaces will be ignored in comparisons anyway, so it shouldn\ 't be a problem \- but be aware of the possibility\&.11015 Although the configuration file permits service names to contain spaces, your client software may not\&. Spaces will be ignored in comparisons anyway, so it shouldn\*(Aqt be a problem \- but be aware of the possibility\&. 11007 11016 .PP 11008 11017 On a similar note, many clients \- especially DOS clients \- limit service names to eight characters\&.
Note:
See TracChangeset
for help on using the changeset viewer.