1 .TH "smb\&.conf " "5" "23 Oct 1998" "Samba" "SAMBA"
4 smb\&.conf \- The configuration file for the Samba suite
8 \fBsmb\&.conf\fP The \fBsmb\&.conf\fP file is a configuration file for the
9 Samba suite\&. \fBsmb\&.conf\fP contains runtime configuration information
10 for the Samba programs\&. The \fBsmb\&.conf\fP file is designed to be
11 configured and administered by the \fBswat (8)\fP
12 program\&. The complete description of the file format and possible
13 parameters held within are here for reference purposes\&.
17 The file consists of sections and parameters\&. A section begins with
18 the name of the section in square brackets and continues until the
19 next section begins\&. Sections contain parameters of the form
21 \f(CW\'name = value\'\fP
23 The file is line-based - that is, each newline-terminated line
24 represents either a comment, a section name or a parameter\&.
26 Section and parameter names are not case sensitive\&.
28 Only the first equals sign in a parameter is significant\&. Whitespace
29 before or after the first equals sign is discarded\&. Leading, trailing
30 and internal whitespace in section and parameter names is
31 irrelevant\&. Leading and trailing whitespace in a parameter value is
32 discarded\&. Internal whitespace within a parameter value is retained
35 Any line beginning with a semicolon (\';\') or a hash (\'#\') character is
36 ignored, as are lines containing only whitespace\&.
38 Any line ending in a \f(CW\'\e\'\fP is "continued" on the next line in the
39 customary UNIX fashion\&.
41 The values following the equals sign in parameters are all either a
42 string (no quotes needed) or a boolean, which may be given as yes/no,
43 0/1 or true/false\&. Case is not significant in boolean values, but is
44 preserved in string values\&. Some items such as create modes are
47 .SH "SECTION DESCRIPTIONS"
49 Each section in the configuration file (except for the
50 \fB[global]\fP section) describes a shared resource (known
51 as a \fI"share"\fP)\&. The section name is the name of the shared resource
52 and the parameters within the section define the shares attributes\&.
54 There are three special sections, \fB[global]\fP,
55 \fB[homes]\fP and \fB[printers]\fP, which are
56 described under \fB\'special sections\'\fP\&. The
57 following notes apply to ordinary section descriptions\&.
59 A share consists of a directory to which access is being given plus
60 a description of the access rights which are granted to the user of
61 the service\&. Some housekeeping options are also specifiable\&.
63 Sections are either filespace services (used by the client as an
64 extension of their native file systems) or printable services (used by
65 the client to access print services on the host running the server)\&.
67 Sections may be designated \fBguest\fP services, in which
68 case no password is required to access them\&. A specified UNIX
69 \fBguest account\fP is used to define access
70 privileges in this case\&.
72 Sections other than guest services will require a password to access
73 them\&. The client provides the username\&. As older clients only provide
74 passwords and not usernames, you may specify a list of usernames to
75 check against the password using the \fB"user="\fP option in
76 the share definition\&. For modern clients such as Windows 95/98 and
77 Windows NT, this should not be necessary\&.
79 Note that the access rights granted by the server are masked by the
80 access rights granted to the specified or guest UNIX user by the host
81 system\&. The server does not grant more access than the host system
84 The following sample section defines a file space share\&. The user has
85 write access to the path \f(CW/home/bar\fP\&. The share is accessed via
102 The following sample section defines a printable share\&. The share
103 is readonly, but printable\&. That is, the only write access permitted
104 is via calls to open, write to and close a spool file\&. The
105 \fB\'guest ok\'\fP parameter means access will be permitted
106 as the default guest user (specified elsewhere):
113 path = /usr/spool/public
122 .SH "SPECIAL SECTIONS"
125 .IP "\fBThe [global] section\fP"
127 Parameters in this section apply to the server as a whole, or are
128 defaults for sections which do not specifically define certain
129 items\&. See the notes under \fB\'PARAMETERS\'\fP for more
132 .IP "\fBThe [homes] section\fP"
134 If a section called \f(CW\'homes\'\fP is included in the configuration file,
135 services connecting clients to their home directories can be created
136 on the fly by the server\&.
138 When the connection request is made, the existing sections are
139 scanned\&. If a match is found, it is used\&. If no match is found, the
140 requested section name is treated as a user name and looked up in the
141 local password file\&. If the name exists and the correct password has
142 been given, a share is created by cloning the [homes] section\&.
144 Some modifications are then made to the newly created share:
148 The share name is changed from \f(CW\'homes\'\fP to the located
152 If no path was given, the path is set to the user\'s home
156 If you decide to use a \fBpath=\fP line in your [homes]
157 section then you may find it useful to use the \fB%S\fP
158 macro\&. For example :
160 \f(CWpath=/data/pchome/%S\fP
162 would be useful if you have different home directories for your PCs
163 than for UNIX access\&.
165 This is a fast and simple way to give a large number of clients access
166 to their home directories with a minimum of fuss\&.
168 A similar process occurs if the requested section name is \f(CW"homes"\fP,
169 except that the share name is not changed to that of the requesting
170 user\&. This method of using the [homes] section works well if different
171 users share a client PC\&.
173 The [homes] section can specify all the parameters a normal service
174 section can specify, though some make more sense than others\&. The
175 following is a typical and suitable [homes] section:
188 An important point is that if guest access is specified in the [homes]
189 section, all home directories will be visible to all clients
190 \fBwithout a password\fP\&. In the very unlikely event that this is
191 actually desirable, it would be wise to also specify \fBread only
194 Note that the \fBbrowseable\fP flag for auto home
195 directories will be inherited from the global browseable flag, not the
196 [homes] browseable flag\&. This is useful as it means setting
197 browseable=no in the [homes] section will hide the [homes] share but
198 make any auto home directories visible\&.
200 .IP "\fBThe [printers] section\fP"
202 This section works like \fB[homes]\fP, but for printers\&.
204 If a [printers] section occurs in the configuration file, users are
205 able to connect to any printer specified in the local host\'s printcap
208 When a connection request is made, the existing sections are
209 scanned\&. If a match is found, it is used\&. If no match is found, but a
210 \fB[homes]\fP section exists, it is used as described
211 above\&. Otherwise, the requested section name is treated as a printer
212 name and the appropriate printcap file is scanned to see if the
213 requested section name is a valid printer share name\&. If a match is
214 found, a new printer share is created by cloning the [printers]
217 A few modifications are then made to the newly created share:
221 The share name is set to the located printer name
224 If no printer name was given, the printer name is set to the
228 If the share does not permit guest access and no username was
229 given, the username is set to the located printer name\&.
232 Note that the [printers] service MUST be printable - if you specify
233 otherwise, the server will refuse to load the configuration file\&.
235 Typically the path specified would be that of a world-writeable spool
236 directory with the sticky bit set on it\&. A typical [printers] entry
237 would look like this:
244 path = /usr/spool/public
252 All aliases given for a printer in the printcap file are legitimate
253 printer names as far as the server is concerned\&. If your printing
254 subsystem doesn\'t work like that, you will have to set up a
255 pseudo-printcap\&. This is a file consisting of one or more lines like
261 alias|alias|alias|alias\&.\&.\&.
266 Each alias should be an acceptable printer name for your printing
267 subsystem\&. In the \fB[global]\fP section, specify the new
268 file as your printcap\&. The server will then only recognize names
269 found in your pseudo-printcap, which of course can contain whatever
270 aliases you like\&. The same technique could be used simply to limit
271 access to a subset of your local printers\&.
273 An alias, by the way, is defined as any component of the first entry
274 of a printcap record\&. Records are separated by newlines, components
275 (if there are more than one) are separated by vertical bar symbols
278 NOTE: On SYSV systems which use lpstat to determine what printers are
279 defined on the system you may be able to use \fB"printcap name =
280 lpstat"\fP to automatically obtain a list of
281 printers\&. See the \fB"printcap name"\fP option for
287 Parameters define the specific attributes of sections\&.
289 Some parameters are specific to the \fB[global]\fP section
290 (e\&.g\&., \fBsecurity\fP)\&. Some parameters are usable in
291 all sections (e\&.g\&., \fBcreate mode\fP)\&. All others are
292 permissible only in normal sections\&. For the purposes of the following
293 descriptions the \fB[homes]\fP and
294 \fB[printers]\fP sections will be considered normal\&.
295 The letter \f(CW\'G\'\fP in parentheses indicates that a parameter is
296 specific to the \fB[global]\fP section\&. The letter \f(CW\'S\'\fP
297 indicates that a parameter can be specified in a service specific
298 section\&. Note that all \f(CW\'S\'\fP parameters can also be specified in the
299 \fB[global]\fP section - in which case they will define
300 the default behavior for all services\&.
302 Parameters are arranged here in alphabetical order - this may not
303 create best bedfellows, but at least you can find them! Where there
304 are synonyms, the preferred synonym is described, others refer to the
307 .SH "VARIABLE SUBSTITUTIONS"
309 Many of the strings that are settable in the config file can take
310 substitutions\&. For example the option \fB\f(CW"path =
311 /tmp/%u"\fP\fP would be interpreted as \f(CW"path = /tmp/john"\fP if
312 the user connected with the username john\&.
314 These substitutions are mostly noted in the descriptions below, but
315 there are some general substitutions which apply whenever they might
316 be relevant\&. These are:
320 \fB%S\fP = the name of the current service, if any\&.
323 \fB%P\fP = the root directory of the current service, if any\&.
326 \fB%u\fP = user name of the current service, if any\&.
329 \fB%g\fP = primary group name of \fB%u\fP\&.
332 \fB%U\fP = session user name (the user name that
333 the client wanted, not necessarily the same as the one they got)\&.
336 \fB%G\fP = primary group name of \fB%U\fP\&.
339 \fB%H\fP = the home directory of the user given by \fB%u\fP\&.
342 \fB%v\fP = the Samba version\&.
345 \fB%h\fP = the internet hostname that Samba is running on\&.
348 \fB%m\fP = the NetBIOS name of the client machine (very useful)\&.
351 \fB%L\fP = the NetBIOS name of the server\&. This allows you to change your
352 config based on what the client calls you\&. Your server can have a "dual
356 \fB%M\fP = the internet name of the client machine\&.
359 \fB%N\fP = the name of your NIS home directory server\&. This is
360 obtained from your NIS auto\&.map entry\&. If you have not compiled Samba
361 with the \fB--with-automount\fP option then this value will be the same
365 \fB%p\fP = the path of the service\'s home directory, obtained from your NIS
366 auto\&.map entry\&. The NIS auto\&.map entry is split up as "%N:%p"\&.
369 \fB%R\fP = the selected protocol level after protocol
370 negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\&.
373 \fB%d\fP = The process id of the current server process\&.
376 \fB%a\fP = the architecture of the remote
377 machine\&. Only some are recognized, and those may not be 100%
378 reliable\&. It currently recognizes Samba, WfWg, WinNT and
379 Win95\&. Anything else will be known as "UNKNOWN"\&. If it gets it wrong
380 then sending a level 3 log to \fIsamba-bugs@samba\&.org\fP
381 should allow it to be fixed\&.
384 \fB%I\fP = The IP address of the client machine\&.
387 \fB%T\fP = the current date and time\&.
390 There are some quite creative things that can be done with these
391 substitutions and other smb\&.conf options\&.
395 Samba supports \fI"name mangling"\fP so that DOS and Windows clients can
396 use files that don\'t conform to the 8\&.3 format\&. It can also be set to
397 adjust the case of 8\&.3 format filenames\&.
399 There are several options that control the way mangling is performed,
400 and they are grouped here rather than listed separately\&. For the
401 defaults look at the output of the testparm program\&.
403 All of these options can be set separately for each service (or
404 globally, of course)\&.
408 \fB"mangle case = yes/no"\fP controls if names that have characters that
409 aren\'t of the "default" case are mangled\&. For example, if this is yes
410 then a name like \f(CW"Mail"\fP would be mangled\&. Default \fIno\fP\&.
412 \fB"case sensitive = yes/no"\fP controls whether filenames are case
413 sensitive\&. If they aren\'t then Samba must do a filename search and
414 match on passed names\&. Default \fIno\fP\&.
416 \fB"default case = upper/lower"\fP controls what the default case is for new
417 filenames\&. Default \fIlower\fP\&.
419 \fB"preserve case = yes/no"\fP controls if new files are created with the
420 case that the client passes, or if they are forced to be the \f(CW"default"\fP
421 case\&. Default \fIYes\fP\&.
424 \fB"short preserve case = yes/no"\fP controls if new files which conform
425 to 8\&.3 syntax, that is all in upper case and of suitable length, are
426 created upper case, or if they are forced to be the \f(CW"default"\fP
427 case\&. This option can be use with \fB"preserve case =
428 yes"\fP to permit long filenames to retain their
429 case, while short names are lowered\&. Default \fIYes\fP\&.
431 By default, Samba 2\&.0 has the same semantics as a Windows NT
432 server, in that it is case insensitive but case preserving\&.
434 .SH "NOTE ABOUT USERNAME/PASSWORD VALIDATION"
436 There are a number of ways in which a user can connect to a
437 service\&. The server follows the following steps in determining if it
438 will allow a connection to a specified service\&. If all the steps fail
439 then the connection request is rejected\&. If one of the steps pass then
440 the following steps are not checked\&.
442 If the service is marked \fB"guest only = yes"\fP then
443 steps 1 to 5 are skipped\&.
447 Step 1: If the client has passed a username/password pair and
448 that username/password pair is validated by the UNIX system\'s password
449 programs then the connection is made as that username\&. Note that this
450 includes the \f(CW\e\eserver\eservice%username\fP method of passing a
454 Step 2: If the client has previously registered a username with
455 the system and now supplies a correct password for that username then
456 the connection is allowed\&.
459 Step 3: The client\'s netbios name and any previously used user
460 names are checked against the supplied password, if they match then
461 the connection is allowed as the corresponding user\&.
464 Step 4: If the client has previously validated a
465 username/password pair with the server and the client has passed the
466 validation token then that username is used\&. This step is skipped if
467 \fB"revalidate = yes"\fP for this service\&.
470 Step 5: If a \fB"user = "\fP field is given in the
471 smb\&.conf file for the service and the client has supplied a password,
472 and that password matches (according to the UNIX system\'s password
473 checking) with one of the usernames from the \fBuser=\fP
474 field then the connection is made as the username in the
475 \fB"user="\fP line\&. If one of the username in the
476 \fBuser=\fP list begins with a \f(CW\'@\'\fP then that name
477 expands to a list of names in the group of the same name\&.
480 Step 6: If the service is a guest service then a connection is
481 made as the username given in the \fB"guest account
482 ="\fP for the service, irrespective of the supplied
486 .SH "COMPLETE LIST OF GLOBAL PARAMETERS"
488 Here is a list of all global parameters\&. See the section of each
489 parameter for details\&. Note that some are synonyms\&.
496 \fBannounce version\fP
502 \fBbind interfaces only\fP
508 \fBchange notify timeout\fP
514 \fBclient code page\fP
526 \fBdebug timestamp\fP
535 \fBdefault service\fP
544 \fBdomain admin group\fP
547 \fBdomain admin users\fP
550 \fBdomain controller\fP
553 \fBdomain group map\fP
559 \fBdomain guest group\fP
562 \fBdomain guest users\fP
571 \fBdomain user map\fP
574 \fBencrypt passwords\fP
598 \fBldap passwd file\fP
619 \fBlocal group map\fP
652 \fBmachine password timeout\fP
682 \fBmessage command\fP
688 \fBname resolve order\fP
691 \fBnetbios aliases\fP
700 \fBnt pipe support\fP
709 \fBole locking compatibility\fP
724 \fBpasswd chat debug\fP
733 \fBpassword server\fP
736 \fBprefered master\fP
739 \fBpreferred master\fP
751 \fBprinter driver file\fP
760 \fBread prediction\fP
769 \fBremote announce\fP
772 \fBremote browse sync\fP
790 \fBshared mem size\fP
793 \fBsmb passwd file\fP
811 \fBssl CA certFile\fP
817 \fBssl client cert\fP
823 \fBssl compatibility\fP
829 \fBssl hosts resign\fP
832 \fBssl require clientcert\fP
835 \fBssl require servercert\fP
838 \fBssl server cert\fP
850 \fBstat cache size\fP
871 \fBunix password sync\fP
877 \fBupdate encrypted\fP
907 .SH "COMPLETE LIST OF SERVICE PARAMETERS"
909 Here is a list of all service parameters\&. See the section of each
910 parameter for details\&. Note that some are synonyms\&.
920 \fBalternate permissions\fP
956 \fBdelete readonly\fP
959 \fBdelete veto files\fP
977 \fBdos filetime resolution\fP
986 \fBfake directory create times\fP
992 \fBfollow symlinks\fP
995 \fBforce create mode\fP
998 \fBforce directory mode\fP
1022 \fBhide dot files\fP
1043 \fBlppause command\fP
1049 \fBlpresume command\fP
1085 \fBmax connections\fP
1088 \fBmin print space\fP
1127 \fBprinter driver\fP
1130 \fBprinter driver location\fP
1142 \fBqueuepause command\fP
1145 \fBqueueresume command\fP
1169 \fBshort preserve case\fP
1175 \fBstrict locking\fP
1199 \fBveto oplock files\fP
1220 .SH "EXPLANATION OF EACH PARAMETER"
1223 .IP "\fBadmin users (S)\fP"
1225 This is a list of users who will be granted administrative privileges
1226 on the share\&. This means that they will do all file operations as the
1227 super-user (root)\&.
1229 You should use this option very carefully, as any user in this list
1230 will be able to do anything they like on the share, irrespective of
1235 \f(CW no admin users\fP
1239 \f(CW admin users = jason\fP
1241 .IP "\fBallow hosts (S)\fP"
1243 A synonym for this parameter is \fB\'hosts allow\'\fP
1245 This parameter is a comma, space, or tab delimited set of hosts which
1246 are permitted to access a service\&.
1248 If specified in the \fB[global]\fP section then it will
1249 apply to all services, regardless of whether the individual service
1250 has a different setting\&.
1252 You can specify the hosts by name or IP number\&. For example, you could
1253 restrict access to only the hosts on a Class C subnet with something
1254 like \f(CW"allow hosts = 150\&.203\&.5\&."\fP\&. The full syntax of the list is
1255 described in the man page \fBhosts_access (5)\fP\&. Note that this man
1256 page may not be present on your system, so a brief description will
1257 be given here also\&.
1259 \fINOTE:\fP IF you wish to allow the \fBsmbpasswd
1260 (8)\fP program to be run by local users to change
1261 their Samba passwords using the local \fBsmbd (8)\fP
1262 daemon, then you \fIMUST\fP ensure that the localhost is listed in your
1263 \fBallow hosts\fP list, as \fBsmbpasswd (8)\fP runs
1264 in client-server mode and is seen by the local
1265 \fBsmbd\fP process as just another client\&.
1267 You can also specify hosts by network/netmask pairs and by netgroup
1268 names if your system supports netgroups\&. The \fIEXCEPT\fP keyword can also
1269 be used to limit a wildcard list\&. The following examples may provide
1272 \fBExample 1\fP: allow localhost and all IPs in 150\&.203\&.*\&.* except one
1274 \f(CW hosts allow = localhost, 150\&.203\&. EXCEPT 150\&.203\&.6\&.66\fP
1276 \fBExample 2\fP: allow localhost and hosts that match the given network/netmask
1278 \f(CW hosts allow = localhost, 150\&.203\&.15\&.0/255\&.255\&.255\&.0\fP
1280 \fBExample 3\fP: allow a localhost plus a couple of hosts
1282 \f(CW hosts allow = localhost, lapland, arvidsjaur\fP
1284 \fBExample 4\fP: allow only hosts in NIS netgroup "foonet" or localhost, but
1285 deny access from one particular host
1287 \f(CW hosts allow = @foonet, localhost\fP
1288 \f(CW hosts deny = pirate\fP
1290 Note that access still requires suitable user-level passwords\&.
1292 See \fBtestparm (1)\fP for a way of testing your
1293 host access to see if it does what you expect\&.
1296 \f(CW none (i\&.e\&., all hosts permitted access)\fP
1299 \f(CW allow hosts = 150\&.203\&.5\&. localhost myhost\&.mynet\&.edu\&.au\fP
1301 .IP "\fBalternate permissions (S)\fP"
1303 This is a deprecated parameter\&. It no longer has any effect in Samba2\&.0\&.
1304 In previous versions of Samba it affected the way the DOS "read only"
1305 attribute was mapped for a file\&. In Samba2\&.0 a file is marked "read only"
1306 if the UNIX file does not have the \'w\' bit set for the owner of the file,
1307 regardless if the owner of the file is the currently logged on user or not\&.
1309 .IP "\fBannounce as (G)\fP"
1311 This specifies what type of server \fBnmbd\fP will
1312 announce itself as, to a network neighborhood browse list\&. By default
1313 this is set to Windows NT\&. The valid options are : "NT", "Win95" or
1314 "WfW" meaning Windows NT, Windows 95 and Windows for Workgroups
1315 respectively\&. Do not change this parameter unless you have a specific
1316 need to stop Samba appearing as an NT server as this may prevent Samba
1317 servers from participating as browser servers correctly\&.
1320 \f(CW announce as = NT\fP
1323 \f(CW announce as = Win95\fP
1325 .IP "\fBannounce version (G)\fP"
1327 This specifies the major and minor version numbers that nmbd will use
1328 when announcing itself as a server\&. The default is 4\&.2\&. Do not change
1329 this parameter unless you have a specific need to set a Samba server
1330 to be a downlevel server\&.
1333 \f(CW announce version = 4\&.2\fP
1336 \f(CW announce version = 2\&.0\fP
1338 .IP "\fBauto services (G)\fP"
1340 This is a list of services that you want to be automatically added to
1341 the browse lists\&. This is most useful for homes and printers services
1342 that would otherwise not be visible\&.
1344 Note that if you just want all printers in your printcap file loaded
1345 then the \fB"load printers"\fP option is easier\&.
1348 \f(CW no auto services\fP
1351 \f(CW auto services = fred lp colorlp\fP
1353 .IP "\fBavailable (S)\fP"
1355 This parameter lets you \fI\'turn off\'\fP a service\&. If \f(CW\'available = no\'\fP,
1356 then \fIALL\fP attempts to connect to the service will fail\&. Such failures
1360 \f(CW available = yes\fP
1363 \f(CW available = no\fP
1365 .IP "\fBbind interfaces only (G)\fP"
1367 This global parameter allows the Samba admin to limit what interfaces
1368 on a machine will serve smb requests\&. If affects file service
1369 \fBsmbd\fP and name service \fBnmbd\fP
1370 in slightly different ways\&.
1372 For name service it causes \fBnmbd\fP to bind to ports
1373 137 and 138 on the interfaces listed in the
1374 \fB\'interfaces\'\fP
1375 parameter\&. \fBnmbd\fP also binds to the \'all
1376 addresses\' interface (0\&.0\&.0\&.0) on ports 137 and 138 for the purposes
1377 of reading broadcast messages\&. If this option is not set then
1378 \fBnmbd\fP will service name requests on all of these
1379 sockets\&. If \fB"bind interfaces only"\fP is set then
1380 \fBnmbd\fP will check the source address of any
1381 packets coming in on the broadcast sockets and discard any that don\'t
1382 match the broadcast addresses of the interfaces in the
1383 \fB\'interfaces\'\fP parameter list\&. As unicast packets
1384 are received on the other sockets it allows \fBnmbd\fP
1385 to refuse to serve names to machines that send packets that arrive
1386 through any interfaces not listed in the
1387 \fB"interfaces"\fP list\&. IP Source address spoofing
1388 does defeat this simple check, however so it must not be used
1389 seriously as a security feature for \fBnmbd\fP\&.
1391 For file service it causes \fBsmbd\fP to bind only to
1392 the interface list given in the \fB\'interfaces\'\fP
1393 parameter\&. This restricts the networks that \fBsmbd\fP
1394 will serve to packets coming in those interfaces\&. Note that you
1395 should not use this parameter for machines that are serving PPP or
1396 other intermittent or non-broadcast network interfaces as it will not
1397 cope with non-permanent interfaces\&.
1399 In addition, to change a users SMB password, the
1400 \fBsmbpasswd\fP by default connects to the
1401 \fI"localhost" - 127\&.0\&.0\&.1\fP address as an SMB client to issue the
1402 password change request\&. If \fB"bind interfaces only"\fP is set then
1403 unless the network address \fI127\&.0\&.0\&.1\fP is added to the
1404 \fB\'interfaces\'\fP parameter list then
1405 \fBsmbpasswd\fP will fail to connect in it\'s
1406 default mode\&. \fBsmbpasswd\fP can be forced to
1407 use the primary IP interface of the local host by using its
1408 \fB"-r remote machine"\fP parameter, with
1409 \fB"remote machine"\fP set to the IP name of the primary interface
1410 of the local host\&.
1413 \f(CW bind interfaces only = False\fP
1416 \f(CW bind interfaces only = True\fP
1418 .IP "\fBblocking locks (S)\fP"
1420 This parameter controls the behavior of \fBsmbd\fP when
1421 given a request by a client to obtain a byte range lock on a region
1422 of an open file, and the request has a time limit associated with it\&.
1424 If this parameter is set and the lock range requested cannot be
1425 immediately satisfied, Samba 2\&.0 will internally queue the lock
1426 request, and periodically attempt to obtain the lock until the
1427 timeout period expires\&.
1429 If this parameter is set to "False", then Samba 2\&.0 will behave
1430 as previous versions of Samba would and will fail the lock
1431 request immediately if the lock range cannot be obtained\&.
1433 This parameter can be set per share\&.
1436 \f(CW blocking locks = True\fP
1439 \f(CW blocking locks = False\fP
1441 .IP "\fBbrowsable (S)\fP"
1443 Synonym for \fBbrowseable\fP\&.
1445 .IP "\fBbrowse list(G)\fP"
1447 This controls whether \fBsmbd\fP will serve a browse
1448 list to a client doing a NetServerEnum call\&. Normally set to true\&. You
1449 should never need to change this\&.
1452 \f(CW browse list = Yes\fP
1454 .IP "\fBbrowseable\fP"
1456 This controls whether this share is seen in the list of available
1457 shares in a net view and in the browse list\&.
1460 \f(CW browseable = Yes\fP
1463 \f(CW browseable = No\fP
1465 .IP "\fBcase sensitive (S)\fP"
1467 See the discussion in the section \fBNAME MANGLING\fP\&.
1469 .IP "\fBcasesignames (S)\fP"
1471 Synonym for \fB"case sensitive"\fP\&.
1473 .IP "\fBchange notify timeout (G)\fP"
1475 One of the new NT SMB requests that Samba 2\&.0 supports is the
1476 "ChangeNotify" requests\&. This SMB allows a client to tell a server to
1477 \fI"watch"\fP a particular directory for any changes and only reply to
1478 the SMB request when a change has occurred\&. Such constant scanning of
1479 a directory is expensive under UNIX, hence an
1480 \fBsmbd\fP daemon only performs such a scan on each
1481 requested directory once every \fBchange notify timeout\fP seconds\&.
1483 \fBchange notify timeout\fP is specified in units of seconds\&.
1486 \f(CW change notify timeout = 60\fP
1489 \f(CW change notify timeout = 300\fP
1491 Would change the scan time to every 5 minutes\&.
1493 .IP "\fBcharacter set (G)\fP"
1495 This allows a smbd to map incoming filenames from a DOS Code page (see
1496 the \fBclient code page\fP parameter) to several
1497 built in UNIX character sets\&. The built in code page translations are:
1501 \fBISO8859-1\fP Western European UNIX character set\&. The parameter
1502 \fBclient code page\fP \fIMUST\fP be set to code
1503 page 850 if the \fBcharacter set\fP parameter is set to iso8859-1
1504 in order for the conversion to the UNIX character set to be done
1508 \fBISO8859-2\fP Eastern European UNIX character set\&. The parameter
1509 \fBclient code page\fP \fIMUST\fP be set to code
1510 page 852 if the \fBcharacter set\fP parameter is set to ISO8859-2
1511 in order for the conversion to the UNIX character set to be done
1515 \fBISO8859-5\fP Russian Cyrillic UNIX character set\&. The parameter
1516 \fBclient code page\fP \fIMUST\fP be set to code
1517 page 866 if the \fBcharacter set\fP parameter is set to ISO8859-2
1518 in order for the conversion to the UNIX character set to be done
1522 \fBKOI8-R\fP Alternate mapping for Russian Cyrillic UNIX
1523 character set\&. The parameter \fBclient code
1524 page\fP \fIMUST\fP be set to code page 866 if the
1525 \fBcharacter set\fP parameter is set to KOI8-R in order for the
1526 conversion to the UNIX character set to be done correctly\&.
1529 \fIBUG\fP\&. These MSDOS code page to UNIX character set mappings should
1530 be dynamic, like the loading of MS DOS code pages, not static\&.
1532 See also \fBclient code page\fP\&. Normally this
1533 parameter is not set, meaning no filename translation is done\&.
1536 \f(CW character set = <empty string>\fP
1539 \f(CW character set = ISO8859-1\fP
1541 .IP "\fBclient code page (G)\fP"
1543 This parameter specifies the DOS code page that the clients accessing
1544 Samba are using\&. To determine what code page a Windows or DOS client
1545 is using, open a DOS command prompt and type the command "chcp"\&. This
1546 will output the code page\&. The default for USA MS-DOS, Windows 95, and
1547 Windows NT releases is code page 437\&. The default for western european
1548 releases of the above operating systems is code page 850\&.
1550 This parameter tells \fBsmbd\fP which of the
1551 \f(CWcodepage\&.XXX\fP files to dynamically load on startup\&. These files,
1552 described more fully in the manual page \fBmake_smbcodepage
1553 (1)\fP, tell \fBsmbd\fP how
1554 to map lower to upper case characters to provide the case insensitivity
1555 of filenames that Windows clients expect\&.
1557 Samba currently ships with the following code page files :
1561 \fBCode Page 437 - MS-DOS Latin US\fP
1564 \fBCode Page 737 - Windows \'95 Greek\fP
1567 \fBCode Page 850 - MS-DOS Latin 1\fP
1570 \fBCode Page 852 - MS-DOS Latin 2\fP
1573 \fBCode Page 861 - MS-DOS Icelandic\fP
1576 \fBCode Page 866 - MS-DOS Cyrillic\fP
1579 \fBCode Page 932 - MS-DOS Japanese SJIS\fP
1582 \fBCode Page 936 - MS-DOS Simplified Chinese\fP
1585 \fBCode Page 949 - MS-DOS Korean Hangul\fP
1588 \fBCode Page 950 - MS-DOS Traditional Chinese\fP
1591 Thus this parameter may have any of the values 437, 737, 850, 852,
1592 861, 932, 936, 949, or 950\&. If you don\'t find the codepage you need,
1593 read the comments in one of the other codepage files and the
1594 \fBmake_smbcodepage (1)\fP man page and
1595 write one\&. Please remember to donate it back to the Samba user
1598 This parameter co-operates with the \fB"valid
1599 chars"\fP parameter in determining what characters are
1600 valid in filenames and how capitalization is done\&. If you set both
1601 this parameter and the \fB"valid chars"\fP parameter
1602 the \fB"client code page"\fP parameter \fIMUST\fP be set before the
1603 \fB"valid chars"\fP parameter in the \fBsmb\&.conf\fP
1604 file\&. The \fB"valid chars"\fP string will then augment
1605 the character settings in the "client code page" parameter\&.
1607 If not set, \fB"client code page"\fP defaults to 850\&.
1609 See also : \fB"valid chars"\fP
1612 \f(CW client code page = 850\fP
1615 \f(CW client code page = 936\fP
1617 .IP "\fBcodingsystem (G)\fP"
1619 This parameter is used to determine how incoming Shift-JIS Japanese
1620 characters are mapped from the incoming \fB"client code
1621 page"\fP used by the client, into file names in the
1622 UNIX filesystem\&. Only useful if \fB"client code
1623 page"\fP is set to 932 (Japanese Shift-JIS)\&.
1629 \fBSJIS\fP Shift-JIS\&. Does no conversion of the incoming filename\&.
1632 \fBJIS8, J8BB, J8BH, J8@B, J8@J, J8@H \fP Convert from incoming
1633 Shift-JIS to eight bit JIS code with different shift-in, shift out
1637 \fBJIS7, J7BB, J7BH, J7@B, J7@J, J7@H \fP Convert from incoming
1638 Shift-JIS to seven bit JIS code with different shift-in, shift out
1642 \fBJUNET, JUBB, JUBH, JU@B, JU@J, JU@H \fP Convert from incoming
1643 Shift-JIS to JUNET code with different shift-in, shift out codes\&.
1646 \fBEUC\fP Convert an incoming Shift-JIS character to EUC code\&.
1649 \fBHEX\fP Convert an incoming Shift-JIS character to a 3 byte hex
1650 representation, i\&.e\&. \f(CW:AB\fP\&.
1653 \fBCAP\fP Convert an incoming Shift-JIS character to the 3 byte hex
1654 representation used by the Columbia AppleTalk Program (CAP),
1655 i\&.e\&. \f(CW:AB\fP\&. This is used for compatibility between Samba and CAP\&.
1658 .IP "\fBcomment (S)\fP"
1660 This is a text field that is seen next to a share when a client does a
1661 queries the server, either via the network neighborhood or via "net
1662 view" to list what shares are available\&.
1664 If you want to set the string that is displayed next to the machine
1665 name then see the server string command\&.
1668 \f(CW No comment string\fP
1671 \f(CW comment = Fred\'s Files\fP
1673 .IP "\fBconfig file (G)\fP"
1675 This allows you to override the config file to use, instead of the
1676 default (usually \fBsmb\&.conf\fP)\&. There is a chicken and egg problem
1677 here as this option is set in the config file!
1679 For this reason, if the name of the config file has changed when the
1680 parameters are loaded then it will reload them from the new config
1683 This option takes the usual substitutions, which can be very useful\&.
1685 If the config file doesn\'t exist then it won\'t be loaded (allowing you
1686 to special case the config files of just a few clients)\&.
1689 \f(CW config file = /usr/local/samba/lib/smb\&.conf\&.%m\fP
1691 .IP "\fBcopy (S)\fP"
1693 This parameter allows you to \fI\'clone\'\fP service entries\&. The specified
1694 service is simply duplicated under the current service\'s name\&. Any
1695 parameters specified in the current section will override those in the
1696 section being copied\&.
1698 This feature lets you set up a \'template\' service and create similar
1699 services easily\&. Note that the service being copied must occur earlier
1700 in the configuration file than the service doing the copying\&.
1706 \f(CW copy = otherservice\fP
1708 .IP "\fBcreate mask (S)\fP"
1710 A synonym for this parameter is \fB\'create mode\'\fP\&.
1712 When a file is created, the necessary permissions are calculated
1713 according to the mapping from DOS modes to UNIX permissions, and the
1714 resulting UNIX mode is then bit-wise \'AND\'ed with this parameter\&.
1715 This parameter may be thought of as a bit-wise MASK for the UNIX modes
1716 of a file\&. Any bit \fI*not*\fP set here will be removed from the modes set
1717 on a file when it is created\&.
1719 The default value of this parameter removes the \'group\' and \'other\'
1720 write and execute bits from the UNIX modes\&.
1722 Following this Samba will bit-wise \'OR\' the UNIX mode created from
1723 this parameter with the value of the "force create mode" parameter
1724 which is set to 000 by default\&.
1726 This parameter does not affect directory modes\&. See the parameter
1727 \fB\'directory mode\'\fP for details\&.
1729 See also the \fB"force create mode"\fP parameter
1730 for forcing particular mode bits to be set on created files\&. See also
1731 the \fB"directory mode"\fP parameter for masking
1732 mode bits on created directories\&.
1735 \f(CW create mask = 0744\fP
1738 \f(CW create mask = 0775\fP
1740 .IP "\fBcreate mode (S)\fP"
1742 This is a synonym for \fBcreate mask\fP\&.
1744 .IP "\fBdeadtime (G)\fP"
1746 The value of the parameter (a decimal integer) represents the number
1747 of minutes of inactivity before a connection is considered dead, and
1748 it is disconnected\&. The deadtime only takes effect if the number of
1749 open files is zero\&.
1751 This is useful to stop a server\'s resources being exhausted by a large
1752 number of inactive connections\&.
1754 Most clients have an auto-reconnect feature when a connection is
1755 broken so in most cases this parameter should be transparent to users\&.
1757 Using this parameter with a timeout of a few minutes is recommended
1760 A deadtime of zero indicates that no auto-disconnection should be
1764 \f(CW deadtime = 0\fP
1767 \f(CW deadtime = 15\fP
1769 .IP "\fBdebug timestamp (G)\fP"
1771 Samba2\&.0 debug log messages are timestamped by default\&. If you are
1772 running at a high \fB"debug level"\fP these timestamps
1773 can be distracting\&. This boolean parameter allows them to be turned
1777 \f(CW debug timestamp = Yes\fP
1780 \f(CW debug timestamp = No\fP
1782 .IP "\fBdebug level (G)\fP"
1784 The value of the parameter (an integer) allows the debug level
1785 (logging level) to be specified in the \fBsmb\&.conf\fP file\&. This is to
1786 give greater flexibility in the configuration of the system\&.
1788 The default will be the debug level specified on the command line
1789 or level zero if none was specified\&.
1792 \f(CW debug level = 3\fP
1794 .IP "\fBdefault (G)\fP"
1796 A synonym for \fBdefault service\fP\&.
1798 .IP "\fBdefault case (S)\fP"
1800 See the section on \fB"NAME MANGLING"\fP\&. Also note
1801 the \fB"short preserve case"\fP parameter\&.
1803 .IP "\fBdefault service (G)\fP"
1805 This parameter specifies the name of a service which will be connected
1806 to if the service actually requested cannot be found\&. Note that the
1807 square brackets are \fINOT\fP given in the parameter value (see example
1810 There is no default value for this parameter\&. If this parameter is not
1811 given, attempting to connect to a nonexistent service results in an
1814 Typically the default service would be a \fBguest ok\fP,
1815 \fBread-only\fP service\&.
1817 Also note that the apparent service name will be changed to equal that
1818 of the requested service, this is very useful as it allows you to use
1819 macros like \fB%S\fP to make a wildcard service\&.
1821 Note also that any \f(CW\'_\'\fP characters in the name of the service used
1822 in the default service will get mapped to a \f(CW\'/\'\fP\&. This allows for
1823 interesting things\&.
1830 default service = pub
1839 .IP "\fBdelete readonly (S)\fP"
1841 This parameter allows readonly files to be deleted\&. This is not
1842 normal DOS semantics, but is allowed by UNIX\&.
1844 This option may be useful for running applications such as rcs, where
1845 UNIX file ownership prevents changing file permissions, and DOS
1846 semantics prevent deletion of a read only file\&.
1849 \f(CW delete readonly = No\fP
1852 \f(CW delete readonly = Yes\fP
1854 .IP "\fBdelete veto files (S)\fP"
1856 This option is used when Samba is attempting to delete a directory
1857 that contains one or more vetoed directories (see the \fB\'veto
1858 files\'\fP option)\&. If this option is set to False (the
1859 default) then if a vetoed directory contains any non-vetoed files or
1860 directories then the directory delete will fail\&. This is usually what
1863 If this option is set to True, then Samba will attempt to recursively
1864 delete any files and directories within the vetoed directory\&. This can
1865 be useful for integration with file serving systems such as \fBNetAtalk\fP,
1866 which create meta-files within directories you might normally veto
1867 DOS/Windows users from seeing (e\&.g\&. \f(CW\&.AppleDouble\fP)
1869 Setting \f(CW\'delete veto files = True\'\fP allows these directories to be
1870 transparently deleted when the parent directory is deleted (so long
1871 as the user has permissions to do so)\&.
1873 See also the \fBveto files\fP parameter\&.
1876 \f(CW delete veto files = False\fP
1879 \f(CW delete veto files = True\fP
1881 .IP "\fBdeny hosts (S)\fP"
1883 The opposite of \fB\'allow hosts\'\fP - hosts listed
1884 here are \fINOT\fP permitted access to services unless the specific
1885 services have their own lists to override this one\&. Where the lists
1886 conflict, the \fB\'allow\'\fP list takes precedence\&.
1889 \f(CW none (i\&.e\&., no hosts specifically excluded)\fP
1892 \f(CW deny hosts = 150\&.203\&.4\&. badhost\&.mynet\&.edu\&.au\fP
1894 .IP "\fBdfree command (G)\fP"
1896 The dfree command setting should only be used on systems where a
1897 problem occurs with the internal disk space calculations\&. This has
1898 been known to happen with Ultrix, but may occur with other operating
1899 systems\&. The symptom that was seen was an error of "Abort Retry
1900 Ignore" at the end of each directory listing\&.
1902 This setting allows the replacement of the internal routines to
1903 calculate the total disk space and amount available with an external
1904 routine\&. The example below gives a possible script that might fulfill
1907 The external program will be passed a single parameter indicating a
1908 directory in the filesystem being queried\&. This will typically consist
1909 of the string \f(CW"\&./"\fP\&. The script should return two integers in
1910 ascii\&. The first should be the total disk space in blocks, and the
1911 second should be the number of available blocks\&. An optional third
1912 return value can give the block size in bytes\&. The default blocksize
1915 Note: Your script should \fINOT\fP be setuid or setgid and should be
1916 owned by (and writeable only by) root!
1919 \f(CW By default internal routines for determining the disk capacity
1920 and remaining space will be used\&.\fP
1923 \f(CW dfree command = /usr/local/samba/bin/dfree\fP
1925 Where the script dfree (which must be made executable) could be:
1932 df $1 | tail -1 | awk \'{print $2" "$4}\'
1938 or perhaps (on Sys V based systems):
1945 /usr/bin/df -k $1 | tail -1 | awk \'{print $3" "$5}\'
1951 Note that you may have to replace the command names with full
1952 path names on some systems\&.
1954 .IP "\fBdirectory (S)\fP"
1956 Synonym for \fBpath\fP\&.
1958 .IP "\fBdirectory mask (S)\fP"
1960 This parameter is the octal modes which are used when converting DOS
1961 modes to UNIX modes when creating UNIX directories\&.
1963 When a directory is created, the necessary permissions are calculated
1964 according to the mapping from DOS modes to UNIX permissions, and the
1965 resulting UNIX mode is then bit-wise \'AND\'ed with this parameter\&.
1966 This parameter may be thought of as a bit-wise MASK for the UNIX modes
1967 of a directory\&. Any bit \fI*not*\fP set here will be removed from the
1968 modes set on a directory when it is created\&.
1970 The default value of this parameter removes the \'group\' and \'other\'
1971 write bits from the UNIX mode, allowing only the user who owns the
1972 directory to modify it\&.
1974 Following this Samba will bit-wise \'OR\' the UNIX mode created from
1975 this parameter with the value of the "force directory mode"
1976 parameter\&. This parameter is set to 000 by default (i\&.e\&. no extra mode
1979 See the \fB"force directory mode"\fP parameter
1980 to cause particular mode bits to always be set on created directories\&.
1982 See also the \fB"create mode"\fP parameter for masking
1983 mode bits on created files\&.
1986 \f(CW directory mask = 0755\fP
1989 \f(CW directory mask = 0775\fP
1991 .IP "\fBdirectory mode (S)\fP"
1993 Synonym for \fBdirectory mask\fP\&.
1995 .IP "\fBdns proxy (G)\fP"
1997 Specifies that \fBnmbd\fP when acting as a WINS
1998 server and finding that a NetBIOS name has not been registered, should
1999 treat the NetBIOS name word-for-word as a DNS name and do a lookup
2000 with the DNS server for that name on behalf of the name-querying
2003 Note that the maximum length for a NetBIOS name is 15 characters, so
2004 the DNS name (or DNS alias) can likewise only be 15 characters,
2007 \fBnmbd\fP spawns a second copy of itself to do the
2008 DNS name lookup requests, as doing a name lookup is a blocking action\&.
2010 See also the parameter \fBwins support\fP\&.
2013 \f(CW dns proxy = yes\fP
2015 \fBdomain admin group (G)\fP
2017 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
2018 Samba NT Domain Controller Code\&. It has been removed as of November 98\&.
2019 To work with the latest code builds that may have more support for
2020 Samba NT Domain Controller functionality please subscribe to the
2021 mailing list \fBSamba-ntdom\fP available by sending email to
2022 \fIlistproc@samba\&.org\fP
2024 .IP "\fBdomain admin users (G)\fP"
2026 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
2027 Samba NT Domain Controller Code\&. It has been removed as of November 98\&.
2028 To work with the latest code builds that may have more support for
2029 Samba NT Domain Controller functionality please subscribe to the
2030 mailing list \fBSamba-ntdom\fP available by sending email to
2031 \fIlistproc@samba\&.org\fP
2033 .IP "\fBdomain controller (G)\fP"
2035 This is a \fBDEPRECATED\fP parameter\&. It is currently not used within
2036 the Samba source and should be removed from all current smb\&.conf
2037 files\&. It is left behind for compatibility reasons\&.
2039 .IP "\fBdomain group map (G)\fP"
2041 This option allows you to specify a file containing unique mappings
2042 of individual NT Domain Group names (in any domain) to UNIX group
2043 names\&. This allows NT domain groups to be presented correctly to
2044 NT users, despite the lack of native support for the NT Security model
2045 (based on VAX/VMS) in UNIX\&. The reader is advised to become familiar
2046 with the NT Domain system and its administration\&.
2048 This option is used in conjunction with \fB\'local group map\'\fP
2049 and \fB\'domain user map\'\fP\&. The use of these three
2050 options is trivial and often unnecessary in the case where Samba is
2051 not expected to interact with any other SAM databases (whether local
2052 workstations or Domain Controllers)\&.
2054 The map file is parsed line by line\&. If any line begins with a \f(CW\'#\'\fP
2055 or a \f(CW\';\'\fP then it is ignored\&. Each line should contain a single UNIX
2056 group name on the left then a single NT Domain Group name on the right,
2057 separated by a tabstop or \f(CW\'=\'\fP\&. If either name contains spaces then
2058 it should be enclosed in quotes\&.
2059 The line can be either of the form:
2061 \f(CW UNIXgroupname \e\eDOMAIN_NAME\e\eDomainGroupName \fP
2065 \f(CW UNIXgroupname DomainGroupName \fP
2067 In the case where Samba is either an \fBEXPERIMENTAL\fP Domain Controller
2068 or it is a member of a domain using \fB"security = domain"\fP,
2069 the latter format can be used: the default Domain name is the Samba Server\'s
2070 Domain name, specified by \fB"workgroup = MYGROUP"\fP\&.
2072 Any UNIX groups that are \fINOT\fP specified in this map file are assumed to
2073 be either Local or Domain Groups, depending on the role of the Samba Server\&.
2075 In the case when Samba is an \fBEXPERIMENTAL\fP Domain Controller, Samba
2076 will present \fIALL\fP such unspecified UNIX groups as its own NT Domain
2077 Groups, with the same name\&.
2079 In the case where Samba is member of a domain using
2080 \fB"security = domain"\fP, Samba will check the UNIX name with
2081 its Domain Controller (see \fB"password server"\fP)
2082 as if it was an NT Domain Group\&. If the Domain Controller says that it is not,
2083 such unspecified (unmapped) UNIX groups which also are not NT Domain
2084 Groups are treated as Local Groups in the Samba Server\'s local SAM database\&.
2085 NT Administrators will recognise these as Workstation Local Groups,
2086 which are managed by running \fBUSRMGR\&.EXE\fP and selecting a remote
2087 Domain named "\e\eWORKSTATION_NAME", or by running \fBMUSRMGR\&.EXE\fP on
2088 a local Workstation\&.
2090 This may sound complicated, but it means that a Samba Server as
2091 either a member of a domain or as an \fBEXPERIMENTAL\fP Domain Controller
2092 will act like an NT Workstation (with a local SAM database) or an NT PDC
2093 (with a Domain SAM database) respectively, without the need for any of
2094 the map files at all\&. If you \fBwant\fP to get fancy, however, you can\&.
2096 Note that adding an entry to map an arbitrary NT group in an arbitrary
2097 Domain to an arbitrary UNIX group \fIREQUIRES\fP the following:
2101 that the UNIX group exists on the UNIX server\&.
2104 that the NT Domain Group exists in the specified NT Domain
2107 that the UNIX Server knows about the specified Domain;
2110 that all the UNIX users (who are expecting to access the Samba
2111 Server as the correct NT user and with the correct NT group permissions)
2112 in the UNIX group be mapped to the correct NT Domain users in the specified
2113 NT Domain using \fB\'domain user map\'\fP\&.
2116 Failure to meet any of these requirements may result in either (or
2117 both) errors reported in the log files or (and) incorrect or missing
2118 access rights granted to users\&.
2120 .IP "\fBdomain groups (G)\fP"
2122 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
2123 Samba NT Domain Controller Code\&. It has been removed as of November 98\&.
2124 To work with the latest code builds that may have more support for
2125 Samba NT Domain Controller functionality please subscribe to the
2126 mailing list \fBSamba-ntdom\fP available by sending email to
2127 \fIlistproc@samba\&.org\fP
2129 .IP "\fBdomain guest group (G)\fP"
2131 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
2132 Samba NT Domain Controller Code\&. It has been removed as of November 98\&.
2133 To work with the latest code builds that may have more support for
2134 Samba NT Domain Controller functionality please subscribe to the
2135 mailing list \fBSamba-ntdom\fP available by sending email to
2136 \fIlistproc@samba\&.org\fP
2138 .IP "\fBdomain guest users (G)\fP"
2140 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
2141 Samba NT Domain Controller Code\&. It has been removed as of November 98\&.
2142 To work with the latest code builds that may have more support for
2143 Samba NT Domain Controller functionality please subscribe to the
2144 mailing list \fBSamba-ntdom\fP available by sending email to
2145 \fIlistproc@samba\&.org\fP
2147 .IP "\fBdomain logons (G)\fP"
2149 If set to true, the Samba server will serve Windows 95/98 Domain
2150 logons for the \fBworkgroup\fP it is in\&. For more
2151 details on setting up this feature see the file DOMAINS\&.txt in the
2152 Samba documentation directory \f(CWdocs/\fP shipped with the source code\&.
2154 Note that Win95/98 Domain logons are \fINOT\fP the same as Windows
2155 NT Domain logons\&. NT Domain logons require a Primary Domain Controller
2156 (PDC) for the Domain\&. It is intended that in a future release Samba
2157 will be able to provide this functionality for Windows NT clients
2161 \f(CW domain logons = no\fP
2163 .IP "\fBdomain master (G)\fP"
2165 Tell \fBnmbd\fP to enable WAN-wide browse list
2166 collation\&. Setting this option causes \fBnmbd\fP to
2167 claim a special domain specific NetBIOS name that identifies it as a
2168 domain master browser for its given
2169 \fBworkgroup\fP\&. Local master browsers in the same
2170 \fBworkgroup\fP on broadcast-isolated subnets will give
2171 this \fBnmbd\fP their local browse lists, and then
2172 ask \fBsmbd\fP for a complete copy of the browse list
2173 for the whole wide area network\&. Browser clients will then contact
2174 their local master browser, and will receive the domain-wide browse
2175 list, instead of just the list for their broadcast-isolated subnet\&.
2177 Note that Windows NT Primary Domain Controllers expect to be able to
2178 claim this \fBworkgroup\fP specific special NetBIOS
2179 name that identifies them as domain master browsers for that
2180 \fBworkgroup\fP by default (i\&.e\&. there is no way to
2181 prevent a Windows NT PDC from attempting to do this)\&. This means that
2182 if this parameter is set and \fBnmbd\fP claims the
2183 special name for a \fBworkgroup\fP before a Windows NT
2184 PDC is able to do so then cross subnet browsing will behave strangely
2187 By default ("auto") Samba will attempt to become the domain master
2188 browser only if it is the Primary Domain Controller\&.
2191 \f(CW domain master = auto\fP
2194 \f(CW domain master = no\fP
2196 .IP "\fBdomain user map (G)\fP"
2198 This option allows you to specify a file containing unique mappings
2199 of individual NT Domain User names (in any domain) to UNIX user
2200 names\&. This allows NT domain users to be presented correctly to
2201 NT systems, despite the lack of native support for the NT Security model
2202 (based on VAX/VMS) in UNIX\&. The reader is advised to become familiar
2203 with the NT Domain system and its administration\&.
2205 This option is used in conjunction with \fB\'local group map\'\fP
2206 and \fB\'domain group map\'\fP\&. The use of these three
2207 options is trivial and often unnecessary in the case where Samba is
2208 not expected to interact with any other SAM databases (whether local
2209 workstations or Domain Controllers)\&.
2211 This option, which provides (and maintains) a one-to-one link between
2212 UNIX and NT users, is \fIDIFFERENT\fP from \fB\'username map\'\fP, which does \fINOT\fP maintain a distinction between the
2213 name(s) it can map to and the name it maps\&.
2215 The map file is parsed line by line\&. If any line begins with a \f(CW\'#\'\fP
2216 or a \f(CW\';\'\fP then the line is ignored\&. Each line should contain a single UNIX
2217 user name on the left then a single NT Domain User name on the right,
2218 separated by a tabstop or \f(CW\'=\'\fP\&. If either name contains spaces then
2219 it should be enclosed in quotes\&.
2220 The line can be either of the form:
2222 \f(CW UNIXusername \e\eDOMAIN_NAME\e\eDomainUserName \fP
2226 \f(CW UNIXusername DomainUserName \fP
2228 In the case where Samba is either an \fBEXPERIMENTAL\fP Domain Controller
2229 or it is a member of a domain using \fB"security = domain"\fP,
2230 the latter format can be used: the default Domain name is the Samba Server\'s
2231 Domain name, specified by \fB"workgroup = MYGROUP"\fP\&.
2233 Any UNIX users that are \fINOT\fP specified in this map file are assumed
2234 to be either Domain or Workstation Users, depending on the role of the
2237 In the case when Samba is an \fBEXPERIMENTAL\fP Domain Controller, Samba
2238 will present \fIALL\fP such unspecified UNIX users as its own NT Domain
2239 Users, with the same name\&.
2241 In the case where Samba is a member of a domain using
2242 \fB"security = domain"\fP, Samba will check the UNIX name with
2243 its Domain Controller (see \fB"password server"\fP)
2244 as if it was an NT Domain User\&. If the Domain Controller says that it is not,
2245 such unspecified (unmapped) UNIX users which also are not NT Domain
2246 Users are treated as Local Users in the Samba Server\'s local SAM database\&.
2247 NT Administrators will recognise these as Workstation Users,
2248 which are managed by running \fBUSRMGR\&.EXE\fP and selecting a remote
2249 Domain named "\e\eWORKSTATION_NAME", or by running \fBMUSRMGR\&.EXE\fP on
2250 a local Workstation\&.
2252 This may sound complicated, but it means that a Samba Server as
2253 either a member of a domain or as an \fBEXPERIMENTAL\fP Domain Controller
2254 will act like an NT Workstation (with a local SAM database) or an NT PDC
2255 (with a Domain SAM database) respectively, without the need for any of
2256 the map files at all\&. If you \fBwant\fP to get fancy, however, you can\&.
2258 Note that adding an entry to map an arbitrary NT User in an arbitrary
2259 Domain to an arbitrary UNIX user \fIREQUIRES\fP the following:
2263 that the UNIX user exists on the UNIX server\&.
2266 that the NT Domain User exists in the specified NT Domain\&.
2269 that the UNIX Server knows about the specified Domain\&.
2272 Failure to meet any of these requirements may result in either (or
2273 both) errors reported in the log files or (and) incorrect or missing
2274 access rights granted to users\&.
2276 .IP "\fBdont descend (S)\fP"
2278 There are certain directories on some systems (e\&.g\&., the \f(CW/proc\fP tree
2279 under Linux) that are either not of interest to clients or are
2280 infinitely deep (recursive)\&. This parameter allows you to specify a
2281 comma-delimited list of directories that the server should always show
2284 Note that Samba can be very fussy about the exact format of the "dont
2285 descend" entries\&. For example you may need \f(CW"\&./proc"\fP instead of
2286 just \f(CW"/proc"\fP\&. Experimentation is the best policy :-)
2289 \f(CW none (i\&.e\&., all directories are OK to descend)\fP
2292 \f(CW dont descend = /proc,/dev\fP
2294 .IP "\fBdos filetime resolution (S)\fP"
2296 Under the DOS and Windows FAT filesystem, the finest granularity on
2297 time resolution is two seconds\&. Setting this parameter for a share
2298 causes Samba to round the reported time down to the nearest two second
2299 boundary when a query call that requires one second resolution is made
2302 This option is mainly used as a compatibility option for Visual C++
2303 when used against Samba shares\&. If oplocks are enabled on a share,
2304 Visual C++ uses two different time reading calls to check if a file
2305 has changed since it was last read\&. One of these calls uses a
2306 one-second granularity, the other uses a two second granularity\&. As
2307 the two second call rounds any odd second down, then if the file has a
2308 timestamp of an odd number of seconds then the two timestamps will not
2309 match and Visual C++ will keep reporting the file has changed\&. Setting
2310 this option causes the two timestamps to match, and Visual C++ is
2314 \f(CW dos filetime resolution = False\fP
2317 \f(CW dos filetime resolution = True\fP
2319 .IP "\fBdos filetimes (S)\fP"
2321 Under DOS and Windows, if a user can write to a file they can change
2322 the timestamp on it\&. Under POSIX semantics, only the owner of the file
2323 or root may change the timestamp\&. By default, Samba runs with POSIX
2324 semantics and refuses to change the timestamp on a file if the user
2325 smbd is acting on behalf of is not the file owner\&. Setting this option
2326 to True allows DOS semantics and smbd will change the file timestamp as
2330 \f(CW dos filetimes = False\fP
2333 \f(CW dos filetimes = True\fP
2335 .IP "\fBencrypt passwords (G)\fP"
2337 This boolean controls whether encrypted passwords will be negotiated
2338 with the client\&. Note that Windows NT 4\&.0 SP3 and above and also
2339 Windows 98 will by default expect encrypted passwords unless a
2340 registry entry is changed\&. To use encrypted passwords in Samba see the
2341 file ENCRYPTION\&.txt in the Samba documentation directory \f(CWdocs/\fP
2342 shipped with the source code\&.
2344 In order for encrypted passwords to work correctly
2345 \fBsmbd\fP must either have access to a local
2346 \fBsmbpasswd (5)\fP file (see the
2347 \fBsmbpasswd (8)\fP program for information on
2348 how to set up and maintain this file), or set the
2349 \fBsecurity=\fP parameter to either
2351 \fB"domain"\fP which causes
2352 \fBsmbd\fP to authenticate against another server\&.
2354 .IP "\fBexec (S)\fP"
2356 This is a synonym for \fBpreexec\fP\&.
2358 .IP "\fBfake directory create times (S)\fP"
2360 NTFS and Windows VFAT file systems keep a create time for all files
2361 and directories\&. This is not the same as the ctime - status change
2362 time - that Unix keeps, so Samba by default reports the earliest of
2363 the various times Unix does keep\&. Setting this parameter for a share
2364 causes Samba to always report midnight 1-1-1980 as the create time for
2367 This option is mainly used as a compatibility option for Visual C++
2368 when used against Samba shares\&. Visual C++ generated makefiles have
2369 the object directory as a dependency for each object file, and a make
2370 rule to create the directory\&. Also, when NMAKE compares timestamps it
2371 uses the creation time when examining a directory\&. Thus the object
2372 directory will be created if it does not exist, but once it does exist
2373 it will always have an earlier timestamp than the object files it
2376 However, Unix time semantics mean that the create time reported by
2377 Samba will be updated whenever a file is created or deleted in the
2378 directory\&. NMAKE therefore finds all object files in the object
2379 directory bar the last one built are out of date compared to the
2380 directory and rebuilds them\&. Enabling this option ensures directories
2381 always predate their contents and an NMAKE build will proceed as
2385 \f(CW fake directory create times = False\fP
2388 \f(CW fake directory create times = True\fP
2390 .IP "\fBfake oplocks (S)\fP"
2392 Oplocks are the way that SMB clients get permission from a server to
2393 locally cache file operations\&. If a server grants an oplock
2394 (opportunistic lock) then the client is free to assume that it is the
2395 only one accessing the file and it will aggressively cache file
2396 data\&. With some oplock types the client may even cache file open/close
2397 operations\&. This can give enormous performance benefits\&.
2399 When you set \f(CW"fake oplocks = yes"\fP \fBsmbd\fP will
2400 always grant oplock requests no matter how many clients are using the
2403 It is generally much better to use the real \fBoplocks\fP
2404 support rather than this parameter\&.
2406 If you enable this option on all read-only shares or shares that you
2407 know will only be accessed from one client at a time such as
2408 physically read-only media like CDROMs, you will see a big performance
2409 improvement on many operations\&. If you enable this option on shares
2410 where multiple clients may be accessing the files read-write at the
2411 same time you can get data corruption\&. Use this option carefully!
2413 This option is disabled by default\&.
2415 .IP "\fBfollow symlinks (S)\fP"
2417 This parameter allows the Samba administrator to stop
2418 \fBsmbd\fP from following symbolic links in a
2419 particular share\&. Setting this parameter to \fI"No"\fP prevents any file
2420 or directory that is a symbolic link from being followed (the user
2421 will get an error)\&. This option is very useful to stop users from
2422 adding a symbolic link to \f(CW/etc/passwd\fP in their home directory for
2423 instance\&. However it will slow filename lookups down slightly\&.
2425 This option is enabled (i\&.e\&. \fBsmbd\fP will follow
2426 symbolic links) by default\&.
2428 .IP "\fBforce create mode (S)\fP"
2430 This parameter specifies a set of UNIX mode bit permissions that will
2431 \fI*always*\fP be set on a file created by Samba\&. This is done by
2432 bitwise \'OR\'ing these bits onto the mode bits of a file that is being
2433 created\&. The default for this parameter is (in octal) 000\&. The modes
2434 in this parameter are bitwise \'OR\'ed onto the file mode after the mask
2435 set in the \fB"create mask"\fP parameter is applied\&.
2437 See also the parameter \fB"create mask"\fP for details
2438 on masking mode bits on created files\&.
2441 \f(CW force create mode = 000\fP
2444 \f(CW force create mode = 0755\fP
2446 would force all created files to have read and execute permissions set
2447 for \'group\' and \'other\' as well as the read/write/execute bits set for
2450 .IP "\fBforce directory mode (S)\fP"
2452 This parameter specifies a set of UNIX mode bit permissions that will
2453 \fI*always*\fP be set on a directory created by Samba\&. This is done by
2454 bitwise \'OR\'ing these bits onto the mode bits of a directory that is
2455 being created\&. The default for this parameter is (in octal) 0000 which
2456 will not add any extra permission bits to a created directory\&. This
2457 operation is done after the mode mask in the parameter
2458 \fB"directory mask"\fP is applied\&.
2460 See also the parameter \fB"directory mask"\fP for
2461 details on masking mode bits on created directories\&.
2464 \f(CW force directory mode = 000\fP
2467 \f(CW force directory mode = 0755\fP
2469 would force all created directories to have read and execute
2470 permissions set for \'group\' and \'other\' as well as the
2471 read/write/execute bits set for the \'user\'\&.
2473 .IP "\fBforce group (S)\fP"
2475 This specifies a UNIX group name that will be assigned as the default
2476 primary group for all users connecting to this service\&. This is useful
2477 for sharing files by ensuring that all access to files on service will
2478 use the named group for their permissions checking\&. Thus, by assigning
2479 permissions for this group to the files and directories within this
2480 service the Samba administrator can restrict or allow sharing of these
2484 \f(CW no forced group\fP
2487 \f(CW force group = agroup\fP
2489 .IP "\fBforce user (S)\fP"
2491 This specifies a UNIX user name that will be assigned as the default
2492 user for all users connecting to this service\&. This is useful for
2493 sharing files\&. You should also use it carefully as using it
2494 incorrectly can cause security problems\&.
2496 This user name only gets used once a connection is established\&. Thus
2497 clients still need to connect as a valid user and supply a valid
2498 password\&. Once connected, all file operations will be performed as the
2499 \f(CW"forced user"\fP, no matter what username the client connected as\&.
2501 This can be very useful\&.
2504 \f(CW no forced user\fP
2507 \f(CW force user = auser\fP
2509 .IP "\fBfstype (S)\fP"
2511 This parameter allows the administrator to configure the string that
2512 specifies the type of filesystem a share is using that is reported by
2513 \fBsmbd\fP when a client queries the filesystem type
2514 for a share\&. The default type is \fB"NTFS"\fP for compatibility with
2515 Windows NT but this can be changed to other strings such as "Samba" or
2516 "FAT" if required\&.
2519 \f(CW fstype = NTFS\fP
2522 \f(CW fstype = Samba\fP
2524 .IP "\fBgetwd cache (G)\fP"
2526 This is a tuning option\&. When this is enabled a caching algorithm
2527 will be used to reduce the time taken for getwd() calls\&. This can have
2528 a significant impact on performance, especially when the
2529 \fBwidelinks\fP parameter is set to False\&.
2532 \f(CW getwd cache = No\fP
2535 \f(CW getwd cache = Yes\fP
2537 .IP "\fBgroup (S)\fP"
2539 Synonym for \fB"force group"\fP\&.
2541 .IP "\fBguest account (S)\fP"
2543 This is a username which will be used for access to services which are
2544 specified as \fB\'guest ok\'\fP (see below)\&. Whatever
2545 privileges this user has will be available to any client connecting to
2546 the guest service\&. Typically this user will exist in the password
2547 file, but will not have a valid login\&. The user account \fB"ftp"\fP is
2548 often a good choice for this parameter\&. If a username is specified in
2549 a given service, the specified username overrides this one\&.
2551 One some systems the default guest account "nobody" may not be able to
2552 print\&. Use another account in this case\&. You should test this by
2553 trying to log in as your guest user (perhaps by using the \f(CW"su -"\fP
2554 command) and trying to print using the system print command such as
2555 \fBlpr (1)\fP or \fBlp (1)\fP\&.
2558 \f(CW specified at compile time, usually "nobody"\fP
2561 \f(CW guest account = ftp\fP
2563 .IP "\fBguest ok (S)\fP"
2565 If this parameter is \fI\'yes\'\fP for a service, then no password is
2566 required to connect to the service\&. Privileges will be those of the
2567 \fBguest account\fP\&.
2569 See the section below on \fBsecurity\fP for more
2570 information about this option\&.
2573 \f(CW guest ok = no\fP
2576 \f(CW guest ok = yes\fP
2578 .IP "\fBguest only (S)\fP"
2580 If this parameter is \fI\'yes\'\fP for a service, then only guest
2581 connections to the service are permitted\&. This parameter will have no
2582 affect if \fB"guest ok"\fP or \fB"public"\fP
2583 is not set for the service\&.
2585 See the section below on \fBsecurity\fP for more
2586 information about this option\&.
2589 \f(CW guest only = no\fP
2592 \f(CW guest only = yes\fP
2594 .IP "\fBhide dot files (S)\fP"
2596 This is a boolean parameter that controls whether files starting with
2597 a dot appear as hidden files\&.
2600 \f(CW hide dot files = yes\fP
2603 \f(CW hide dot files = no\fP
2605 .IP "\fBhide files(S)\fP"
2607 This is a list of files or directories that are not visible but are
2608 accessible\&. The DOS \'hidden\' attribute is applied to any files or
2609 directories that match\&.
2611 Each entry in the list must be separated by a \f(CW\'/\'\fP, which allows
2612 spaces to be included in the entry\&. \f(CW\'*\'\fP and \f(CW\'?\'\fP can be used
2613 to specify multiple files or directories as in DOS wildcards\&.
2615 Each entry must be a Unix path, not a DOS path and must not include the
2616 Unix directory separator \f(CW\'/\'\fP\&.
2618 Note that the case sensitivity option is applicable in hiding files\&.
2620 Setting this parameter will affect the performance of Samba, as it
2621 will be forced to check all files and directories for a match as they
2624 See also \fB"hide dot files"\fP, \fB"veto
2625 files"\fP and \fB"case sensitive"\fP\&.
2632 No files or directories are hidden by this option (dot files are
2633 hidden by default because of the "hide dot files" option)\&.
2640 \f(CW hide files = /\&.*/DesktopFolderDB/TrashFor%m/resource\&.frk/\fP
2642 The above example is based on files that the Macintosh SMB client
2643 (DAVE) available from \fBThursby\fP creates for
2644 internal use, and also still hides all files beginning with a dot\&.
2646 .IP "\fBhomedir map (G)\fP"
2648 If \fB"nis homedir"\fP is true, and
2649 \fBsmbd\fP is also acting as a Win95/98 \fBlogon
2650 server\fP then this parameter specifies the NIS (or YP)
2651 map from which the server for the user\'s home directory should be
2652 extracted\&. At present, only the Sun auto\&.home map format is
2653 understood\&. The form of the map is:
2655 \f(CWusername server:/some/file/system\fP
2657 and the program will extract the servername from before the first
2658 \f(CW\':\'\fP\&. There should probably be a better parsing system that copes
2659 with different map formats and also Amd (another automounter) maps\&.
2661 NB: A working NIS is required on the system for this option to work\&.
2663 See also \fB"nis homedir"\fP, \fBdomain
2667 \f(CW homedir map = auto\&.home\fP
2670 \f(CW homedir map = amd\&.homedir\fP
2672 .IP "\fBhosts allow (S)\fP"
2674 Synonym for \fBallow hosts\fP\&.
2676 .IP "\fBhosts deny (S)\fP"
2678 Synonym for \fBdenyhosts\fP\&.
2680 .IP "\fBhosts equiv (G)\fP"
2682 If this global parameter is a non-null string, it specifies the name
2683 of a file to read for the names of hosts and users who will be allowed
2684 access without specifying a password\&.
2686 This is not be confused with \fBallow hosts\fP which
2687 is about hosts access to services and is more useful for guest
2688 services\&. \fBhosts equiv\fP may be useful for NT clients which will not
2689 supply passwords to samba\&.
2691 NOTE: The use of \fBhosts equiv\fP can be a major security hole\&. This is
2692 because you are trusting the PC to supply the correct username\&. It is
2693 very easy to get a PC to supply a false username\&. I recommend that the
2694 \fBhosts equiv\fP option be only used if you really know what you are
2695 doing, or perhaps on a home network where you trust your spouse and
2696 kids\&. And only if you \fIreally\fP trust them :-)\&.
2699 \f(CW No host equivalences\fP
2702 \f(CW hosts equiv = /etc/hosts\&.equiv\fP
2704 .IP "\fBinclude (G)\fP"
2706 This allows you to include one config file inside another\&. The file
2707 is included literally, as though typed in place\&.
2709 It takes the standard substitutions, except \fB%u\fP,
2710 \fB%P\fP and \fB%S\fP\&.
2712 .IP "\fBinterfaces (G)\fP"
2714 This option allows you to setup multiple network interfaces, so that
2715 Samba can properly handle browsing on all interfaces\&.
2717 The option takes a list of ip/netmask pairs\&. The netmask may either be
2718 a bitmask, or a bitlength\&.
2720 For example, the following line:
2722 \f(CWinterfaces = 192\&.168\&.2\&.10/24 192\&.168\&.3\&.10/24\fP
2724 would configure two network interfaces with IP addresses 192\&.168\&.2\&.10
2725 and 192\&.168\&.3\&.10\&. The netmasks of both interfaces would be set to
2726 255\&.255\&.255\&.0\&.
2728 You could produce an equivalent result by using:
2730 \f(CWinterfaces = 192\&.168\&.2\&.10/255\&.255\&.255\&.0 192\&.168\&.3\&.10/255\&.255\&.255\&.0\fP
2732 if you prefer that format\&.
2734 If this option is not set then Samba will attempt to find a primary
2735 interface, but won\'t attempt to configure more than one interface\&.
2737 See also \fB"bind interfaces only"\fP\&.
2739 .IP "\fBinvalid users (S)\fP"
2741 This is a list of users that should not be allowed to login to this
2742 service\&. This is really a \fI"paranoid"\fP check to absolutely ensure an
2743 improper setting does not breach your security\&.
2745 A name starting with a \f(CW\'@\'\fP is interpreted as an NIS netgroup first
2746 (if your system supports NIS), and then as a UNIX group if the name
2747 was not found in the NIS netgroup database\&.
2749 A name starting with \f(CW\'+\'\fP is interpreted only by looking in the
2750 UNIX group database\&. A name starting with \f(CW\'&\'\fP is interpreted only
2751 by looking in the NIS netgroup database (this requires NIS to be
2752 working on your system)\&. The characters \f(CW\'+\'\fP and \f(CW\'&\'\fP may be
2753 used at the start of the name in either order so the value
2754 \f(CW"+&group"\fP means check the UNIX group database, followed by the NIS
2755 netgroup database, and the value \f(CW"&+group"\fP means check the NIS
2756 netgroup database, followed by the UNIX group database (the same as
2757 the \f(CW\'@\'\fP prefix)\&.
2759 The current servicename is substituted for
2760 \fB%S\fP\&. This is useful in the \fB[homes]\fP
2763 See also \fB"valid users"\fP\&.
2766 \f(CW No invalid users\fP
2769 \f(CW invalid users = root fred admin @wheel\fP
2771 .IP "\fBkeepalive (G)\fP"
2773 The value of the parameter (an integer) represents the number of
2774 seconds between \fB\'keepalive\'\fP packets\&. If this parameter is zero, no
2775 keepalive packets will be sent\&. Keepalive packets, if sent, allow the
2776 server to tell whether a client is still present and responding\&.
2778 Keepalives should, in general, not be needed if the socket being used
2779 has the SO_KEEPALIVE attribute set on it (see \fB"socket
2780 options"\fP)\&. Basically you should only use this option
2781 if you strike difficulties\&.
2784 \f(CW keep alive = 0\fP
2787 \f(CW keep alive = 60\fP
2789 .IP "\fBkernel oplocks (G)\fP"
2791 For UNIXs that support kernel based \fBoplocks\fP
2792 (currently only IRIX but hopefully also Linux and FreeBSD soon) this
2793 parameter allows the use of them to be turned on or off\&.
2795 Kernel oplocks support allows Samba \fBoplocks\fP to be
2796 broken whenever a local UNIX process or NFS operation accesses a file
2797 that \fBsmbd\fP has oplocked\&. This allows complete
2798 data consistency between SMB/CIFS, NFS and local file access (and is a
2799 \fIvery\fP cool feature :-)\&.
2801 This parameter defaults to \fI"On"\fP on systems that have the support,
2802 and \fI"off"\fP on systems that don\'t\&. You should never need to touch
2805 .IP "\fBldap bind as (G)\fP"
2807 This parameter is part of the \fIEXPERIMENTAL\fP Samba support for a
2808 password database stored on an LDAP server\&. These options are only
2809 available if your version of Samba was configured with the \fB--with-ldap\fP
2812 This parameter specifies the entity to bind to an LDAP directory as\&.
2813 Usually it should be safe to use the LDAP root account; for larger
2814 installations it may be preferable to restrict Samba\'s access\&. See also
2815 \fBldap passwd file\fP\&.
2818 \f(CW none (bind anonymously)\fP
2821 \f(CW ldap bind as = "uid=root, dc=mydomain, dc=org"\fP
2823 .IP "\fBldap passwd file (G)\fP"
2825 This parameter is part of the \fIEXPERIMENTAL\fP Samba support for a
2826 password database stored on an LDAP server\&. These options are only
2827 available if your version of Samba was configured with the \fB--with-ldap\fP
2830 This parameter specifies a file containing the password with which
2831 Samba should bind to an LDAP server\&. For obvious security reasons
2832 this file must be set to mode 700 or less\&.
2835 \f(CW none (bind anonymously)\fP
2838 \f(CW ldap passwd file = /usr/local/samba/private/ldappasswd\fP
2840 .IP "\fBldap port (G)\fP"
2842 This parameter is part of the \fIEXPERIMENTAL\fP Samba support for a
2843 password database stored on an LDAP server\&. These options are only
2844 available if your version of Samba was configured with the \fB--with-ldap\fP
2847 This parameter specifies the TCP port number of the LDAP server\&.
2850 \f(CW ldap port = 389\&.\fP
2852 .IP "\fBldap server (G)\fP"
2854 This parameter is part of the \fIEXPERIMENTAL\fP Samba support for a
2855 password database stored on an LDAP server back-end\&. These options
2856 are only available if your version of Samba was configured with
2857 the \fB--with-ldap\fP option\&.
2859 This parameter specifies the DNS name of the LDAP server to use
2860 when storing and retrieving information about Samba users and
2864 \f(CW ldap server = localhost\fP
2866 .IP "\fBldap suffix (G)\fP"
2868 This parameter is part of the \fIEXPERIMENTAL\fP Samba support for a
2869 password database stored on an LDAP server back-end\&. These options
2870 are only available if your version of Samba was configured with
2871 the \fB--with-ldap\fP option\&.
2873 This parameter specifies the node of the LDAP tree beneath which
2874 Samba should store its information\&. This parameter MUST be provided
2875 when using LDAP with Samba\&.
2881 \f(CW ldap suffix = "dc=mydomain, dc=org"\fP
2883 .IP "\fBlm announce (G)\fP"
2885 This parameter determines if \fBnmbd\fP will produce
2886 Lanman announce broadcasts that are needed by \fBOS/2\fP clients in order
2887 for them to see the Samba server in their browse list\&. This parameter
2888 can have three values, \f(CW"true"\fP, \f(CW"false"\fP, or \f(CW"auto"\fP\&. The
2889 default is \f(CW"auto"\fP\&. If set to \f(CW"false"\fP Samba will never produce
2890 these broadcasts\&. If set to \f(CW"true"\fP Samba will produce Lanman
2891 announce broadcasts at a frequency set by the parameter \fB"lm
2892 interval"\fP\&. If set to \f(CW"auto"\fP Samba will not send Lanman
2893 announce broadcasts by default but will listen for them\&. If it hears
2894 such a broadcast on the wire it will then start sending them at a
2895 frequency set by the parameter \fB"lm interval"\fP\&.
2897 See also \fB"lm interval"\fP\&.
2900 \f(CW lm announce = auto\fP
2903 \f(CW lm announce = true\fP
2905 .IP "\fBlm interval (G)\fP"
2907 If Samba is set to produce Lanman announce broadcasts needed by
2908 \fBOS/2\fP clients (see the \fB"lm announce"\fP
2909 parameter) then this parameter defines the frequency in seconds with
2910 which they will be made\&. If this is set to zero then no Lanman
2911 announcements will be made despite the setting of the \fB"lm
2912 announce"\fP parameter\&.
2914 See also \fB"lm announce"\fP\&.
2917 \f(CW lm interval = 60\fP
2920 \f(CW lm interval = 120\fP
2922 .IP "\fBload printers (G)\fP"
2924 A boolean variable that controls whether all printers in the printcap
2925 will be loaded for browsing by default\&. See the
2926 \fB"printers"\fP section for more details\&.
2929 \f(CW load printers = yes\fP
2932 \f(CW load printers = no\fP
2934 .IP "\fBlocal group map (G)\fP"
2936 This option allows you to specify a file containing unique mappings
2937 of individual NT Local Group names (in any domain) to UNIX group
2938 names\&. This allows NT Local groups (aliases) to be presented correctly to
2939 NT users, despite the lack of native support for the NT Security model
2940 (based on VAX/VMS) in UNIX\&. The reader is advised to become familiar
2941 with the NT Domain system and its administration\&.
2943 This option is used in conjunction with \fB\'domain group map\'\fP
2944 and \fB\'domain name map\'\fP\&. The use of these three
2945 options is trivial and often unnecessary in the case where Samba
2946 is not expected to interact with any other SAM databases (whether local
2947 workstations or Domain Controllers)\&.
2949 The map file is parsed line by line\&. If any line begins with a \f(CW\'#\'\fP
2950 or a \f(CW\';\'\fP then it is ignored\&. Each line should contain a single UNIX
2951 group name on the left then a single NT Local Group name on the right,
2952 separated by a tabstop or \f(CW\'=\'\fP\&. If either name contains spaces then
2953 it should be enclosed in quotes\&.
2954 The line can be either of the form:
2956 \f(CW UNIXgroupname \e\eDOMAIN_NAME\e\eLocalGroupName \fP
2960 \f(CW UNIXgroupname LocalGroupName \fP
2962 In the case where Samba is either an \fBEXPERIMENTAL\fP Domain Controller
2963 or it is a member of a domain using \fB"security = domain"\fP,
2964 the latter format can be used: the default Domain name is the Samba Server\'s
2965 Domain name, specified by \fB"workgroup = MYGROUP"\fP\&.
2967 Any UNIX groups that are \fINOT\fP specified in this map file are treated
2968 as either Local or Domain Groups depending on the role of the Samba Server\&.
2970 In the case when Samba is an \fBEXPERIMENTAL\fP Domain Controller, Samba
2971 will present \fIALL\fP unspecified UNIX groups as its own NT Domain
2972 Groups, with the same name, and \fINOT\fP as Local Groups\&.
2974 In the case where Samba is member of a domain using
2975 \fB"security = domain"\fP, Samba will check the UNIX name with
2976 its Domain Controller (see \fB"password server"\fP)
2977 as if it was an NT Domain Group\&. If the Domain Controller says that it is not,
2978 such unspecified (unmapped) UNIX groups which also are not NT Domain
2979 Groups are treated as Local Groups in the Samba Server\'s local SAM database\&.
2980 NT Administrators will recognise these as Workstation Local Groups,
2981 which are managed by running \fBUSRMGR\&.EXE\fP and selecting a remote
2982 Domain named "\e\eWORKSTATION_NAME", or by running \fBMUSRMGR\&.EXE\fP on
2983 a local Workstation\&.
2985 This may sound complicated, but it means that a Samba Server as
2986 either a member of a domain or as an \fBEXPERIMENTAL\fP Domain Controller
2987 will act like an NT Workstation (with a local SAM database) or an NT PDC
2988 (with a Domain SAM database) respectively, without the need for any of
2989 the map files at all\&. If you \fBwant\fP to get fancy, however, you can\&.
2991 Note that adding an entry to map an arbitrary NT group in an arbitrary
2992 Domain to an arbitrary UNIX group \fIREQUIRES\fP the following:
2996 that the UNIX group exists on the UNIX server\&.
2999 that the NT Domain Group exists in the specified NT Domain
3002 that the UNIX Server knows about the specified Domain;
3005 that all the UNIX users (who are expecting to access the Samba
3006 Server as the correct NT user and with the correct NT group permissions)
3007 in the UNIX group be mapped to the correct NT Domain users in the specified
3008 NT Domain using \fB\'domain user map\'\fP\&.
3011 Failure to meet any of these requirements may result in either (or
3012 both) errors reported in the log files or (and) incorrect or missing
3013 access rights granted to users\&.
3015 .IP "\fBlocal master (G)\fP"
3017 This option allows \fBnmbd\fP to try and become a
3018 local master browser on a subnet\&. If set to False then
3019 \fBnmbd\fP will not attempt to become a local master
3020 browser on a subnet and will also lose in all browsing elections\&. By
3021 default this value is set to true\&. Setting this value to true doesn\'t
3022 mean that Samba will \fIbecome\fP the local master browser on a subnet,
3023 just that \fBnmbd\fP will \fIparticipate\fP in
3024 elections for local master browser\&.
3026 Setting this value to False will cause \fBnmbd\fP
3027 \fInever\fP to become a local master browser\&.
3030 \f(CW local master = yes\fP
3032 .IP "\fBlock dir (G)\fP"
3034 Synonym for \fB"lock directory"\fP\&.
3036 .IP "\fBlock directory (G)\fP"
3038 This option specifies the directory where lock files will be placed\&.
3039 The lock files are used to implement the \fB"max
3040 connections"\fP option\&.
3043 \f(CW lock directory = /tmp/samba\fP
3046 \f(CW lock directory = /usr/local/samba/var/locks\fP
3048 .IP "\fBlocking (S)\fP"
3050 This controls whether or not locking will be performed by the server
3051 in response to lock requests from the client\&.
3053 If \f(CW"locking = no"\fP, all lock and unlock requests will appear to
3054 succeed and all lock queries will indicate that the queried lock is
3057 If \f(CW"locking = yes"\fP, real locking will be performed by the server\&.
3059 This option \fImay\fP be useful for read-only filesystems which \fImay\fP
3060 not need locking (such as cdrom drives), although setting this
3061 parameter of \f(CW"no"\fP is not really recommended even in this case\&.
3063 Be careful about disabling locking either globally or in a specific
3064 service, as lack of locking may result in data corruption\&. You should
3065 never need to set this parameter\&.
3068 \f(CW locking = yes\fP
3071 \f(CW locking = no\fP
3073 .IP "\fBlog file (G)\fP"
3075 This options allows you to override the name of the Samba log file
3076 (also known as the debug file)\&.
3078 This option takes the standard substitutions, allowing you to have
3079 separate log files for each user or machine\&.
3082 \f(CW log file = /usr/local/samba/var/log\&.%m\fP
3084 .IP "\fBlog level (G)\fP"
3086 Synonym for \fB"debug level"\fP\&.
3088 .IP "\fBlogon drive (G)\fP"
3090 This parameter specifies the local path to which the home directory
3091 will be connected (see \fB"logon home"\fP) and is only
3092 used by NT Workstations\&.
3094 Note that this option is only useful if Samba is set up as a
3095 \fBlogon server\fP\&.
3098 \f(CW logon drive = h:\fP
3100 .IP "\fBlogon home (G)\fP"
3102 This parameter specifies the home directory location when a Win95/98 or
3103 NT Workstation logs into a Samba PDC\&. It allows you to do
3105 \f(CW"NET USE H: /HOME"\fP
3107 from a command prompt, for example\&.
3109 This option takes the standard substitutions, allowing you to have
3110 separate logon scripts for each user or machine\&.
3112 Note that this option is only useful if Samba is set up as a
3113 \fBlogon server\fP\&.
3116 \f(CW logon home = "\e\eremote_smb_server\e%U"\fP
3119 \f(CW logon home = "\e\e%N\e%U"\fP
3121 .IP "\fBlogon path (G)\fP"
3123 This parameter specifies the home directory where roaming profiles
3124 (USER\&.DAT / USER\&.MAN files for Windows 95/98) are stored\&.
3126 This option takes the standard substitutions, allowing you to have
3127 separate logon scripts for each user or machine\&. It also specifies
3128 the directory from which the \f(CW"desktop"\fP, \f(CW"start menu"\fP,
3129 \f(CW"network neighborhood"\fP and \f(CW"programs"\fP folders, and their
3130 contents, are loaded and displayed on your Windows 95/98 client\&.
3132 The share and the path must be readable by the user for the
3133 preferences and directories to be loaded onto the Windows 95/98
3134 client\&. The share must be writeable when the logs in for the first
3135 time, in order that the Windows 95/98 client can create the user\&.dat
3136 and other directories\&.
3138 Thereafter, the directories and any of the contents can, if required, be
3139 made read-only\&. It is not advisable that the USER\&.DAT file be made
3140 read-only - rename it to USER\&.MAN to achieve the desired effect (a
3141 \fIMAN\fPdatory profile)\&.
3143 Windows clients can sometimes maintain a connection to the [homes]
3144 share, even though there is no user logged in\&. Therefore, it is vital
3145 that the logon path does not include a reference to the homes share
3146 (i\&.e\&. setting this parameter to \f(CW\e\e%N\eHOMES\eprofile_path\fP will cause
3149 This option takes the standard substitutions, allowing you to have
3150 separate logon scripts for each user or machine\&.
3152 Note that this option is only useful if Samba is set up as a
3153 \fBlogon server\fP\&.
3156 \f(CW logon path = \e\e%N\e%U\eprofile\fP
3159 \f(CW logon path = \e\ePROFILESERVER\eHOME_DIR\e%U\ePROFILE\fP
3161 .IP "\fBlogon script (G)\fP"
3163 This parameter specifies the batch file (\&.bat) or NT command file
3164 (\&.cmd) to be downloaded and run on a machine when a user successfully
3165 logs in\&. The file must contain the DOS style cr/lf line endings\&.
3166 Using a DOS-style editor to create the file is recommended\&.
3168 The script must be a relative path to the \f(CW[netlogon]\fP service\&. If
3169 the \f(CW[netlogon]\fP service specifies a \fBpath\fP of
3170 /usr/local/samba/netlogon, and logon script = STARTUP\&.BAT, then the
3171 file that will be downloaded is:
3173 \f(CW/usr/local/samba/netlogon/STARTUP\&.BAT\fP
3175 The contents of the batch file is entirely your choice\&. A suggested
3176 command would be to add \f(CWNET TIME \e\eSERVER /SET /YES\fP, to force every
3177 machine to synchronize clocks with the same time server\&. Another use
3178 would be to add \f(CWNET USE U: \e\eSERVER\eUTILS\fP for commonly used
3179 utilities, or \f(CWNET USE Q: \e\eSERVER\eISO9001_QA\fP for example\&.
3181 Note that it is particularly important not to allow write access to
3182 the \f(CW[netlogon]\fP share, or to grant users write permission on the
3183 batch files in a secure environment, as this would allow the batch
3184 files to be arbitrarily modified and security to be breached\&.
3186 This option takes the standard substitutions, allowing you to have
3187 separate logon scripts for each user or machine\&.
3189 Note that this option is only useful if Samba is set up as a
3190 \fBlogon server\fP\&.
3193 \f(CW logon script = scripts\e%U\&.bat\fP
3195 .IP "\fBlppause command (S)\fP"
3197 This parameter specifies the command to be executed on the server host
3198 in order to stop printing or spooling a specific print job\&.
3200 This command should be a program or script which takes a printer name
3201 and job number to pause the print job\&. One way of implementing this is
3202 by using job priorities, where jobs having a too low priority won\'t be
3203 sent to the printer\&.
3205 If a \f(CW"%p"\fP is given then the printername is put in its place\&. A
3206 \f(CW"%j"\fP is replaced with the job number (an integer)\&. On HPUX (see
3207 \fBprinting=hpux\fP), if the \f(CW"-p%p"\fP option is added
3208 to the lpq command, the job will show up with the correct status,
3209 i\&.e\&. if the job priority is lower than the set fence priority it will
3210 have the PAUSED status, whereas if the priority is equal or higher it
3211 will have the SPOOLED or PRINTING status\&.
3213 Note that it is good practice to include the absolute path in the
3214 lppause command as the PATH may not be available to the server\&.
3216 See also the \fB"printing"\fP parameter\&.
3219 Currently no default value is given to this string, unless the
3220 value of the \fB"printing"\fP parameter is \f(CWSYSV\fP, in
3221 which case the default is :
3223 \f(CW lp -i %p-%j -H hold\fP
3225 or if the value of the \fB"printing"\fP parameter is \f(CWsoftq\fP,
3226 then the default is:
3228 \f(CW qstat -s -j%j -h\fP
3230 \fBExample for HPUX:\fP
3231 lppause command = /usr/bin/lpalt %p-%j -p0
3233 .IP "\fBlpq cache time (G)\fP"
3235 This controls how long lpq info will be cached for to prevent the
3236 \fBlpq\fP command being called too often\&. A separate cache is kept for
3237 each variation of the \fBlpq\fP command used by the system, so if you
3238 use different \fBlpq\fP commands for different users then they won\'t
3239 share cache information\&.
3241 The cache files are stored in \f(CW/tmp/lpq\&.xxxx\fP where xxxx is a hash of
3242 the \fBlpq\fP command in use\&.
3244 The default is 10 seconds, meaning that the cached results of a
3245 previous identical \fBlpq\fP command will be used if the cached data is
3246 less than 10 seconds old\&. A large value may be advisable if your
3247 \fBlpq\fP command is very slow\&.
3249 A value of 0 will disable caching completely\&.
3251 See also the \fB"printing"\fP parameter\&.
3254 \f(CW lpq cache time = 10\fP
3257 \f(CW lpq cache time = 30\fP
3259 .IP "\fBlpq command (S)\fP"
3261 This parameter specifies the command to be executed on the server host
3262 in order to obtain \f(CW"lpq"\fP-style printer status information\&.
3264 This command should be a program or script which takes a printer name
3265 as its only parameter and outputs printer status information\&.
3267 Currently eight styles of printer status information are supported;
3268 BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX and SOFTQ\&. This covers most UNIX
3269 systems\&. You control which type is expected using the
3270 \fB"printing ="\fP option\&.
3272 Some clients (notably Windows for Workgroups) may not correctly send
3273 the connection number for the printer they are requesting status
3274 information about\&. To get around this, the server reports on the first
3275 printer service connected to by the client\&. This only happens if the
3276 connection number sent is invalid\&.
3278 If a \f(CW%p\fP is given then the printername is put in its place\&. Otherwise
3279 it is placed at the end of the command\&.
3281 Note that it is good practice to include the absolute path in the \fBlpq
3282 command\fP as the PATH may not be available to the server\&.
3284 See also the \fB"printing"\fP parameter\&.
3287 \f(CW depends on the setting of printing =\fP
3290 \f(CW lpq command = /usr/bin/lpq %p\fP
3292 .IP "\fBlpresume command (S)\fP"
3294 This parameter specifies the command to be executed on the server host
3295 in order to restart or continue printing or spooling a specific print
3298 This command should be a program or script which takes a printer name
3299 and job number to resume the print job\&. See also the \fB"lppause
3300 command"\fP parameter\&.
3302 If a \f(CW%p\fP is given then the printername is put in its place\&. A
3303 \f(CW%j\fP is replaced with the job number (an integer)\&.
3305 Note that it is good practice to include the absolute path in the \fBlpresume
3306 command\fP as the PATH may not be available to the server\&.
3308 See also the \fB"printing"\fP parameter\&.
3312 Currently no default value is given to this string, unless the
3313 value of the \fB"printing"\fP parameter is \f(CWSYSV\fP, in
3314 which case the default is :
3316 \f(CW lp -i %p-%j -H resume\fP
3318 or if the value of the \fB"printing"\fP parameter is \f(CWsoftq\fP,
3319 then the default is:
3321 \f(CW qstat -s -j%j -r\fP
3323 \fBExample for HPUX:\fP
3324 \f(CW lpresume command = /usr/bin/lpalt %p-%j -p2\fP
3326 .IP "\fBlprm command (S)\fP"
3328 This parameter specifies the command to be executed on the server host
3329 in order to delete a print job\&.
3331 This command should be a program or script which takes a printer name
3332 and job number, and deletes the print job\&.
3334 If a \f(CW%p\fP is given then the printername is put in its place\&. A
3335 \f(CW%j\fP is replaced with the job number (an integer)\&.
3337 Note that it is good practice to include the absolute path in the
3338 \fBlprm command\fP as the PATH may not be available to the server\&.
3340 See also the \fB"printing"\fP parameter\&.
3343 \f(CW depends on the setting of "printing ="\fP
3346 \f(CW lprm command = /usr/bin/lprm -P%p %j\fP
3349 \f(CW lprm command = /usr/bin/cancel %p-%j\fP
3351 .IP "\fBmachine password timeout (G)\fP"
3353 If a Samba server is a member of an Windows NT Domain (see the
3354 \fB"security=domain"\fP) parameter) then
3355 periodically a running \fBsmbd\fP process will try and
3356 change the \fBMACHINE ACCOUNT PASWORD\fP stored in the file called
3357 \f(CW<Domain>\&.<Machine>\&.mac\fP where \f(CW<Domain>\fP is the name of the
3358 Domain we are a member of and \f(CW<Machine>\fP is the primary
3359 \fB"NetBIOS name"\fP of the machine
3360 \fBsmbd\fP is running on\&. This parameter specifies how
3361 often this password will be changed, in seconds\&. The default is one
3362 week (expressed in seconds), the same as a Windows NT Domain member
3365 See also \fBsmbpasswd (8)\fP, and the
3366 \fB"security=domain"\fP) parameter\&.
3369 \f(CW machine password timeout = 604800\fP
3371 .IP "\fBmagic output (S)\fP"
3373 This parameter specifies the name of a file which will contain output
3374 created by a magic script (see the \fB"magic
3375 script"\fP parameter below)\&.
3377 Warning: If two clients use the same \fB"magic
3378 script"\fP in the same directory the output file content
3382 \f(CW magic output = <magic script name>\&.out\fP
3385 \f(CW magic output = myfile\&.txt\fP
3387 .IP "\fBmagic script (S)\fP"
3389 This parameter specifies the name of a file which, if opened, will be
3390 executed by the server when the file is closed\&. This allows a UNIX
3391 script to be sent to the Samba host and executed on behalf of the
3394 Scripts executed in this way will be deleted upon completion,
3395 permissions permitting\&.
3397 If the script generates output, output will be sent to the file
3398 specified by the \fB"magic output"\fP parameter (see
3401 Note that some shells are unable to interpret scripts containing
3402 carriage-return-linefeed instead of linefeed as the end-of-line
3403 marker\&. Magic scripts must be executable \fI"as is"\fP on the host,
3404 which for some hosts and some shells will require filtering at the DOS
3407 Magic scripts are \fIEXPERIMENTAL\fP and should \fINOT\fP be relied upon\&.
3410 \f(CW None\&. Magic scripts disabled\&.\fP
3413 \f(CW magic script = user\&.csh\fP
3415 .IP "\fBmangle case (S)\fP"
3417 See the section on \fB"NAME MANGLING"\fP\&.
3419 .IP "\fBmangled map (S)\fP"
3421 This is for those who want to directly map UNIX file names which can
3422 not be represented on Windows/DOS\&. The mangling of names is not always
3423 what is needed\&. In particular you may have documents with file
3424 extensions that differ between DOS and UNIX\&. For example, under UNIX
3425 it is common to use \f(CW"\&.html"\fP for HTML files, whereas under
3426 Windows/DOS \f(CW"\&.htm"\fP is more commonly used\&.
3428 So to map \f(CW"html"\fP to \f(CW"htm"\fP you would use:
3430 \f(CW mangled map = (*\&.html *\&.htm)\fP
3432 One very useful case is to remove the annoying \f(CW";1"\fP off the ends
3433 of filenames on some CDROMS (only visible under some UNIXs)\&. To do
3434 this use a map of (*;1 *)\&.
3437 \f(CW no mangled map\fP
3440 \f(CW mangled map = (*;1 *)\fP
3442 .IP "\fBmangled names (S)\fP"
3444 This controls whether non-DOS names under UNIX should be mapped to
3445 DOS-compatible names ("mangled") and made visible, or whether non-DOS
3446 names should simply be ignored\&.
3448 See the section on \fB"NAME MANGLING"\fP for details
3449 on how to control the mangling process\&.
3451 If mangling is used then the mangling algorithm is as follows:
3455 The first (up to) five alphanumeric characters before the
3456 rightmost dot of the filename are preserved, forced to upper case, and
3457 appear as the first (up to) five characters of the mangled name\&.
3460 A tilde \f(CW"~"\fP is appended to the first part of the mangled
3461 name, followed by a two-character unique sequence, based on the
3462 original root name (i\&.e\&., the original filename minus its final
3463 extension)\&. The final extension is included in the hash calculation
3464 only if it contains any upper case characters or is longer than three
3467 Note that the character to use may be specified using the
3468 \fB"mangling char"\fP option, if you don\'t like
3472 The first three alphanumeric characters of the final extension
3473 are preserved, forced to upper case and appear as the extension of the
3474 mangled name\&. The final extension is defined as that part of the
3475 original filename after the rightmost dot\&. If there are no dots in the
3476 filename, the mangled name will have no extension (except in the case
3477 of \fB"hidden files"\fP - see below)\&.
3480 Files whose UNIX name begins with a dot will be presented as DOS
3481 hidden files\&. The mangled name will be created as for other filenames,
3482 but with the leading dot removed and \f(CW"___"\fP as its extension regardless
3483 of actual original extension (that\'s three underscores)\&.
3486 The two-digit hash value consists of upper case alphanumeric
3489 This algorithm can cause name collisions only if files in a directory
3490 share the same first five alphanumeric characters\&. The probability of
3491 such a clash is 1/1300\&.
3493 The name mangling (if enabled) allows a file to be copied between UNIX
3494 directories from Windows/DOS while retaining the long UNIX
3495 filename\&. UNIX files can be renamed to a new extension from
3496 Windows/DOS and will retain the same basename\&. Mangled names do not
3497 change between sessions\&.
3500 \f(CW mangled names = yes\fP
3503 \f(CW mangled names = no\fP
3505 .IP "\fBmangling char (S)\fP"
3507 This controls what character is used as the \fI"magic"\fP character in
3508 \fBname mangling\fP\&. The default is a \f(CW\'~\'\fP but
3509 this may interfere with some software\&. Use this option to set it to
3510 whatever you prefer\&.
3513 \f(CW mangling char = ~\fP
3516 \f(CW mangling char = ^\fP
3518 .IP "\fBmangled stack (G)\fP"
3520 This parameter controls the number of mangled names that should be
3521 cached in the Samba server \fBsmbd\fP\&.
3523 This stack is a list of recently mangled base names (extensions are
3524 only maintained if they are longer than 3 characters or contains upper
3527 The larger this value, the more likely it is that mangled names can be
3528 successfully converted to correct long UNIX names\&. However, large
3529 stack sizes will slow most directory access\&. Smaller stacks save
3530 memory in the server (each stack element costs 256 bytes)\&.
3532 It is not possible to absolutely guarantee correct long file names, so
3533 be prepared for some surprises!
3536 \f(CW mangled stack = 50\fP
3539 \f(CW mangled stack = 100\fP
3541 .IP "\fBmap archive (S)\fP"
3543 This controls whether the DOS archive attribute should be mapped to
3544 the UNIX owner execute bit\&. The DOS archive bit is set when a file
3545 has been modified since its last backup\&. One motivation for this
3546 option it to keep Samba/your PC from making any file it touches from
3547 becoming executable under UNIX\&. This can be quite annoying for shared
3548 source code, documents, etc\&.\&.\&.
3550 Note that this requires the \fB"create mask"\fP
3551 parameter to be set such that owner execute bit is not masked out
3552 (i\&.e\&. it must include 100)\&. See the parameter \fB"create
3553 mask"\fP for details\&.
3556 \f(CW map archive = yes\fP
3559 \f(CW map archive = no\fP
3561 .IP "\fBmap hidden (S)\fP"
3563 This controls whether DOS style hidden files should be mapped to the
3564 UNIX world execute bit\&.
3566 Note that this requires the \fB"create mask"\fP to be
3567 set such that the world execute bit is not masked out (i\&.e\&. it must
3568 include 001)\&. See the parameter \fB"create mask"\fP
3572 \f(CW map hidden = no\fP
3575 \f(CW map hidden = yes\fP
3577 .IP "\fBmap system (S)\fP"
3579 This controls whether DOS style system files should be mapped to the
3580 UNIX group execute bit\&.
3582 Note that this requires the \fB"create mask"\fP to be
3583 set such that the group execute bit is not masked out (i\&.e\&. it must
3584 include 010)\&. See the parameter \fB"create mask"\fP
3588 \f(CW map system = no\fP
3591 \f(CW map system = yes\fP
3593 .IP "\fBmap to guest (G)\fP"
3595 This parameter is only useful in \fBsecurity\fP modes
3596 other than \fB"security=share"\fP - i\&.e\&. user,
3597 server, and domain\&.
3599 This parameter can take three different values, which tell
3600 \fBsmbd\fP what to do with user login requests that
3601 don\'t match a valid UNIX user in some way\&.
3603 The three settings are :
3607 \fB"Never"\fP - Means user login requests with an invalid password
3608 are rejected\&. This is the default\&.
3611 \fB"Bad User"\fP - Means user logins with an invalid password are
3612 rejected, unless the username does not exist, in which case it is
3613 treated as a guest login and mapped into the \fB"guest
3617 \fB"Bad Password"\fP - Means user logins with an invalid
3618 password are treated as a guest login and mapped into the
3619 \fB"guest account"\fP\&. Note that this can
3620 cause problems as it means that any user incorrectly typing their
3621 password will be silently logged on a \fB"guest"\fP - and
3622 will not know the reason they cannot access files they think
3623 they should - there will have been no message given to them
3624 that they got their password wrong\&. Helpdesk services will
3625 \fI*hate*\fP you if you set the \fB"map to guest"\fP parameter
3629 Note that this parameter is needed to set up \fB"Guest"\fP share
3630 services when using \fBsecurity\fP modes other than
3631 share\&. This is because in these modes the name of the resource being
3632 requested is \fI*not*\fP sent to the server until after the server has
3633 successfully authenticated the client so the server cannot make
3634 authentication decisions at the correct time (connection to the
3635 share) for \fB"Guest"\fP shares\&.
3637 For people familiar with the older Samba releases, this parameter
3638 maps to the old compile-time setting of the GUEST_SESSSETUP value
3642 \f(CW map to guest = Never\fP
3644 \f(CW map to guest = Bad User\fP
3646 .IP "\fBmax connections (S)\fP"
3648 This option allows the number of simultaneous connections to a service
3649 to be limited\&. If \fB"max connections"\fP is greater than 0 then
3650 connections will be refused if this number of connections to the
3651 service are already open\&. A value of zero mean an unlimited number of
3652 connections may be made\&.
3654 Record lock files are used to implement this feature\&. The lock files
3655 will be stored in the directory specified by the \fB"lock
3656 directory"\fP option\&.
3659 \f(CW max connections = 0\fP
3662 \f(CW max connections = 10\fP
3664 .IP "\fBmax disk size (G)\fP"
3666 This option allows you to put an upper limit on the apparent size of
3667 disks\&. If you set this option to 100 then all shares will appear to be
3668 not larger than 100 MB in size\&.
3670 Note that this option does not limit the amount of data you can put on
3671 the disk\&. In the above case you could still store much more than 100
3672 MB on the disk, but if a client ever asks for the amount of free disk
3673 space or the total disk size then the result will be bounded by the
3674 amount specified in \fB"max disk size"\fP\&.
3676 This option is primarily useful to work around bugs in some pieces of
3677 software that can\'t handle very large disks, particularly disks over
3680 A \fB"max disk size"\fP of 0 means no limit\&.
3683 \f(CW max disk size = 0\fP
3686 \f(CW max disk size = 1000\fP
3688 .IP "\fBmax log size (G)\fP"
3690 This option (an integer in kilobytes) specifies the max size the log
3691 file should grow to\&. Samba periodically checks the size and if it is
3692 exceeded it will rename the file, adding a \f(CW"\&.old"\fP extension\&.
3694 A size of 0 means no limit\&.
3697 \f(CW max log size = 5000\fP
3700 \f(CW max log size = 1000\fP
3702 .IP "\fBmax mux (G)\fP"
3704 This option controls the maximum number of outstanding simultaneous
3705 SMB operations that samba tells the client it will allow\&. You should
3706 never need to set this parameter\&.
3709 \f(CW max mux = 50\fP
3711 .IP "\fBmaxopenfiles (G)\fP"
3713 This parameter limits the maximum number of open files that one
3714 \fBsmbd\fP file serving process may have open for
3715 a client at any one time\&. The default for this parameter is set
3716 very high (10,000) as Samba uses only one bit per unopened file\&.
3718 The limit of the number of open files is usually set by the
3719 UNIX per-process file descriptor limit rather than this parameter
3720 so you should never need to touch this parameter\&.
3723 \f(CW max open files = 10000\fP
3725 .IP "\fBmax packet (G)\fP"
3727 Synonym for (packetsize)\&.
3729 .IP "\fBmax ttl (G)\fP"
3731 This option tells \fBnmbd\fP what the default \'time
3732 to live\' of NetBIOS names should be (in seconds) when
3733 \fBnmbd\fP is requesting a name using either a
3734 broadcast packet or from a WINS server\&. You should never need to
3735 change this parameter\&. The default is 3 days\&.
3738 \f(CW max ttl = 259200\fP
3740 .IP "\fBmax wins ttl (G)\fP"
3742 This option tells \fBnmbd\fP when acting as a WINS
3743 server \fB(wins support =true)\fP what the maximum
3744 \'time to live\' of NetBIOS names that \fBnmbd\fP will
3745 grant will be (in seconds)\&. You should never need to change this
3746 parameter\&. The default is 6 days (518400 seconds)\&.
3748 See also the \fB"min wins ttl"\fP parameter\&.
3751 \f(CW max wins ttl = 518400\fP
3753 .IP "\fBmax xmit (G)\fP"
3755 This option controls the maximum packet size that will be negotiated
3756 by Samba\&. The default is 65535, which is the maximum\&. In some cases
3757 you may find you get better performance with a smaller value\&. A value
3758 below 2048 is likely to cause problems\&.
3761 \f(CW max xmit = 65535\fP
3764 \f(CW max xmit = 8192\fP
3766 .IP "\fBmessage command (G)\fP"
3768 This specifies what command to run when the server receives a WinPopup
3771 This would normally be a command that would deliver the message
3772 somehow\&. How this is to be done is up to your imagination\&.
3776 \f(CW message command = csh -c \'xedit %s;rm %s\' &\fP
3778 This delivers the message using \fBxedit\fP, then removes it
3779 afterwards\&. \fINOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN
3780 IMMEDIATELY\fP\&. That\'s why I have the \f(CW\'&\'\fP on the end\&. If it doesn\'t
3781 return immediately then your PCs may freeze when sending messages
3782 (they should recover after 30secs, hopefully)\&.
3784 All messages are delivered as the global guest user\&. The command takes
3785 the standard substitutions, although \fB%u\fP won\'t work
3786 (\fB%U\fP may be better in this case)\&.
3788 Apart from the standard substitutions, some additional ones apply\&. In
3793 \f(CW"%s"\fP = the filename containing the message\&.
3796 \f(CW"%t"\fP = the destination that the message was sent to (probably the server
3800 \f(CW"%f"\fP = who the message is from\&.
3803 You could make this command send mail, or whatever else takes your
3804 fancy\&. Please let us know of any really interesting ideas you have\&.
3806 Here\'s a way of sending the messages as mail to root:
3808 \f(CWmessage command = /bin/mail -s \'message from %f on %m\' root < %s; rm %s\fP
3810 If you don\'t have a message command then the message won\'t be
3811 delivered and Samba will tell the sender there was an
3812 error\&. Unfortunately WfWg totally ignores the error code and carries
3813 on regardless, saying that the message was delivered\&.
3815 If you want to silently delete it then try:
3817 \f(CW"message command = rm %s"\fP\&.
3820 \f(CW no message command\fP
3823 \f(CW message command = csh -c \'xedit %s;rm %s\' &\fP
3825 .IP "\fBmin print space (S)\fP"
3827 This sets the minimum amount of free disk space that must be available
3828 before a user will be able to spool a print job\&. It is specified in
3829 kilobytes\&. The default is 0, which means a user can always spool a print
3832 See also the \fBprinting\fP parameter\&.
3835 \f(CW min print space = 0\fP
3838 \f(CW min print space = 2000\fP
3840 .IP "\fBmin wins ttl (G)\fP"
3842 This option tells \fBnmbd\fP when acting as a WINS
3843 server \fB(wins support = true)\fP what the minimum
3844 \'time to live\' of NetBIOS names that \fBnmbd\fP will
3845 grant will be (in seconds)\&. You should never need to change this
3846 parameter\&. The default is 6 hours (21600 seconds)\&.
3849 \f(CW min wins ttl = 21600\fP
3851 .IP "\fBname resolve order (G)\fP"
3853 This option is used by the programs in the Samba suite to determine
3854 what naming services and in what order to resolve host names to IP
3855 addresses\&. The option takes a space separated string of different name
3856 resolution options\&.
3858 The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause
3859 names to be resolved as follows :
3863 \fBlmhosts\fP : Lookup an IP address in the Samba lmhosts file\&.
3866 \fBhost\fP : Do a standard host name to IP address resolution,
3867 using the system /etc/hosts, NIS, or DNS lookups\&. This method of name
3868 resolution is operating system depended for instance on IRIX or
3869 Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fP file)\&.
3872 \fBwins\fP : Query a name with the IP address listed in the
3873 \fBwins server\fP parameter\&. If no WINS server has
3874 been specified this method will be ignored\&.
3877 \fBbcast\fP : Do a broadcast on each of the known local interfaces
3878 listed in the \fBinterfaces\fP parameter\&. This is the
3879 least reliable of the name resolution methods as it depends on the
3880 target host being on a locally connected subnet\&.
3884 \f(CW name resolve order = lmhosts host wins bcast\fP
3887 \f(CW name resolve order = lmhosts bcast host\fP
3889 This will cause the local lmhosts file to be examined first, followed
3890 by a broadcast attempt, followed by a normal system hostname lookup\&.
3892 .IP "\fBnetbios aliases (G)\fP"
3894 This is a list of NetBIOS names that \fBnmbd\fP will
3895 advertise as additional names by which the Samba server is known\&. This
3896 allows one machine to appear in browse lists under multiple names\&. If
3897 a machine is acting as a \fBbrowse server\fP or
3898 \fBlogon server\fP none of these names will be
3899 advertised as either browse server or logon servers, only the primary
3900 name of the machine will be advertised with these capabilities\&.
3902 See also \fB"netbios name"\fP\&.
3905 \f(CW empty string (no additional names)\fP
3908 \f(CW netbios aliases = TEST TEST1 TEST2\fP
3910 .IP "\fBnetbios name (G)\fP"
3912 This sets the NetBIOS name by which a Samba server is known\&. By
3913 default it is the same as the first component of the host\'s DNS name\&.
3914 If a machine is a \fBbrowse server\fP or
3915 \fBlogon server\fP this name (or the first component
3916 of the hosts DNS name) will be the name that these services are
3919 See also \fB"netbios aliases"\fP\&.
3922 \f(CW Machine DNS name\&.\fP
3925 \f(CW netbios name = MYNAME\fP
3927 .IP "\fBnis homedir (G)\fP"
3929 Get the home share server from a NIS map\&. For UNIX systems that use an
3930 automounter, the user\'s home directory will often be mounted on a
3931 workstation on demand from a remote server\&.
3933 When the Samba logon server is not the actual home directory server,
3934 but is mounting the home directories via NFS then two network hops
3935 would be required to access the users home directory if the logon
3936 server told the client to use itself as the SMB server for home
3937 directories (one over SMB and one over NFS)\&. This can be very
3940 This option allows Samba to return the home share as being on a
3941 different server to the logon server and as long as a Samba daemon is
3942 running on the home directory server, it will be mounted on the Samba
3943 client directly from the directory server\&. When Samba is returning the
3944 home share to the client, it will consult the NIS map specified in
3945 \fB"homedir map"\fP and return the server listed
3948 Note that for this option to work there must be a working NIS
3949 system and the Samba server with this option must also be a
3950 \fBlogon server\fP\&.
3953 \f(CW nis homedir = false\fP
3956 \f(CW nis homedir = true\fP
3958 .IP "\fBnt pipe support (G)\fP"
3960 This boolean parameter controls whether \fBsmbd\fP
3961 will allow Windows NT clients to connect to the NT SMB specific
3962 \f(CWIPC$\fP pipes\&. This is a developer debugging option and can be left
3966 \f(CW nt pipe support = yes\fP
3968 .IP "\fBnt smb support (G)\fP"
3970 This boolean parameter controls whether \fBsmbd\fP
3971 will negotiate NT specific SMB support with Windows NT
3972 clients\&. Although this is a developer debugging option and should be
3973 left alone, benchmarking has discovered that Windows NT clients give
3974 faster performance with this option set to \f(CW"no"\fP\&. This is still
3975 being investigated\&. If this option is set to \f(CW"no"\fP then Samba
3976 offers exactly the same SMB calls that versions prior to Samba2\&.0
3977 offered\&. This information may be of use if any users are having
3978 problems with NT SMB support\&.
3981 \f(CW nt support = yes\fP
3983 .IP "\fBnull passwords (G)\fP"
3985 Allow or disallow client access to accounts that have null passwords\&.
3987 See also \fBsmbpasswd (5)\fP\&.
3990 \f(CW null passwords = no\fP
3993 \f(CW null passwords = yes\fP
3995 .IP "\fBole locking compatibility (G)\fP"
3997 This parameter allows an administrator to turn off the byte range lock
3998 manipulation that is done within Samba to give compatibility for OLE
3999 applications\&. Windows OLE applications use byte range locking as a
4000 form of inter-process communication, by locking ranges of bytes around
4001 the 2^32 region of a file range\&. This can cause certain UNIX lock
4002 managers to crash or otherwise cause problems\&. Setting this parameter
4003 to \f(CW"no"\fP means you trust your UNIX lock manager to handle such cases
4007 \f(CW ole locking compatibility = yes\fP
4010 \f(CW ole locking compatibility = no\fP
4012 .IP "\fBonly guest (S)\fP"
4014 A synonym for \fB"guest only"\fP\&.
4016 .IP "\fBonly user (S)\fP"
4018 This is a boolean option that controls whether connections with
4019 usernames not in the \fBuser=\fP list will be allowed\&. By
4020 default this option is disabled so a client can supply a username to
4021 be used by the server\&.
4023 Note that this also means Samba won\'t try to deduce usernames from the
4024 service name\&. This can be annoying for the \fB[homes]\fP
4025 section\&. To get around this you could use "\fBuser\fP =
4026 \fB%S\fP" which means your \fB"user"\fP list
4027 will be just the service name, which for home directories is the name
4030 See also the \fBuser\fP parameter\&.
4033 \f(CW only user = False\fP
4036 \f(CW only user = True\fP
4038 .IP "\fBoplocks (S)\fP"
4040 This boolean option tells smbd whether to issue oplocks (opportunistic
4041 locks) to file open requests on this share\&. The oplock code can
4042 dramatically (approx\&. 30% or more) improve the speed of access to files
4043 on Samba servers\&. It allows the clients to aggressively cache files
4044 locally and you may want to disable this option for unreliable network
4045 environments (it is turned on by default in Windows NT Servers)\&. For
4046 more information see the file Speed\&.txt in the Samba docs/ directory\&.
4048 Oplocks may be selectively turned off on certain files on a per share basis\&.
4049 See the \'veto oplock files\' parameter\&. On some systems oplocks are recognized
4050 by the underlying operating system\&. This allows data synchronization between
4051 all access to oplocked files, whether it be via Samba or NFS or a local
4052 UNIX process\&. See the \fBkernel oplocks\fP parameter
4056 \f(CW oplocks = True\fP
4059 \f(CW oplocks = False\fP
4061 .IP "\fBos level (G)\fP"
4063 This integer value controls what level Samba advertises itself as for
4064 browse elections\&. The value of this parameter determines whether
4065 \fBnmbd\fP has a chance of becoming a local master
4066 browser for the \fBWORKGROUP\fP in the local broadcast
4067 area\&. Setting this to zero will cause \fBnmbd\fP to
4068 always lose elections to Windows machines\&. See BROWSING\&.txt in the
4069 Samba docs/ directory for details\&.
4072 \f(CW os level = 32\fP
4075 \f(CW os level = 65 ; This will win against any NT Server\fP
4077 .IP "\fBpacket size (G)\fP"
4079 This is a deprecated parameter that how no effect on the current
4080 Samba code\&. It is left in the parameter list to prevent breaking
4081 old \fBsmb\&.conf\fP files\&.
4083 .IP "\fBpanic action (G)\fP"
4085 This is a Samba developer option that allows a system command to be
4086 called when either \fBsmbd\fP or
4087 \fBnmbd\fP crashes\&. This is usually used to draw
4088 attention to the fact that a problem occurred\&.
4091 \f(CW panic action = <empty string>\fP
4093 .IP "\fBpasswd chat (G)\fP"
4095 This string controls the \fI"chat"\fP conversation that takes places
4096 between \fBsmbd\fP and the local password changing
4097 program to change the users password\&. The string describes a sequence
4098 of response-receive pairs that \fBsmbd\fP uses to
4099 determine what to send to the \fBpasswd\fP program
4100 and what to expect back\&. If the expected output is not received then
4101 the password is not changed\&.
4103 This chat sequence is often quite site specific, depending on what
4104 local methods are used for password control (such as NIS etc)\&.
4106 The string can contain the macros \f(CW"%o"\fP and \f(CW"%n"\fP which are
4107 substituted for the old and new passwords respectively\&. It can also
4108 contain the standard macros \f(CW"\en"\fP, \f(CW"\er"\fP, \f(CW"\et"\fP and \f(CW"\es"\fP
4109 to give line-feed, carriage-return, tab and space\&.
4111 The string can also contain a \f(CW\'*\'\fP which matches any sequence of
4114 Double quotes can be used to collect strings with spaces in them into
4117 If the send string in any part of the chat sequence is a fullstop
4118 \f(CW"\&."\fP then no string is sent\&. Similarly, is the expect string is a
4119 fullstop then no string is expected\&.
4121 Note that if the \fB"unix password sync"\fP
4122 parameter is set to true, then this sequence is called \fI*AS ROOT*\fP
4123 when the SMB password in the smbpasswd file is being changed, without
4124 access to the old password cleartext\&. In this case the old password
4125 cleartext is set to \f(CW""\fP (the empty string)\&.
4127 See also \fB"unix password sync"\fP,
4128 \fB"passwd program"\fP and \fB"passwd chat
4135 passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en "*Reenter NEW password*" %n\en "*Password changed*"
4145 passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed*
4150 .IP "\fBpasswd chat debug (G)\fP"
4152 This boolean specifies if the passwd chat script parameter is run in
4153 \f(CW"debug"\fP mode\&. In this mode the strings passed to and received from
4154 the passwd chat are printed in the \fBsmbd\fP log with
4155 a \fB"debug level"\fP of 100\&. This is a dangerous
4156 option as it will allow plaintext passwords to be seen in the
4157 \fBsmbd\fP log\&. It is available to help Samba admins
4158 debug their \fB"passwd chat"\fP scripts when calling
4159 the \fB"passwd program"\fP and should be turned off
4160 after this has been done\&. This parameter is off by default\&.
4162 See also \fB"passwd chat"\fP, \fB"passwd
4166 \f(CW passwd chat debug = True\fP
4169 \f(CW passwd chat debug = False\fP
4171 .IP "\fBpasswd program (G)\fP"
4173 The name of a program that can be used to set UNIX user passwords\&.
4174 Any occurrences of \fB%u\fP will be replaced with the
4175 user name\&. The user name is checked for existence before calling the
4176 password changing program\&.
4178 Also note that many passwd programs insist in \fI"reasonable"\fP
4179 passwords, such as a minimum length, or the inclusion of mixed case
4180 chars and digits\&. This can pose a problem as some clients (such as
4181 Windows for Workgroups) uppercase the password before sending it\&.
4183 \fINote\fP that if the \fB"unix password sync"\fP
4184 parameter is set to \f(CW"True"\fP then this program is called \fI*AS
4185 ROOT*\fP before the SMB password in the
4186 \fBsmbpasswd\fP file is changed\&. If this UNIX
4187 password change fails, then \fBsmbd\fP will fail to
4188 change the SMB password also (this is by design)\&.
4190 If the \fB"unix password sync"\fP parameter is
4191 set this parameter \fIMUST USE ABSOLUTE PATHS\fP for \fIALL\fP programs
4192 called, and must be examined for security implications\&. Note that by
4193 default \fB"unix password sync"\fP is set to
4196 See also \fB"unix password sync"\fP\&.
4199 \f(CW passwd program = /bin/passwd\fP
4202 \f(CW passwd program = /sbin/passwd %u\fP
4204 .IP "\fBpassword level (G)\fP"
4206 Some client/server combinations have difficulty with mixed-case
4207 passwords\&. One offending client is Windows for Workgroups, which for
4208 some reason forces passwords to upper case when using the LANMAN1
4209 protocol, but leaves them alone when using COREPLUS!
4211 This parameter defines the maximum number of characters that may be
4212 upper case in passwords\&.
4214 For example, say the password given was \f(CW"FRED"\fP\&. If \fBpassword
4215 level\fP is set to 1, the following combinations would be tried if
4216 \f(CW"FRED"\fP failed:
4218 \f(CW"Fred"\fP, \f(CW"fred"\fP, \f(CW"fRed"\fP, \f(CW"frEd"\fP, \f(CW"freD"\fP
4220 If \fBpassword level\fP was set to 2, the following combinations would
4223 \f(CW"FRed"\fP, \f(CW"FrEd"\fP, \f(CW"FreD"\fP, \f(CW"fREd"\fP, \f(CW"fReD"\fP,
4224 \f(CW"frED"\fP, \f(CW\&.\&.\fP
4228 The higher value this parameter is set to the more likely it is that a
4229 mixed case password will be matched against a single case
4230 password\&. However, you should be aware that use of this parameter
4231 reduces security and increases the time taken to process a new
4234 A value of zero will cause only two attempts to be made - the password
4235 as is and the password in all-lower case\&.
4238 \f(CW password level = 0\fP
4241 \f(CW password level = 4\fP
4243 .IP "\fBpassword server (G)\fP"
4245 By specifying the name of another SMB server (such as a WinNT box)
4246 with this option, and using \fB"security = domain"\fP or
4247 \fB"security = server"\fP you can get Samba to do all
4248 its username/password validation via a remote server\&.
4250 This options sets the name of the password server to use\&. It must be a
4251 NetBIOS name, so if the machine\'s NetBIOS name is different from its
4252 internet name then you may have to add its NetBIOS name to the lmhosts
4253 file which is stored in the same directory as the \fBsmb\&.conf\fP file\&.
4255 The name of the password server is looked up using the parameter
4256 \fB"name resolve order="\fP and so may resolved
4257 by any method and order described in that parameter\&.
4259 The password server much be a machine capable of using the "LM1\&.2X002"
4260 or the "LM NT 0\&.12" protocol, and it must be in user level security
4263 NOTE: Using a password server means your UNIX box (running Samba) is
4264 only as secure as your password server\&. \fIDO NOT CHOOSE A PASSWORD
4265 SERVER THAT YOU DON\'T COMPLETELY TRUST\fP\&.
4267 Never point a Samba server at itself for password serving\&. This will
4268 cause a loop and could lock up your Samba server!
4270 The name of the password server takes the standard substitutions, but
4271 probably the only useful one is \fB%m\fP, which means
4272 the Samba server will use the incoming client as the password
4273 server\&. If you use this then you better trust your clients, and you
4274 better restrict them with hosts allow!
4276 If the \fB"security"\fP parameter is set to
4277 \fB"domain"\fP, then the list of machines in this option must be a list
4278 of Primary or Backup Domain controllers for the
4279 \fBDomain\fP, as the Samba server is cryptographicly
4280 in that domain, and will use cryptographicly authenticated RPC calls
4281 to authenticate the user logging on\&. The advantage of using
4282 \fB"security=domain"\fP is that if you list
4283 several hosts in the \fB"password server"\fP option then
4284 \fBsmbd\fP will try each in turn till it finds one
4285 that responds\&. This is useful in case your primary server goes down\&.
4287 If the \fB"security"\fP parameter is set to
4288 \fB"server"\fP, then there are different
4289 restrictions that \fB"security=domain"\fP
4290 doesn\'t suffer from:
4294 You may list several password servers in the \fB"password server"\fP
4295 parameter, however if an \fBsmbd\fP makes a connection
4296 to a password server, and then the password server fails, no more
4297 users will be able to be authenticated from this
4298 \fBsmbd\fP\&. This is a restriction of the SMB/CIFS
4299 protocol when in \fB"security=server"\fP mode
4300 and cannot be fixed in Samba\&.
4303 If you are using a Windows NT server as your password server then
4304 you will have to ensure that your users are able to login from the
4305 Samba server, as when in
4306 \fB"security=server"\fP mode the network
4307 logon will appear to come from there rather than from the users
4311 See also the \fB"security"\fP parameter\&.
4314 \f(CW password server = <empty string>\fP
4317 \f(CW password server = NT-PDC, NT-BDC1, NT-BDC2\fP
4319 .IP "\fBpath (S)\fP"
4321 This parameter specifies a directory to which the user of the service
4322 is to be given access\&. In the case of printable services, this is
4323 where print data will spool prior to being submitted to the host for
4326 For a printable service offering guest access, the service should be
4327 readonly and the path should be world-writeable and have the sticky bit
4328 set\&. This is not mandatory of course, but you probably won\'t get the
4329 results you expect if you do otherwise\&.
4331 Any occurrences of \fB%u\fP in the path will be replaced
4332 with the UNIX username that the client is using on this
4333 connection\&. Any occurrences of \fB%m\fP will be replaced
4334 by the NetBIOS name of the machine they are connecting from\&. These
4335 replacements are very useful for setting up pseudo home directories
4338 Note that this path will be based on \fB"root dir"\fP if
4339 one was specified\&.
4345 \f(CW path = /home/fred\fP
4347 .IP "\fBpostexec (S)\fP"
4349 This option specifies a command to be run whenever the service is
4350 disconnected\&. It takes the usual substitutions\&. The command may be run
4351 as the root on some systems\&.
4353 An interesting example may be do unmount server resources:
4355 \f(CWpostexec = /etc/umount /cdrom\fP
4357 See also \fBpreexec\fP\&.
4360 \f(CW none (no command executed)\fP
4363 \f(CW postexec = echo "%u disconnected from %S from %m (%I)" >> /tmp/log\fP
4365 .IP "\fBpostscript (S)\fP"
4367 This parameter forces a printer to interpret the print files as
4368 postscript\&. This is done by adding a \f(CW%!\fP to the start of print output\&.
4370 This is most useful when you have lots of PCs that persist in putting
4371 a control-D at the start of print jobs, which then confuses your
4375 \f(CW postscript = False\fP
4378 \f(CW postscript = True\fP
4380 .IP "\fBpreexec (S)\fP"
4382 This option specifies a command to be run whenever the service is
4383 connected to\&. It takes the usual substitutions\&.
4385 An interesting example is to send the users a welcome message every
4386 time they log in\&. Maybe a message of the day? Here is an example:
4392 preexec = csh -c \'echo \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient -M %m -I %I\' &
4398 Of course, this could get annoying after a while :-)
4400 See also \fBpostexec\fP\&.
4403 \f(CW none (no command executed)\fP
4406 \f(CW preexec = echo \e"%u connected to %S from %m (%I)\e" >> /tmp/log\fP
4408 .IP "\fBpreferred master (G)\fP"
4410 This boolean parameter controls if \fBnmbd\fP is a
4411 preferred master browser for its workgroup\&.
4413 If this is set to true, on startup, \fBnmbd\fP will
4414 force an election, and it will have a slight advantage in winning the
4415 election\&. It is recommended that this parameter is used in
4416 conjunction with \fB"domain master = yes"\fP, so
4417 that \fBnmbd\fP can guarantee becoming a domain
4418 master\&. Indeed the default ("auto") enables "preferred master" if
4419 Samba is configured as the domain master browser\&.
4421 Use this option with caution, because if there are several hosts
4422 (whether Samba servers, Windows 95 or NT) that are preferred master
4423 browsers on the same subnet, they will each periodically and
4424 continuously attempt to become the local master browser\&. This will
4425 result in unnecessary broadcast traffic and reduced browsing
4428 See also \fBos level\fP\&.
4431 \f(CW preferred master = auto\fP
4434 \f(CW preferred master = yes\fP
4436 .IP "\fBprefered master (G)\fP"
4438 Synonym for \fB"preferred master"\fP for people
4439 who cannot spell :-)\&.
4442 Synonym for \fB"auto services"\fP\&.
4444 .IP "\fBpreserve case (S)\fP"
4446 This controls if new filenames are created with the case that the
4447 client passes, or if they are forced to be the \f(CW"default"\fP case\&.
4450 \f(CW preserve case = yes\fP
4452 See the section on \fB"NAME MANGLING"\fP for a
4453 fuller discussion\&.
4455 .IP "\fBprint command (S)\fP"
4457 After a print job has finished spooling to a service, this command
4458 will be used via a \f(CWsystem()\fP call to process the spool
4459 file\&. Typically the command specified will submit the spool file to
4460 the host\'s printing subsystem, but there is no requirement that this
4461 be the case\&. The server will not remove the spool file, so whatever
4462 command you specify should remove the spool file when it has been
4463 processed, otherwise you will need to manually remove old spool files\&.
4465 The print command is simply a text string\&. It will be used verbatim,
4466 with two exceptions: All occurrences of \f(CW"%s"\fP will be replaced by
4467 the appropriate spool file name, and all occurrences of \f(CW"%p"\fP will
4468 be replaced by the appropriate printer name\&. The spool file name is
4469 generated automatically by the server, the printer name is discussed
4472 The full path name will be used for the filename if \f(CW"%s"\fP is not
4473 preceded by a \f(CW\'/\'\fP\&. If you don\'t like this (it can stuff up some
4474 lpq output) then use \f(CW"%f"\fP instead\&. Any occurrences of \f(CW"%f"\fP get
4475 replaced by the spool filename without the full path at the front\&.
4477 The print command \fIMUST\fP contain at least one occurrence of \f(CW"%s"\fP
4478 or \f(CW"%f"\fP - the \f(CW"%p"\fP is optional\&. At the time a job is
4479 submitted, if no printer name is supplied the \f(CW"%p"\fP will be
4480 silently removed from the printer command\&.
4482 If specified in the \fB"[global]"\fP section, the print
4483 command given will be used for any printable service that does not
4484 have its own print command specified\&.
4486 If there is neither a specified print command for a printable service
4487 nor a global print command, spool files will be created but not
4488 processed and (most importantly) not removed\&.
4490 Note that printing may fail on some UNIXs from the \f(CW"nobody"\fP
4491 account\&. If this happens then create an alternative guest account that
4492 can print and set the \fB"guest account"\fP in the
4493 \fB"[global]"\fP section\&.
4495 You can form quite complex print commands by realizing that they are
4496 just passed to a shell\&. For example the following will log a print
4497 job, print the file, then remove it\&. Note that \f(CW\';\'\fP is the usual
4498 separator for command in shell scripts\&.
4500 \f(CWprint command = echo Printing %s >> /tmp/print\&.log; lpr -P %p %s; rm %s\fP
4502 You may have to vary this command considerably depending on how you
4503 normally print files on your system\&. The default for the parameter
4504 varies depending on the setting of the \fB"printing="\fP
4508 For \fB"printing="\fP BSD, AIX, QNX, LPRNG or PLP :
4509 \f(CW print command = lpr -r -P%p %s\fP
4511 For \fB"printing="\fP SYS or HPUX :
4512 \f(CW print command = lp -c -d%p %s; rm %s\fP
4514 For \fB"printing="\fP SOFTQ :
4515 \f(CW print command = lp -d%p -s %s; rm %s\fP
4518 \f(CW print command = /usr/local/samba/bin/myprintscript %p %s\fP
4520 .IP "\fBprint ok (S)\fP"
4522 Synonym for \fBprintable\fP\&.
4524 .IP "\fBprintable (S)\fP"
4526 If this parameter is \f(CW"yes"\fP, then clients may open, write to and
4527 submit spool files on the directory specified for the service\&.
4529 Note that a printable service will ALWAYS allow writing to the service
4530 path (user privileges permitting) via the spooling of print data\&. The
4531 \fB"read only"\fP parameter controls only non-printing
4532 access to the resource\&.
4535 \f(CW printable = no\fP
4538 \f(CW printable = yes\fP
4540 .IP "\fBprintcap (G)\fP"
4542 Synonym for \fBprintcapname\fP\&.
4544 .IP "\fBprintcap name (G)\fP"
4546 This parameter may be used to override the compiled-in default
4547 printcap name used by the server (usually /etc/printcap)\&. See the
4548 discussion of the \fB[printers]\fP section above for
4549 reasons why you might want to do this\&.
4551 On System V systems that use \fBlpstat\fP to list available printers you
4552 can use \f(CW"printcap name = lpstat"\fP to automatically obtain lists of
4553 available printers\&. This is the default for systems that define SYSV
4554 at configure time in Samba (this includes most System V based
4555 systems)\&. If \fB"printcap name"\fP is set to \fBlpstat\fP on these systems
4556 then Samba will launch \f(CW"lpstat -v"\fP and attempt to parse the output
4557 to obtain a printer list\&.
4559 A minimal printcap file would look something like this:
4575 where the \f(CW\'|\'\fP separates aliases of a printer\&. The fact that the
4576 second alias has a space in it gives a hint to Samba that it\'s a
4579 \fINOTE\fP: Under AIX the default printcap name is
4580 \f(CW"/etc/qconfig"\fP\&. Samba will assume the file is in AIX \f(CW"qconfig"\fP
4581 format if the string \f(CW"/qconfig"\fP appears in the printcap filename\&.
4584 \f(CW printcap name = /etc/printcap\fP
4587 \f(CW printcap name = /etc/myprintcap\fP
4589 .IP "\fBprinter (S)\fP"
4591 This parameter specifies the name of the printer to which print jobs
4592 spooled through a printable service will be sent\&.
4594 If specified in the \fB[global]\fP section, the printer
4595 name given will be used for any printable service that does not have
4596 its own printer name specified\&.
4599 none (but may be \f(CW"lp"\fP on many systems)
4602 printer name = laserwriter
4604 .IP "\fBprinter driver (S)\fP"
4606 This option allows you to control the string that clients receive when
4607 they ask the server for the printer driver associated with a
4608 printer\&. If you are using Windows95 or WindowsNT then you can use this
4609 to automate the setup of printers on your system\&.
4611 You need to set this parameter to the exact string (case sensitive)
4612 that describes the appropriate printer driver for your system\&. If you
4613 don\'t know the exact string to use then you should first try with no
4614 \fB"printer driver"\fP option set and the client will give you a list of
4615 printer drivers\&. The appropriate strings are shown in a scrollbox
4616 after you have chosen the printer manufacturer\&.
4618 See also \fB"printer driver file"\fP\&.
4621 printer driver = HP LaserJet 4L
4623 .IP "\fBprinter driver file (G)\fP"
4625 This parameter tells Samba where the printer driver definition file,
4626 used when serving drivers to Windows 95 clients, is to be found\&. If
4627 this is not set, the default is :
4629 \f(CWSAMBA_INSTALL_DIRECTORY/lib/printers\&.def\fP
4631 This file is created from Windows 95 \f(CW"msprint\&.def"\fP files found on
4632 the Windows 95 client system\&. For more details on setting up serving
4633 of printer drivers to Windows 95 clients, see the documentation file
4634 in the docs/ directory, PRINTER_DRIVER\&.txt\&.
4637 \f(CW None (set in compile)\&.\fP
4640 \f(CW printer driver file = /usr/local/samba/printers/drivers\&.def\fP
4642 See also \fB"printer driver location"\fP\&.
4644 .IP "\fBprinter driver location (S)\fP"
4646 This parameter tells clients of a particular printer share where to
4647 find the printer driver files for the automatic installation of
4648 drivers for Windows 95 machines\&. If Samba is set up to serve printer
4649 drivers to Windows 95 machines, this should be set to
4651 \f(CW\e\eMACHINE\ePRINTER$\fP
4653 Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$
4654 is a share you set up for serving printer driver files\&. For more
4655 details on setting this up see the documentation file in the docs/
4656 directory, PRINTER_DRIVER\&.txt\&.
4662 \f(CW printer driver location = \e\eMACHINE\ePRINTER$\fP
4664 See also \fB"printer driver file"\fP\&.
4666 .IP "\fBprinter name (S)\fP"
4668 Synonym for \fBprinter\fP\&.
4670 .IP "\fBprinting (S)\fP"
4672 This parameters controls how printer status information is interpreted
4673 on your system, and also affects the default values for the
4674 \fB"print command"\fP, \fB"lpq
4675 command"\fP \fB"lppause command"\fP,
4676 \fB"lpresume command"\fP, and \fB"lprm
4679 Currently eight printing styles are supported\&. They are
4680 \fB"printing=BSD"\fP, \fB"printing=AIX"\fP, \fB"printing=LPRNG"\fP,
4681 \fB"printing=PLP"\fP,
4682 \fB"printing=SYSV"\fP,\fB"printing="HPUX"\fP,\fB"printing=QNX"\fP and
4683 \fB"printing=SOFTQ"\fP\&.
4685 To see what the defaults are for the other print commands when using
4686 these three options use the \fB"testparm"\fP program\&.
4688 This option can be set on a per printer basis
4690 See also the discussion in the \fB[printers]\fP section\&.
4692 .IP "\fBprotocol (G)\fP"
4694 The value of the parameter (a string) is the highest protocol level
4695 that will be supported by the server\&.
4697 Possible values are :
4701 CORE: Earliest version\&. No concept of user names\&.
4704 COREPLUS: Slight improvements on CORE for efficiency\&.
4707 LANMAN1: First \fI"modern"\fP version of the protocol\&. Long
4711 LANMAN2: Updates to Lanman1 protocol\&.
4714 NT1: Current up to date version of the protocol\&. Used by Windows
4715 NT\&. Known as CIFS\&.
4718 Normally this option should not be set as the automatic negotiation
4719 phase in the SMB protocol takes care of choosing the appropriate
4723 \f(CW protocol = NT1\fP
4726 \f(CW protocol = LANMAN1\fP
4728 .IP "\fBpublic (S)\fP"
4730 Synonym for \fB"guest ok"\fP\&.
4732 .IP "\fBqueuepause command (S)\fP"
4734 This parameter specifies the command to be executed on the server host
4735 in order to pause the printerqueue\&.
4737 This command should be a program or script which takes a printer name
4738 as its only parameter and stops the printerqueue, such that no longer
4739 jobs are submitted to the printer\&.
4741 This command is not supported by Windows for Workgroups, but can be
4742 issued from the Printer\'s window under Windows 95 & NT\&.
4744 If a \f(CW"%p"\fP is given then the printername is put in its
4745 place\&. Otherwise it is placed at the end of the command\&.
4747 Note that it is good practice to include the absolute path in the
4748 command as the PATH may not be available to the server\&.
4751 \f(CW depends on the setting of "printing ="\fP
4754 \f(CW queuepause command = disable %p\fP
4756 .IP "\fBqueueresume command (S)\fP"
4758 This parameter specifies the command to be executed on the server host
4759 in order to resume the printerqueue\&. It is the command to undo the
4760 behavior that is caused by the previous parameter
4761 (\fB"queuepause command\fP)\&.
4763 This command should be a program or script which takes a printer name
4764 as its only parameter and resumes the printerqueue, such that queued
4765 jobs are resubmitted to the printer\&.
4767 This command is not supported by Windows for Workgroups, but can be
4768 issued from the Printer\'s window under Windows 95 & NT\&.
4770 If a \f(CW"%p"\fP is given then the printername is put in its
4771 place\&. Otherwise it is placed at the end of the command\&.
4773 Note that it is good practice to include the absolute path in the
4774 command as the PATH may not be available to the server\&.
4777 \f(CW depends on the setting of "printing ="\fP
4780 \f(CW queuepause command = enable %p\fP
4782 .IP "\fBread bmpx (G)\fP"
4784 This boolean parameter controls whether \fBsmbd\fP
4785 will support the "Read Block Multiplex" SMB\&. This is now rarely used
4786 and defaults to off\&. You should never need to set this parameter\&.
4791 .IP "\fBread list (S)\fP"
4793 This is a list of users that are given read-only access to a
4794 service\&. If the connecting user is in this list then they will not be
4795 given write access, no matter what the \fB"read only"\fP
4796 option is set to\&. The list can include group names using the syntax
4797 described in the \fB"invalid users"\fP parameter\&.
4799 See also the \fB"write list"\fP parameter and
4800 the \fB"invalid users"\fP parameter\&.
4803 \f(CW read list = <empty string>\fP
4806 \f(CW read list = mary, @students\fP
4808 .IP "\fBread only (S)\fP"
4810 Note that this is an inverted synonym for
4811 \fB"writeable"\fP and \fB"write ok"\fP\&.
4813 See also \fB"writeable"\fP and \fB"write
4816 .IP "\fBread prediction (G)\fP"
4818 \fINOTE\fP: This code is currently disabled in Samba2\&.0 and
4819 may be removed at a later date\&. Hence this parameter has
4822 This options enables or disables the read prediction code used to
4823 speed up reads from the server\&. When enabled the server will try to
4824 pre-read data from the last accessed file that was opened read-only
4825 while waiting for packets\&.
4828 \f(CW read prediction = False\fP
4830 .IP "\fBread raw (G)\fP"
4832 This parameter controls whether or not the server will support the raw
4833 read SMB requests when transferring data to clients\&.
4835 If enabled, raw reads allow reads of 65535 bytes in one packet\&. This
4836 typically provides a major performance benefit\&.
4838 However, some clients either negotiate the allowable block size
4839 incorrectly or are incapable of supporting larger block sizes, and for
4840 these clients you may need to disable raw reads\&.
4842 In general this parameter should be viewed as a system tuning tool and left
4843 severely alone\&. See also \fB"write raw"\fP\&.
4846 \f(CW read raw = yes\fP
4848 .IP "\fBread size (G)\fP"
4850 The option \fB"read size"\fP affects the overlap of disk reads/writes
4851 with network reads/writes\&. If the amount of data being transferred in
4852 several of the SMB commands (currently SMBwrite, SMBwriteX and
4853 SMBreadbraw) is larger than this value then the server begins writing
4854 the data before it has received the whole packet from the network, or
4855 in the case of SMBreadbraw, it begins writing to the network before
4856 all the data has been read from disk\&.
4858 This overlapping works best when the speeds of disk and network access
4859 are similar, having very little effect when the speed of one is much
4860 greater than the other\&.
4862 The default value is 2048, but very little experimentation has been
4863 done yet to determine the optimal value, and it is likely that the
4864 best value will vary greatly between systems anyway\&. A value over
4865 65536 is pointless and will cause you to allocate memory
4869 \f(CW read size = 2048\fP
4872 \f(CW read size = 8192\fP
4874 .IP "\fBremote announce (G)\fP"
4876 This option allows you to setup \fBnmbd\fP to
4877 periodically announce itself to arbitrary IP addresses with an
4878 arbitrary workgroup name\&.
4880 This is useful if you want your Samba server to appear in a remote
4881 workgroup for which the normal browse propagation rules don\'t
4882 work\&. The remote workgroup can be anywhere that you can send IP
4887 \f(CW remote announce = 192\&.168\&.2\&.255/SERVERS 192\&.168\&.4\&.255/STAFF\fP
4889 the above line would cause nmbd to announce itself to the two given IP
4890 addresses using the given workgroup names\&. If you leave out the
4891 workgroup name then the one given in the
4892 \fB"workgroup"\fP parameter is used instead\&.
4894 The IP addresses you choose would normally be the broadcast addresses
4895 of the remote networks, but can also be the IP addresses of known
4896 browse masters if your network config is that stable\&.
4898 See the documentation file BROWSING\&.txt in the docs/ directory\&.
4901 \f(CW remote announce = <empty string>\fP
4904 \f(CW remote announce = 192\&.168\&.2\&.255/SERVERS 192\&.168\&.4\&.255/STAFF\fP
4906 .IP "\fBremote browse sync (G)\fP"
4908 This option allows you to setup \fBnmbd\fP to
4909 periodically request synchronization of browse lists with the master
4910 browser of a samba server that is on a remote segment\&. This option
4911 will allow you to gain browse lists for multiple workgroups across
4912 routed networks\&. This is done in a manner that does not work with any
4913 non-samba servers\&.
4915 This is useful if you want your Samba server and all local clients to
4916 appear in a remote workgroup for which the normal browse propagation
4917 rules don\'t work\&. The remote workgroup can be anywhere that you can
4918 send IP packets to\&.
4922 \f(CW remote browse sync = 192\&.168\&.2\&.255 192\&.168\&.4\&.255\fP
4924 the above line would cause \fBnmbd\fP to request the
4925 master browser on the specified subnets or addresses to synchronize
4926 their browse lists with the local server\&.
4928 The IP addresses you choose would normally be the broadcast addresses
4929 of the remote networks, but can also be the IP addresses of known
4930 browse masters if your network config is that stable\&. If a machine IP
4931 address is given Samba makes NO attempt to validate that the remote
4932 machine is available, is listening, nor that it is in fact the browse
4933 master on it\'s segment\&.
4936 \f(CW remote browse sync = <empty string>\fP
4939 \f(CW remote browse sync = 192\&.168\&.2\&.255 192\&.168\&.4\&.255\fP
4941 .IP "\fBrevalidate (S)\fP"
4943 Note that this option only works with
4944 \fB"security=share"\fP and will be ignored if
4945 this is not the case\&.
4947 This option controls whether Samba will allow a previously validated
4948 username/password pair to be used to attach to a share\&. Thus if you
4949 connect to \f(CW\e\eserver\eshare1\fP then to \f(CW\e\eserver\eshare2\fP it won\'t
4950 automatically allow the client to request connection to the second
4951 share as the same username as the first without a password\&.
4953 If \fB"revalidate"\fP is \f(CW"True"\fP then the client will be denied
4954 automatic access as the same username\&.
4957 \f(CW revalidate = False\fP
4960 \f(CW revalidate = True\fP
4962 .IP "\fBroot (G)\fP"
4964 Synonym for \fB"root directory"\fP\&.
4966 .IP "\fBroot dir (G)\fP"
4968 Synonym for \fB"root directory"\fP\&.
4970 .IP "\fBroot directory (G)\fP"
4972 The server will \f(CW"chroot()"\fP (i\&.e\&. Change it\'s root directory) to
4973 this directory on startup\&. This is not strictly necessary for secure
4974 operation\&. Even without it the server will deny access to files not in
4975 one of the service entries\&. It may also check for, and deny access to,
4976 soft links to other parts of the filesystem, or attempts to use
4977 \f(CW"\&.\&."\fP in file names to access other directories (depending on the
4978 setting of the \fB"wide links"\fP parameter)\&.
4980 Adding a \fB"root directory"\fP entry other than \f(CW"/"\fP adds an extra
4981 level of security, but at a price\&. It absolutely ensures that no
4982 access is given to files not in the sub-tree specified in the \fB"root
4983 directory"\fP option, \fI*including*\fP some files needed for complete
4984 operation of the server\&. To maintain full operability of the server
4985 you will need to mirror some system files into the \fB"root
4986 directory"\fP tree\&. In particular you will need to mirror /etc/passwd
4987 (or a subset of it), and any binaries or configuration files needed
4988 for printing (if required)\&. The set of files that must be mirrored is
4989 operating system dependent\&.
4992 \f(CW root directory = /\fP
4995 \f(CW root directory = /homes/smb\fP
4997 .IP "\fBroot postexec (S)\fP"
4999 This is the same as the \fB"postexec"\fP parameter
5000 except that the command is run as root\&. This is useful for unmounting
5001 filesystems (such as cdroms) after a connection is closed\&.
5003 See also \fB"postexec"\fP\&.
5005 .IP "\fBroot preexec (S)\fP"
5007 This is the same as the \fB"preexec"\fP parameter except
5008 that the command is run as root\&. This is useful for mounting
5009 filesystems (such as cdroms) before a connection is finalized\&.
5011 See also \fB"preexec"\fP\&.
5013 .IP "\fBsecurity (G)\fP"
5015 This option affects how clients respond to Samba and is one of the most
5016 important settings in the \fBsmb\&.conf\fP file\&.
5018 The option sets the \f(CW"security mode bit"\fP in replies to protocol
5019 negotiations with \fBsmbd\fP to turn share level
5020 security on or off\&. Clients decide based on this bit whether (and how)
5021 to transfer user and password information to the server\&.
5023 The default is "security=user", as this is
5024 the most common setting needed when talking to Windows 98 and Windows
5027 The alternatives are \fB"security = share"\fP,
5028 \fB"security = server"\fP or
5029 \fB"security=domain"\fP\&.
5031 \fI*****NOTE THAT THIS DEFAULT IS DIFFERENT IN SAMBA2\&.0 THAN FOR
5032 PREVIOUS VERSIONS OF SAMBA *******\fP\&.
5034 In previous versions of Samba the default was
5035 \fB"security=share"\fP mainly because that was
5036 the only option at one stage\&.
5038 There is a bug in WfWg that has relevance to this setting\&. When in
5039 user or server level security a WfWg client will totally ignore the
5040 password you type in the "connect drive" dialog box\&. This makes it
5041 very difficult (if not impossible) to connect to a Samba service as
5042 anyone except the user that you are logged into WfWg as\&.
5044 If your PCs use usernames that are the same as their usernames on the
5045 UNIX machine then you will want to use \fB"security = user"\fP\&. If you
5046 mostly use usernames that don\'t exist on the UNIX box then use
5047 \fB"security = share"\fP\&.
5049 You should also use \fBsecurity=share\fP if
5050 you want to mainly setup shares without a password (guest
5051 shares)\&. This is commonly used for a shared printer server\&. It is more
5052 difficult to setup guest shares with
5053 \fBsecurity=user\fP, see the \fB"map to
5054 guest"\fPparameter for details\&.
5056 It is possible to use \fBsmbd\fP in a \fI"hybrid
5057 mode"\fP where it is offers both user and share level security under
5058 different \fBNetBIOS aliases\fP\&. See the
5059 \fBNetBIOS aliases\fP and the
5060 \fBinclude\fP parameters for more information\&.
5062 The different settings will now be explained\&.
5065 .IP "\fB"security=share"\fP"
5066 When clients connect to a share level
5067 security server then need not log onto the server with a valid
5068 username and password before attempting to connect to a shared
5069 resource (although modern clients such as Windows 95/98 and Windows NT
5070 will send a logon request with a username but no password when talking
5071 to a \fBsecurity=share\fP server)\&. Instead, the clients send
5072 authentication information (passwords) on a per-share basis, at the
5073 time they attempt to connect to that share\&.
5075 Note that \fBsmbd\fP \fI*ALWAYS*\fP uses a valid UNIX
5076 user to act on behalf of the client, even in \fB"security=share"\fP
5079 As clients are not required to send a username to the server
5080 in share level security, \fBsmbd\fP uses several
5081 techniques to determine the correct UNIX user to use on behalf
5084 A list of possible UNIX usernames to match with the given
5085 client password is constructed using the following methods :
5089 If the \fB"guest only"\fP parameter is set, then
5090 all the other stages are missed and only the \fB"guest
5091 account"\fP username is checked\&.
5094 Is a username is sent with the share connection request, then
5095 this username (after mapping - see \fB"username
5096 map"\fP), is added as a potential username\&.
5099 If the client did a previous \fI"logon"\fP request (the
5100 SessionSetup SMB call) then the username sent in this SMB
5101 will be added as a potential username\&.
5104 The name of the service the client requested is added
5105 as a potential username\&.
5108 The NetBIOS name of the client is added to the list as a
5109 potential username\&.
5112 Any users on the \fB"user"\fP list are added
5113 as potential usernames\&.
5116 If the \fB"guest only"\fP parameter is not set, then
5117 this list is then tried with the supplied password\&. The first user for
5118 whom the password matches will be used as the UNIX user\&.
5120 If the \fB"guest only"\fP parameter is set, or no
5121 username can be determined then if the share is marked as available to
5122 the \fB"guest account"\fP, then this guest user will
5123 be used, otherwise access is denied\&.
5125 Note that it can be \fI*very*\fP confusing in share-level security as to
5126 which UNIX username will eventually be used in granting access\&.
5128 See also the section \fB"NOTE ABOUT USERNAME/PASSWORD
5131 .IP "\fB"security=user"\fP"
5133 This is the default security setting in Samba2\&.0\&. With user-level
5134 security a client must first \f(CW"log-on"\fP with a valid username and
5135 password (which can be mapped using the \fB"username
5136 map"\fP parameter)\&. Encrypted passwords (see the
5137 \fB"encrypted passwords"\fP parameter) can also
5138 be used in this security mode\&. Parameters such as
5139 \fB"user"\fP and \fB"guest only"\fP, if set
5140 are then applied and may change the UNIX user to use on this
5141 connection, but only after the user has been successfully
5144 \fINote\fP that the name of the resource being requested is
5145 \fI*not*\fP sent to the server until after the server has successfully
5146 authenticated the client\&. This is why guest shares don\'t work in user
5147 level security without allowing the server to automatically map unknown
5148 users into the \fB"guest account"\fP\&. See the
5149 \fB"map to guest"\fP parameter for details on
5152 See also the section \fB"NOTE ABOUT USERNAME/PASSWORD
5155 .IP "\fB"security=server"\fP"
5157 In this mode Samba will try to validate the username/password by
5158 passing it to another SMB server, such as an NT box\&. If this fails it
5159 will revert to \fB"security = user"\fP, but note that if encrypted
5160 passwords have been negotiated then Samba cannot revert back to
5161 checking the UNIX password file, it must have a valid smbpasswd file
5162 to check users against\&. See the documentation file in the docs/
5163 directory ENCRYPTION\&.txt for details on how to set this up\&.
5165 \fINote\fP that from the clients point of view \fB"security=server"\fP is
5166 the same as \fB"security=user"\fP\&. It only
5167 affects how the server deals with the authentication, it does not in
5168 any way affect what the client sees\&.
5170 \fINote\fP that the name of the resource being requested is
5171 \fI*not*\fP sent to the server until after the server has successfully
5172 authenticated the client\&. This is why guest shares don\'t work in server
5173 level security without allowing the server to automatically map unknown
5174 users into the \fB"guest account"\fP\&. See the
5175 \fB"map to guest"\fP parameter for details on
5178 See also the section \fB"NOTE ABOUT USERNAME/PASSWORD
5181 See also the \fB"password server"\fP parameter\&.
5182 and the \fB"encrypted passwords"\fP parameter\&.
5184 .IP "\fB"security=domain"\fP"
5186 This mode will only work correctly if
5187 \fBsmbpasswd\fP has been used to add this machine
5188 into a Windows NT Domain\&. It expects the \fB"encrypted
5189 passwords"\fP parameter to be set to \f(CW"true"\fP\&. In
5190 this mode Samba will try to validate the username/password by passing
5191 it to a Windows NT Primary or Backup Domain Controller, in exactly the
5192 same way that a Windows NT Server would do\&.
5194 \fINote\fP that a valid UNIX user must still exist as well as the
5195 account on the Domain Controller to allow Samba to have a valid
5196 UNIX account to map file access to\&.
5198 \fINote\fP that from the clients point of view \fB"security=domain"\fP is
5199 the same as \fB"security=user"\fP\&. It only
5200 affects how the server deals with the authentication, it does not in
5201 any way affect what the client sees\&.
5203 \fINote\fP that the name of the resource being requested is
5204 \fI*not*\fP sent to the server until after the server has successfully
5205 authenticated the client\&. This is why guest shares don\'t work in domain
5206 level security without allowing the server to automatically map unknown
5207 users into the \fB"guest account"\fP\&. See the
5208 \fB"map to guest"\fP parameter for details on
5211 e,(BUG:) There is currently a bug in the implementation of
5212 \fB"security=domain\fP with respect to multi-byte character
5213 set usernames\&. The communication with a Domain Controller
5214 must be done in UNICODE and Samba currently does not widen
5215 multi-byte user names to UNICODE correctly, thus a multi-byte
5216 username will not be recognized correctly at the Domain Controller\&.
5217 This issue will be addressed in a future release\&.
5219 See also the section \fB"NOTE ABOUT USERNAME/PASSWORD
5222 See also the \fB"password server"\fP parameter\&.
5223 and the \fB"encrypted passwords"\fP parameter\&.
5227 \f(CW security = USER\fP
5230 \f(CW security = DOMAIN\fP
5232 .IP "\fBserver string (G)\fP"
5234 This controls what string will show up in the printer comment box in
5235 print manager and next to the IPC connection in \f(CW"net view"\fP\&. It can be
5236 any string that you wish to show to your users\&.
5238 It also sets what will appear in browse lists next to the machine
5241 A \f(CW"%v"\fP will be replaced with the Samba version number\&.
5243 A \f(CW"%h"\fP will be replaced with the hostname\&.
5246 \f(CW server string = Samba %v\fP
5249 \f(CW server string = University of GNUs Samba Server\fP
5251 .IP "\fBset directory (S)\fP"
5253 If \f(CW"set directory = no"\fP, then users of the service may not use the
5254 setdir command to change directory\&.
5256 The setdir command is only implemented in the Digital Pathworks
5257 client\&. See the Pathworks documentation for details\&.
5260 \f(CW set directory = no\fP
5263 \f(CW set directory = yes\fP
5265 .IP "\fBshare modes (S)\fP"
5267 This enables or disables the honoring of the \f(CW"share modes"\fP during a
5268 file open\&. These modes are used by clients to gain exclusive read or
5269 write access to a file\&.
5271 These open modes are not directly supported by UNIX, so they are
5272 simulated using shared memory, or lock files if your UNIX doesn\'t
5273 support shared memory (almost all do)\&.
5275 The share modes that are enabled by this option are DENY_DOS,
5276 DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB\&.
5278 This option gives full share compatibility and enabled by default\&.
5280 You should \fI*NEVER*\fP turn this parameter off as many Windows
5281 applications will break if you do so\&.
5284 \f(CW share modes = yes\fP
5286 .IP "\fBshared mem size (G)\fP"
5288 It specifies the size of the shared memory (in bytes) to use between
5289 \fBsmbd\fP processes\&. This parameter defaults to one
5290 megabyte of shared memory\&. It is possible that if you have a large
5291 server with many files open simultaneously that you may need to
5292 increase this parameter\&. Signs that this parameter is set too low are
5293 users reporting strange problems trying to save files (locking errors)
5294 and error messages in the smbd log looking like \f(CW"ERROR
5295 smb_shm_alloc : alloc of XX bytes failed"\fP\&.
5298 \f(CW shared mem size = 1048576\fP
5301 \f(CW shared mem size = 5242880 ; Set to 5mb for a large number of files\&.\fP
5303 .IP "\fBshort preserve case (S)\fP"
5305 This boolean parameter controls if new files which conform to 8\&.3
5306 syntax, that is all in upper case and of suitable length, are created
5307 upper case, or if they are forced to be the \f(CW"default"\fP case\&. This
5308 option can be use with \fB"preserve case
5309 =yes"\fP to permit long filenames to retain their
5310 case, while short names are lowered\&. Default \fIYes\fP\&.
5312 See the section on \fBNAME MANGLING\fP\&.
5315 \f(CW short preserve case = yes\fP
5317 .IP "\fBsmb passwd file (G)\fP"
5319 This option sets the path to the encrypted smbpasswd file\&. By default
5320 the path to the smbpasswd file is compiled into Samba\&.
5323 \f(CW smb passwd file= <compiled default>\fP
5326 \f(CW smb passwd file = /usr/samba/private/smbpasswd\fP
5328 .IP "\fBsmbrun (G)\fP"
5330 This sets the full path to the \fBsmbrun\fP binary\&. This defaults to the
5331 value in the Makefile\&.
5333 You must get this path right for many services to work correctly\&.
5335 You should not need to change this parameter so long as Samba
5336 is installed correctly\&.
5339 \f(CW smbrun=<compiled default>\fP
5342 \f(CW smbrun = /usr/local/samba/bin/smbrun\fP
5344 .IP "\fBsocket address (G)\fP"
5346 This option allows you to control what address Samba will listen for
5347 connections on\&. This is used to support multiple virtual interfaces on
5348 the one server, each with a different configuration\&.
5350 By default samba will accept connections on any address\&.
5353 \f(CW socket address = 192\&.168\&.2\&.20\fP
5355 .IP "\fBsocket options (G)\fP"
5357 This option allows you to set socket options to be used when talking
5360 Socket options are controls on the networking layer of the operating
5361 systems which allow the connection to be tuned\&.
5363 This option will typically be used to tune your Samba server for
5364 optimal performance for your local network\&. There is no way that Samba
5365 can know what the optimal parameters are for your net, so you must
5366 experiment and choose them yourself\&. We strongly suggest you read the
5367 appropriate documentation for your operating system first (perhaps
5368 \fB"man setsockopt"\fP will help)\&.
5370 You may find that on some systems Samba will say "Unknown socket
5371 option" when you supply an option\&. This means you either incorrectly
5372 typed it or you need to add an include file to includes\&.h for your OS\&.
5373 If the latter is the case please send the patch to
5374 \fIsamba-bugs@samba\&.org\fP\&.
5376 Any of the supported socket options may be combined in any way you
5377 like, as long as your OS allows it\&.
5379 This is the list of socket options currently settable using this
5414 Those marked with a \f(CW*\fP take an integer argument\&. The others can
5415 optionally take a 1 or 0 argument to enable or disable the option, by
5416 default they will be enabled if you don\'t specify 1 or 0\&.
5418 To specify an argument use the syntax SOME_OPTION=VALUE for example
5419 \f(CWSO_SNDBUF=8192\fP\&. Note that you must not have any spaces before or after
5422 If you are on a local network then a sensible option might be
5424 \f(CWsocket options = IPTOS_LOWDELAY\fP
5426 If you have a local network then you could try:
5428 \f(CWsocket options = IPTOS_LOWDELAY TCP_NODELAY\fP
5430 If you are on a wide area network then perhaps try setting
5433 Note that several of the options may cause your Samba server to fail
5434 completely\&. Use these options with caution!
5437 \f(CW socket options = TCP_NODELAY\fP
5440 \f(CW socket options = IPTOS_LOWDELAY\fP
5444 This variable is part of SSL-enabled Samba\&. This is only available if
5445 the SSL libraries have been compiled on your system and the configure
5446 option \f(CW"--with-ssl"\fP was given at configure time\&.
5448 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5449 enabled by default in any current binary version of Samba\&.
5451 This variable enables or disables the entire SSL mode\&. If it is set to
5452 "no", the SSL enabled samba behaves exactly like the non-SSL samba\&. If
5453 set to "yes", it depends on the variables \fB"ssl
5454 hosts"\fP and \fB"ssl hosts resign"\fP
5455 whether an SSL connection will be required\&.
5462 .IP "\fBssl CA certDir (G)\fP"
5464 This variable is part of SSL-enabled Samba\&. This is only available if
5465 the SSL libraries have been compiled on your system and the configure
5466 option \f(CW"--with-ssl"\fP was given at configure time\&.
5468 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5469 enabled by default in any current binary version of Samba\&.
5471 This variable defines where to look up the Certification
5472 Authorities\&. The given directory should contain one file for each CA
5473 that samba will trust\&. The file name must be the hash value over the
5474 "Distinguished Name" of the CA\&. How this directory is set up is
5475 explained later in this document\&. All files within the directory that
5476 don\'t fit into this naming scheme are ignored\&. You don\'t need this
5477 variable if you don\'t verify client certificates\&.
5480 \f(CW ssl CA certDir = /usr/local/ssl/certs\fP
5482 .IP "\fBssl CA certFile (G)\fP"
5484 This variable is part of SSL-enabled Samba\&. This is only available if
5485 the SSL libraries have been compiled on your system and the configure
5486 option \f(CW"--with-ssl"\fP was given at configure time\&.
5488 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5489 enabled by default in any current binary version of Samba\&.
5491 This variable is a second way to define the trusted CAs\&. The
5492 certificates of the trusted CAs are collected in one big file and this
5493 variable points to the file\&. You will probably only use one of the two
5494 ways to define your CAs\&. The first choice is preferable if you have
5495 many CAs or want to be flexible, the second is preferable if you only
5496 have one CA and want to keep things simple (you won\'t need to create
5497 the hashed file names)\&. You don\'t need this variable if you don\'t
5498 verify client certificates\&.
5501 \f(CW ssl CA certFile = /usr/local/ssl/certs/trustedCAs\&.pem\fP
5503 .IP "\fBssl ciphers (G)\fP"
5505 This variable is part of SSL-enabled Samba\&. This is only available if
5506 the SSL libraries have been compiled on your system and the configure
5507 option \f(CW"--with-ssl"\fP was given at configure time\&.
5509 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5510 enabled by default in any current binary version of Samba\&.
5512 This variable defines the ciphers that should be offered during SSL
5513 negotiation\&. You should not set this variable unless you know what you
5516 .IP "\fBssl client cert (G)\fP"
5518 This variable is part of SSL-enabled Samba\&. This is only available if
5519 the SSL libraries have been compiled on your system and the configure
5520 option \f(CW"--with-ssl"\fP was given at configure time\&.
5522 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5523 enabled by default in any current binary version of Samba\&.
5525 The certificate in this file is used by
5526 \fBsmbclient\fP if it exists\&. It\'s needed if the
5527 server requires a client certificate\&.
5530 \f(CW ssl client cert = /usr/local/ssl/certs/smbclient\&.pem\fP
5532 .IP "\fBssl client key (G)\fP"
5534 This variable is part of SSL-enabled Samba\&. This is only available if
5535 the SSL libraries have been compiled on your system and the configure
5536 option \f(CW"--with-ssl"\fP was given at configure time\&.
5538 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5539 enabled by default in any current binary version of Samba\&.
5541 This is the private key for \fBsmbclient\fP\&. It\'s
5542 only needed if the client should have a certificate\&.
5545 \f(CW ssl client key = /usr/local/ssl/private/smbclient\&.pem\fP
5547 .IP "\fBssl compatibility (G)\fP"
5549 This variable is part of SSL-enabled Samba\&. This is only available if
5550 the SSL libraries have been compiled on your system and the configure
5551 option \f(CW"--with-ssl"\fP was given at configure time\&.
5553 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5554 enabled by default in any current binary version of Samba\&.
5556 This variable defines whether SSLeay should be configured for bug
5557 compatibility with other SSL implementations\&. This is probably not
5558 desirable because currently no clients with SSL implementations other
5559 than SSLeay exist\&.
5562 \f(CW ssl compatibility = no\fP
5564 .IP "\fBssl hosts (G)\fP"
5566 See \fB"ssl hosts resign"\fP\&.
5568 .IP "\fBssl hosts resign (G)\fP"
5570 This variable is part of SSL-enabled Samba\&. This is only available if
5571 the SSL libraries have been compiled on your system and the configure
5572 option \f(CW"--with-ssl"\fP was given at configure time\&.
5574 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5575 enabled by default in any current binary version of Samba\&.
5577 These two variables define whether samba will go into SSL mode or
5578 not\&. If none of them is defined, samba will allow only SSL
5579 connections\&. If the \fB"ssl hosts"\fP variable lists
5580 hosts (by IP-address, IP-address range, net group or name), only these
5581 hosts will be forced into SSL mode\&. If the \fB"ssl hosts resign"\fP
5582 variable lists hosts, only these hosts will NOT be forced into SSL
5583 mode\&. The syntax for these two variables is the same as for the
5584 \fB"hosts allow"\fP and \fB"hosts
5585 deny"\fP pair of variables, only that the subject of the
5586 decision is different: It\'s not the access right but whether SSL is
5587 used or not\&. See the \fB"allow hosts"\fP parameter for
5588 details\&. The example below requires SSL connections from all hosts
5589 outside the local net (which is 192\&.168\&.*\&.*)\&.
5592 \f(CW ssl hosts = <empty string>\fP
5593 \f(CW ssl hosts resign = <empty string>\fP
5596 \f(CW ssl hosts resign = 192\&.168\&.\fP
5598 .IP "\fBssl require clientcert (G)\fP"
5600 This variable is part of SSL-enabled Samba\&. This is only available if
5601 the SSL libraries have been compiled on your system and the configure
5602 option \f(CW"--with-ssl"\fP was given at configure time\&.
5604 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5605 enabled by default in any current binary version of Samba\&.
5607 If this variable is set to \f(CW"yes"\fP, the server will not tolerate
5608 connections from clients that don\'t have a valid certificate\&. The
5609 directory/file given in \fB"ssl CA certDir"\fP and
5610 \fB"ssl CA certFile"\fP will be used to look up the
5611 CAs that issued the client\'s certificate\&. If the certificate can\'t be
5612 verified positively, the connection will be terminated\&. If this
5613 variable is set to \f(CW"no"\fP, clients don\'t need certificates\&. Contrary
5614 to web applications you really \fI*should*\fP require client
5615 certificates\&. In the web environment the client\'s data is sensitive
5616 (credit card numbers) and the server must prove to be trustworthy\&. In
5617 a file server environment the server\'s data will be sensitive and the
5618 clients must prove to be trustworthy\&.
5621 \f(CW ssl require clientcert = no\fP
5623 .IP "\fBssl require servercert (G)\fP"
5625 This variable is part of SSL-enabled Samba\&. This is only available if
5626 the SSL libraries have been compiled on your system and the configure
5627 option \f(CW"--with-ssl"\fP was given at configure time\&.
5629 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5630 enabled by default in any current binary version of Samba\&.
5632 If this variable is set to \f(CW"yes"\fP, the
5633 \fBsmbclient\fP will request a certificate from
5634 the server\&. Same as \fB"ssl require
5635 clientcert"\fP for the server\&.
5638 \f(CW ssl require servercert = no\fP
5640 .IP "\fBssl server cert (G)\fP"
5642 This variable is part of SSL-enabled Samba\&. This is only available if
5643 the SSL libraries have been compiled on your system and the configure
5644 option \f(CW"--with-ssl"\fP was given at configure time\&.
5646 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5647 enabled by default in any current binary version of Samba\&.
5649 This is the file containing the server\'s certificate\&. The server _must_
5650 have a certificate\&. The file may also contain the server\'s private key\&.
5651 See later for how certificates and private keys are created\&.
5654 \f(CW ssl server cert = <empty string>\fP
5656 .IP "\fBssl server key (G)\fP"
5658 This variable is part of SSL-enabled Samba\&. This is only available if
5659 the SSL libraries have been compiled on your system and the configure
5660 option \f(CW"--with-ssl"\fP was given at configure time\&.
5662 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5663 enabled by default in any current binary version of Samba\&.
5665 This file contains the private key of the server\&. If this variable is
5666 not defined, the key is looked up in the certificate file (it may be
5667 appended to the certificate)\&. The server \fI*must*\fP have a private key
5668 and the certificate \fI*must*\fP match this private key\&.
5671 \f(CW ssl server key = <empty string>\fP
5673 .IP "\fBssl version (G)\fP"
5675 This variable is part of SSL-enabled Samba\&. This is only available if
5676 the SSL libraries have been compiled on your system and the configure
5677 option \f(CW"--with-ssl"\fP was given at configure time\&.
5679 \fINote\fP that for export control reasons this code is \fI**NOT**\fP
5680 enabled by default in any current binary version of Samba\&.
5682 This enumeration variable defines the versions of the SSL protocol
5683 that will be used\&. \f(CW"ssl2or3"\fP allows dynamic negotiation of SSL v2
5684 or v3, \f(CW"ssl2"\fP results in SSL v2, \f(CW"ssl3"\fP results in SSL v3 and
5685 "tls1" results in TLS v1\&. TLS (Transport Layer Security) is the
5686 (proposed?) new standard for SSL\&.
5689 \f(CW ssl version = "ssl2or3"\fP
5691 .IP "\fBstat cache (G)\fP"
5693 This parameter determines if \fBsmbd\fP will use a
5694 cache in order to speed up case insensitive name mappings\&. You should
5695 never need to change this parameter\&.
5698 \f(CW stat cache = yes\fP
5700 .IP "\fBstat cache size (G)\fP"
5702 This parameter determines the number of entries in the \fBstat
5703 cache\fP\&. You should never need to change this parameter\&.
5706 \f(CW stat cache size = 50\fP
5708 .IP "\fBstatus (G)\fP"
5710 This enables or disables logging of connections to a status file that
5711 \fBsmbstatus\fP can read\&.
5713 With this disabled \fBsmbstatus\fP won\'t be able
5714 to tell you what connections are active\&. You should never need to
5715 change this parameter\&.
5720 .IP "\fBstrict locking (S)\fP"
5722 This is a boolean that controls the handling of file locking in the
5723 server\&. When this is set to \f(CW"yes"\fP the server will check every read and
5724 write access for file locks, and deny access if locks exist\&. This can
5725 be slow on some systems\&.
5727 When strict locking is \f(CW"no"\fP the server does file lock checks only
5728 when the client explicitly asks for them\&.
5730 Well behaved clients always ask for lock checks when it is important,
5731 so in the vast majority of cases \fB"strict locking = no"\fP is
5735 \f(CW strict locking = no\fP
5738 \f(CW strict locking = yes\fP
5740 .IP "\fBstrict sync (S)\fP"
5742 Many Windows applications (including the Windows 98 explorer shell)
5743 seem to confuse flushing buffer contents to disk with doing a sync to
5744 disk\&. Under UNIX, a sync call forces the process to be suspended until
5745 the kernel has ensured that all outstanding data in kernel disk
5746 buffers has been safely stored onto stable storage\&. This is very slow
5747 and should only be done rarely\&. Setting this parameter to "no" (the
5748 default) means that smbd ignores the Windows applications requests for
5749 a sync call\&. There is only a possibility of losing data if the
5750 operating system itself that Samba is running on crashes, so there is
5751 little danger in this default setting\&. In addition, this fixes many
5752 performance problems that people have reported with the new Windows98
5753 explorer shell file copies\&.
5755 See also the \fB"sync always"\fP parameter\&.
5758 \f(CW strict sync = no\fP
5761 \f(CW strict sync = yes\fP
5763 .IP "\fBstrip dot (G)\fP"
5765 This is a boolean that controls whether to strip trailing dots off
5766 UNIX filenames\&. This helps with some CDROMs that have filenames ending
5770 \f(CW strip dot = no\fP
5773 \f(CW strip dot = yes\fP
5775 .IP "\fBsync always (S)\fP"
5777 This is a boolean parameter that controls whether writes will always
5778 be written to stable storage before the write call returns\&. If this is
5779 false then the server will be guided by the client\'s request in each
5780 write call (clients can set a bit indicating that a particular write
5781 should be synchronous)\&. If this is true then every write will be
5782 followed by a fsync() call to ensure the data is written to disk\&.
5783 Note that the \fB"strict sync"\fP parameter must be
5784 set to \f(CW"yes"\fP in order for this parameter to have any affect\&.
5786 See also the \fB"strict sync"\fP parameter\&.
5789 \f(CW sync always = no\fP
5792 \f(CW sync always = yes\fP
5794 .IP "\fBsyslog (G)\fP"
5796 This parameter maps how Samba debug messages are logged onto the
5797 system syslog logging levels\&. Samba debug level zero maps onto syslog
5798 LOG_ERR, debug level one maps onto LOG_WARNING, debug level two maps
5799 to LOG_NOTICE, debug level three maps onto LOG_INFO\&. The parameter
5800 sets the threshold for doing the mapping, all Samba debug messages
5801 above this threshold are mapped to syslog LOG_DEBUG messages\&.
5806 .IP "\fBsyslog only (G)\fP"
5808 If this parameter is set then Samba debug messages are logged into the
5809 system syslog only, and not to the debug log files\&.
5812 \f(CW syslog only = no\fP
5814 .IP "\fBtime offset (G)\fP"
5816 This parameter is a setting in minutes to add to the normal GMT to
5817 local time conversion\&. This is useful if you are serving a lot of PCs
5818 that have incorrect daylight saving time handling\&.
5821 \f(CW time offset = 0\fP
5824 \f(CW time offset = 60\fP
5827 .IP "\fBtime server (G)\fP"
5829 This parameter determines if \fBnmbd\fP advertises
5830 itself as a time server to Windows clients\&. The default is False\&.
5833 \f(CW time server = False\fP
5836 \f(CW time server = True\fP
5838 .IP "\fBtimestamp logs (G)\fP"
5840 Samba2\&.0 will a timestamps to all log entries by default\&. This
5841 can be distracting if you are attempting to debug a problem\&. This
5842 parameter allows the timestamping to be turned off\&.
5845 \f(CW timestamp logs = True\fP
5848 \f(CW timestamp logs = False\fP
5850 .IP "\fBunix password sync (G)\fP"
5852 This boolean parameter controls whether Samba attempts to synchronize
5853 the UNIX password with the SMB password when the encrypted SMB
5854 password in the smbpasswd file is changed\&. If this is set to true the
5855 program specified in the \fB"passwd program"\fP
5856 parameter is called \fI*AS ROOT*\fP - to allow the new UNIX password to be
5857 set without access to the old UNIX password (as the SMB password has
5858 change code has no access to the old password cleartext, only the
5859 new)\&. By default this is set to \f(CW"false"\fP\&.
5861 See also \fB"passwd program"\fP, \fB"passwd
5865 \f(CW unix password sync = False\fP
5868 \f(CW unix password sync = True\fP
5870 .IP "\fBunix realname (G)\fP"
5872 This boolean parameter when set causes samba to supply the real name
5873 field from the unix password file to the client\&. This is useful for
5874 setting up mail clients and WWW browsers on systems used by more than
5878 \f(CW unix realname = no\fP
5881 \f(CW unix realname = yes\fP
5883 .IP "\fBupdate encrypted (G)\fP"
5885 This boolean parameter allows a user logging on with a plaintext
5886 password to have their encrypted (hashed) password in the smbpasswd
5887 file to be updated automatically as they log on\&. This option allows a
5888 site to migrate from plaintext password authentication (users
5889 authenticate with plaintext password over the wire, and are checked
5890 against a UNIX account database) to encrypted password authentication
5891 (the SMB challenge/response authentication mechanism) without forcing
5892 all users to re-enter their passwords via smbpasswd at the time the
5893 change is made\&. This is a convenience option to allow the change over
5894 to encrypted passwords to be made over a longer period\&. Once all users
5895 have encrypted representations of their passwords in the smbpasswd
5896 file this parameter should be set to \f(CW"off"\fP\&.
5898 In order for this parameter to work correctly the \fB"encrypt
5899 passwords"\fP parameter must be set to \f(CW"no"\fP when
5900 this parameter is set to \f(CW"yes"\fP\&.
5902 Note that even when this parameter is set a user authenticating to
5903 smbd must still enter a valid password in order to connect correctly,
5904 and to update their hashed (smbpasswd) passwords\&.
5907 \f(CW update encrypted = no\fP
5910 \f(CW update encrypted = yes\fP
5912 .IP "\fBuse rhosts (G)\fP"
5914 If this global parameter is a true, it specifies that the UNIX users
5915 \f(CW"\&.rhosts"\fP file in their home directory will be read to find the
5916 names of hosts and users who will be allowed access without specifying
5919 NOTE: The use of \fBuse rhosts\fP can be a major security hole\&. This is
5920 because you are trusting the PC to supply the correct username\&. It is
5921 very easy to get a PC to supply a false username\&. I recommend that the
5922 \fBuse rhosts\fP option be only used if you really know what you are
5926 \f(CW use rhosts = no\fP
5929 \f(CW use rhosts = yes\fP
5931 .IP "\fBuser (S)\fP"
5933 Synonym for \fB"username"\fP\&.
5935 .IP "\fBusers (S)\fP"
5937 Synonym for \fB"username"\fP\&.
5939 .IP "\fBusername (S)\fP"
5941 Multiple users may be specified in a comma-delimited list, in which
5942 case the supplied password will be tested against each username in
5943 turn (left to right)\&.
5945 The \fBusername=\fP line is needed only when the PC is unable to supply
5946 its own username\&. This is the case for the COREPLUS protocol or where
5947 your users have different WfWg usernames to UNIX usernames\&. In both
5948 these cases you may also be better using the \f(CW\e\eserver\eshare%user\fP
5951 The \fBusername=\fP line is not a great solution in many cases as it
5952 means Samba will try to validate the supplied password against each of
5953 the usernames in the username= line in turn\&. This is slow and a bad
5954 idea for lots of users in case of duplicate passwords\&. You may get
5955 timeouts or security breaches using this parameter unwisely\&.
5957 Samba relies on the underlying UNIX security\&. This parameter does not
5958 restrict who can login, it just offers hints to the Samba server as to
5959 what usernames might correspond to the supplied password\&. Users can
5960 login as whoever they please and they will be able to do no more
5961 damage than if they started a telnet session\&. The daemon runs as the
5962 user that they log in as, so they cannot do anything that user cannot
5965 To restrict a service to a particular set of users you can use the
5966 \fB"valid users="\fP parameter\&.
5968 If any of the usernames begin with a \f(CW\'@\'\fP then the name will be
5969 looked up first in the yp netgroups list (if Samba is compiled with
5970 netgroup support), followed by a lookup in the UNIX groups database
5971 and will expand to a list of all users in the group of that name\&.
5973 If any of the usernames begin with a \f(CW\'+\'\fP then the name will be
5974 looked up only in the UNIX groups database and will expand to a list
5975 of all users in the group of that name\&.
5977 If any of the usernames begin with a \f(CW\'&\'\fP then the name will be
5978 looked up only in the yp netgroups database (if Samba is compiled with
5979 netgroup support) and will expand to a list of all users in the
5980 netgroup group of that name\&.
5982 Note that searching though a groups database can take quite some time,
5983 and some clients may time out during the search\&.
5985 See the section \fB"NOTE ABOUT USERNAME/PASSWORD
5986 VALIDATION"\fP for more
5987 information on how this parameter determines access to the services\&.
5990 \f(CW The guest account if a guest service, else the name of the service\&.\fP
5998 username = fred, mary, jack, jane, @users, @pcgroup
6004 .IP "\fBusername level (G)\fP"
6006 This option helps Samba to try and \'guess\' at the real UNIX username,
6007 as many DOS clients send an all-uppercase username\&. By default Samba
6008 tries all lowercase, followed by the username with the first letter
6009 capitalized, and fails if the username is not found on the UNIX
6012 If this parameter is set to non-zero the behavior changes\&. This
6013 parameter is a number that specifies the number of uppercase
6014 combinations to try whilst trying to determine the UNIX user name\&. The
6015 higher the number the more combinations will be tried, but the slower
6016 the discovery of usernames will be\&. Use this parameter when you have
6017 strange usernames on your UNIX machine, such as \f(CW"AstrangeUser"\fP\&.
6020 \f(CW username level = 0\fP
6023 \f(CW username level = 5\fP
6025 .IP "\fBusername map (G)\fP"
6027 This option allows you to specify a file containing a mapping of
6028 usernames from the clients to the server\&. This can be used for several
6029 purposes\&. The most common is to map usernames that users use on DOS or
6030 Windows machines to those that the UNIX box uses\&. The other is to map
6031 multiple users to a single username so that they can more easily share
6034 The use of this option, therefore, relates to UNIX usernames
6035 and not Windows (specifically NT Domain) usernames\&. In other words,
6036 once a name has been mapped using this option, the Samba server uses
6037 the mapped name for internal \fIAND\fP external purposes\&.
6039 This option is \fIDIFFERENT\fP from the \fB"domain user map"\fP
6040 parameter, which maintains a one-to-one mapping between UNIX usernames
6041 and NT Domain Usernames: more specifically, the Samba server maintains
6042 a link between \fIBOTH\fP usernames, presenting the NT username to the
6043 external NT world, and using the UNIX username internally\&.
6045 The map file is parsed line by line\&. Each line should contain a single
6046 UNIX username on the left then a \f(CW\'=\'\fP followed by a list of
6047 usernames on the right\&. The list of usernames on the right may contain
6048 names of the form @group in which case they will match any UNIX
6049 username in that group\&. The special client name \f(CW\'*\'\fP is a wildcard
6050 and matches any name\&. Each line of the map file may be up to 1023
6053 The file is processed on each line by taking the supplied username and
6054 comparing it with each username on the right hand side of the \f(CW\'=\'\fP
6055 signs\&. If the supplied name matches any of the names on the right hand
6056 side then it is replaced with the name on the left\&. Processing then
6057 continues with the next line\&.
6059 If any line begins with a \f(CW\'#\'\fP or a \f(CW\';\'\fP then it is ignored
6061 If any line begins with an \f(CW\'!\'\fP then the processing will stop after
6062 that line if a mapping was done by the line\&. Otherwise mapping
6063 continues with every line being processed\&. Using \f(CW\'!\'\fP is most
6064 useful when you have a wildcard mapping line later in the file\&.
6066 For example to map from the name \f(CW"admin"\fP or \f(CW"administrator"\fP to
6067 the UNIX name \f(CW"root"\fP you would use:
6069 \f(CW root = admin administrator\fP
6071 Or to map anyone in the UNIX group \f(CW"system"\fP to the UNIX name
6072 \f(CW"sys"\fP you would use:
6074 \f(CW sys = @system\fP
6076 You can have as many mappings as you like in a username map file\&.
6078 If your system supports the NIS NETGROUP option then the netgroup
6079 database is checked before the \f(CW/etc/group\fP database for matching
6082 You can map Windows usernames that have spaces in them by using double
6083 quotes around the name\&. For example:
6085 \f(CW tridge = "Andrew Tridgell"\fP
6087 would map the windows username \f(CW"Andrew Tridgell"\fP to the unix
6090 The following example would map mary and fred to the unix user sys,
6091 and map the rest to guest\&. Note the use of the \f(CW\'!\'\fP to tell Samba
6092 to stop processing if it gets a match on that line\&.
6105 Note that the remapping is applied to all occurrences of
6106 usernames\&. Thus if you connect to \f(CW"\e\eserver\efred"\fP and \f(CW"fred"\fP
6107 is remapped to \f(CW"mary"\fP then you will actually be connecting to
6108 \f(CW"\e\eserver\emary"\fP and will need to supply a password suitable for
6109 \f(CW"mary"\fP not \f(CW"fred"\fP\&. The only exception to this is the username
6110 passed to the \fB"password server"\fP (if you have
6111 one)\&. The password server will receive whatever username the client
6112 supplies without modification\&.
6114 Also note that no reverse mapping is done\&. The main effect this has is
6115 with printing\&. Users who have been mapped may have trouble deleting
6116 print jobs as PrintManager under WfWg will think they don\'t own the
6120 \f(CW no username map\fP
6123 \f(CW username map = /usr/local/samba/lib/users\&.map\fP
6125 .IP "\fBvalid chars (S)\fP"
6127 The option allows you to specify additional characters that should be
6128 considered valid by the server in filenames\&. This is particularly
6129 useful for national character sets, such as adding u-umlaut or a-ring\&.
6131 The option takes a list of characters in either integer or character
6132 form with spaces between them\&. If you give two characters with a colon
6133 between them then it will be taken as an lowercase:uppercase pair\&.
6135 If you have an editor capable of entering the characters into the
6136 config file then it is probably easiest to use this method\&. Otherwise
6137 you can specify the characters in octal, decimal or hexadecimal form
6138 using the usual C notation\&.
6140 For example to add the single character \f(CW\'Z\'\fP to the charset (which
6141 is a pointless thing to do as it\'s already there) you could do one of
6150 valid chars = 0132:0172
6156 The last two examples above actually add two characters, and alter the
6157 uppercase and lowercase mappings appropriately\&.
6159 Note that you MUST specify this parameter after the \fB"client
6160 code page"\fP parameter if you have both set\&. If
6161 \fB"client code page"\fP is set after the
6162 \fB"valid chars"\fP parameter the \fB"valid chars"\fP settings will be
6165 See also the \fB"client code page"\fP parameter\&.
6172 Samba defaults to using a reasonable set of valid characters
6180 \f(CW valid chars = 0345:0305 0366:0326 0344:0304\fP
6182 The above example allows filenames to have the Swedish characters in
6185 NOTE: It is actually quite difficult to correctly produce a \fB"valid
6186 chars"\fP line for a particular system\&. To automate the process
6187 \fItino@augsburg\&.net\fP has written a package called \fB"validchars"\fP
6188 which will automatically produce a complete \fB"valid chars"\fP line for
6189 a given client system\&. Look in the examples/validchars/ subdirectory
6190 of your Samba source code distribution for this package\&.
6192 .IP "\fBvalid users (S)\fP"
6194 This is a list of users that should be allowed to login to this
6195 service\&. Names starting with \f(CW\'@\'\fP, \f(CW\'+\'\fP and \f(CW\'&\'\fP are
6196 interpreted using the same rules as described in the \fB"invalid
6197 users"\fP parameter\&.
6199 If this is empty (the default) then any user can login\&. If a username
6200 is in both this list and the \fB"invalid users"\fP
6201 list then access is denied for that user\&.
6203 The current servicename is substituted for
6204 \fB"%S"\fP\&. This is useful in the
6205 \fB[homes]\fP section\&.
6207 See also \fB"invalid users"\fP\&.
6210 \f(CW No valid users list\&. (anyone can login)\fP
6213 \f(CW valid users = greg, @pcusers\fP
6215 .IP "\fBveto files(S)\fP"
6217 This is a list of files and directories that are neither visible nor
6218 accessible\&. Each entry in the list must be separated by a \f(CW\'/\'\fP,
6219 which allows spaces to be included in the entry\&. \f(CW\'*\'\fP and \f(CW\'?\'\fP
6220 can be used to specify multiple files or directories as in DOS
6223 Each entry must be a unix path, not a DOS path and must \fI*not*\fP include the
6224 unix directory separator \f(CW\'/\'\fP\&.
6226 Note that the \fB"case sensitive"\fP option is
6227 applicable in vetoing files\&.
6229 One feature of the veto files parameter that it is important to be
6230 aware of, is that if a directory contains nothing but files that match
6231 the veto files parameter (which means that Windows/DOS clients cannot
6232 ever see them) is deleted, the veto files within that directory *are
6233 automatically deleted* along with it, if the user has UNIX permissions
6236 Setting this parameter will affect the performance of Samba, as it
6237 will be forced to check all files and directories for a match as they
6240 See also \fB"hide files"\fP and \fB"case
6244 \f(CW No files or directories are vetoed\&.\fP
6255 Veto any files containing the word Security,
6256 any ending in \&.tmp, and any directory containing the
6259 veto files = /*Security*/*\&.tmp/*root*/
6271 Veto the Apple specific files that a NetAtalk server
6274 veto files = /\&.AppleDouble/\&.bin/\&.AppleDesktop/Network Trash Folder/
6280 .IP "\fBveto oplock files (S)\fP"
6282 This parameter is only valid when the \fB"oplocks"\fP
6283 parameter is turned on for a share\&. It allows the Samba administrator
6284 to selectively turn off the granting of oplocks on selected files that
6285 match a wildcarded list, similar to the wildcarded list used in the
6286 \fB"veto files"\fP parameter\&.
6289 \f(CW No files are vetoed for oplock grants\&.\fP
6293 You might want to do this on files that you know will be heavily
6294 contended for by clients\&. A good example of this is in the NetBench
6295 SMB benchmark program, which causes heavy client contention for files
6296 ending in \f(CW"\&.SEM"\fP\&. To cause Samba not to grant oplocks on these
6297 files you would use the line (either in the \fB[global]\fP
6298 section or in the section for the particular NetBench share :
6300 \f(CW veto oplock files = /*\&.SEM/\fP
6302 .IP "\fBvolume (S)\fP"
6304 This allows you to override the volume label returned for a
6305 share\&. Useful for CDROMs with installation programs that insist on a
6306 particular volume label\&.
6308 The default is the name of the share\&.
6310 .IP "\fBwide links (S)\fP"
6312 This parameter controls whether or not links in the UNIX file system
6313 may be followed by the server\&. Links that point to areas within the
6314 directory tree exported by the server are always allowed; this
6315 parameter controls access only to areas that are outside the directory
6316 tree being exported\&.
6319 \f(CW wide links = yes\fP
6322 \f(CW wide links = no\fP
6324 .IP "\fBwins proxy (G)\fP"
6326 This is a boolean that controls if \fBnmbd\fP will
6327 respond to broadcast name queries on behalf of other hosts\&. You may
6328 need to set this to \f(CW"yes"\fP for some older clients\&.
6331 \f(CW wins proxy = no\fP
6333 .IP "\fBwins server (G)\fP"
6335 This specifies the IP address (or DNS name: IP address for preference)
6336 of the WINS server that \fBnmbd\fP should register with\&.
6337 If you have a WINS server on your network then you should set this to
6338 the WINS server\'s IP\&.
6340 You should point this at your WINS server if you have a
6341 multi-subnetted network\&.
6343 \fINOTE\fP\&. You need to set up Samba to point to a WINS server if you
6344 have multiple subnets and wish cross-subnet browsing to work correctly\&.
6346 See the documentation file BROWSING\&.txt in the docs/ directory of your
6347 Samba source distribution\&.
6350 \f(CW wins server = \fP
6353 \f(CW wins server = 192\&.9\&.200\&.1\fP
6355 .IP "\fBwins support (G)\fP"
6357 This boolean controls if the \fBnmbd\fP process in
6358 Samba will act as a WINS server\&. You should not set this to true
6359 unless you have a multi-subnetted network and you wish a particular
6360 \fBnmbd\fP to be your WINS server\&. Note that you
6361 should \fI*NEVER*\fP set this to true on more than one machine in your
6365 \f(CW wins support = no\fP
6367 .IP "\fBworkgroup (G)\fP"
6369 This controls what workgroup your server will appear to be in when
6370 queried by clients\&. Note that this parameter also controls the Domain
6371 name used with the \fB"security=domain"\fP
6375 \f(CW set at compile time to WORKGROUP\fP
6380 .IP "\fBwritable (S)\fP"
6382 Synonym for \fB"writeable"\fP for people who can\'t spell :-)\&.
6383 Pronounced "ritter-bull"\&.
6385 .IP "\fBwrite list (S)\fP"
6387 This is a list of users that are given read-write access to a
6388 service\&. If the connecting user is in this list then they will be
6389 given write access, no matter what the \fB"read only"\fP
6390 option is set to\&. The list can include group names using the @group
6393 Note that if a user is in both the read list and the write list then
6394 they will be given write access\&.
6396 See also the \fB"read list"\fP option\&.
6399 \f(CW write list = <empty string>\fP
6402 \f(CW write list = admin, root, @staff\fP
6404 .IP "\fBwrite ok (S)\fP"
6406 Synonym for \fBwriteable\fP\&.
6408 .IP "\fBwrite raw (G)\fP"
6410 This parameter controls whether or not the server will support raw
6411 writes SMB\'s when transferring data from clients\&. You should never
6412 need to change this parameter\&.
6415 \f(CW write raw = yes\fP
6417 .IP "\fBwriteable\fP"
6419 An inverted synonym is \fB"read only"\fP\&.
6421 If this parameter is \f(CW"no"\fP, then users of a service may not create
6422 or modify files in the service\'s directory\&.
6424 Note that a printable service \fB("printable = yes")\fP
6425 will \fI*ALWAYS*\fP allow writing to the directory (user privileges
6426 permitting), but only via spooling operations\&.
6429 \f(CW writeable = no\fP
6446 Although the configuration file permits service names to contain
6447 spaces, your client software may not\&. Spaces will be ignored in
6448 comparisons anyway, so it shouldn\'t be a problem - but be aware of the
6451 On a similar note, many clients - especially DOS clients - limit
6452 service names to eight characters\&. \fBSmbd\fP has no
6453 such limitation, but attempts to connect from such clients will fail
6454 if they truncate the service names\&. For this reason you should
6455 probably keep your service names down to eight characters in length\&.
6457 Use of the \fB[homes]\fP and \fB[printers]\fP
6458 special sections make life for an administrator easy, but the various
6459 combinations of default attributes can be tricky\&. Take extreme care
6460 when designing these sections\&. In particular, ensure that the
6461 permissions on spool directories are correct\&.
6465 This man page is correct for version 2\&.0 of the Samba suite\&.
6469 \fBsmbd (8)\fP, \fBsmbclient (1)\fP,
6470 \fBnmbd (8)\fP, \fBtestparm (1)\fP,
6471 \fBtestprns (1)\fP, \fBSamba\fP,
6472 \fBnmblookup (1)\fP, \fBsmbpasswd (5)\fP,
6473 \fBsmbpasswd (8)\fP\&.
6477 The original Samba software and related utilities were created by
6478 Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
6479 by the Samba Team as an Open Source project similar to the way the
6480 Linux kernel is developed\&.
6482 The original Samba man pages were written by Karl Auer\&. The man page
6483 sources were converted to YODL format (another excellent piece of Open
6484 Source software, available at
6485 \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
6486 and updated for the Samba2\&.0 release by Jeremy Allison\&.
6487 \fIsamba-bugs@samba\&.org\fP\&.
6489 See \fBsamba (7)\fP to find out how to get a full
6490 list of contributors and details on how to submit bug reports,
git.samba.org / ira / wip.git / blob