1 .TH SMB.CONF 5 smb.conf smb.conf
3 smb.conf \- configuration file for smbd
9 file is a configuration file for the Samba suite.
12 contains runtime configuration information for the
16 program provides LanManager-like services to clients
17 using the SMB protocol.
19 The file consists of sections and parameters. A section begins with the
20 name of the section in square brackets and continues until the next
21 section begins. Sections contain parameters of the form 'name = value'.
23 The file is line-based - that is, each newline-terminated line represents
24 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 before
29 or after the first equals sign is discarded. Leading, trailing and internal
30 whitespace in section and parameter names is irrelevant. Leading and
31 trailing whitespace in a parameter value is discarded. Internal whitespace
32 within a parameter value is retained verbatim.
34 Any line beginning with a semicolon is ignored, as are lines containing
37 Any line ending in a \e is "continued" on the next line in the
38 customary UNIX fashion.
40 The values following the equals sign in parameters are all either a string
41 (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or
42 true/false. Case is not significant in boolean values, but is preserved
43 in string values. Some items such as create modes are numeric.
44 .SH SERVICE DESCRIPTIONS
45 Each section in the configuration file describes a service. The section name
46 is the service name and the parameters within the section define the service's
49 There are three special sections, [global], [homes] and [printers], which are
50 described under 'special sections'. The following notes apply to ordinary
53 A service consists of a directory to which access is being given plus a
54 description of the access rights which are granted to the user of the
55 service. Some housekeeping options are also specifiable.
57 Services are either filespace services (used by the client as an extension of
58 their native file systems) or printable services (used by the client to access
59 print services on the host running the server).
61 Services may be guest services, in which case no password is required to
62 access them. A specified guest account is used to define access privileges
65 Services other than guest services will require a password to access
66 them. The client provides the username. As many clients only provide
67 passwords and not usernames, you may specify a list of usernames to
68 check against the password using the "user=" option in the service
71 Note that the access rights granted by the server are masked by the access
72 rights granted to the specified or guest user by the host system. The
73 server does not grant more access than the host system grants.
75 The following sample section defines a file space service. The user has write
76 access to the path /home/bar. The service is accessed via the service name
83 The following sample section defines a printable service. The service is
84 readonly, but printable. That is, the only write access permitted is via
85 calls to open, write to and close a spool file. The 'guest ok' parameter
86 means access will be permitted as the default guest user (specified elsewhere):
89 path = /usr/spool/public
95 .SS The [global] section
97 Parameters in this section apply to the server as a whole, or are defaults
98 for services which do not specifically define certain items. See the notes
99 under 'Parameters' for more information.
102 .SS The [homes] section
104 If a section called 'homes' is included in the configuration file, services
105 connecting clients to their home directories can be created on the fly by the
108 When the connection request is made, the existing services are scanned. If a
109 match is found, it is used. If no match is found, the requested service name is
110 treated as a user name and looked up in the local passwords file. If the
111 name exists and the correct password has been given, a service is created
112 by cloning the [homes] section.
114 Some modifications are then made to the newly created section:
117 The service name is changed from 'homes' to the located username
119 If no path was given, the path is set to the user's home directory.
122 If you decide to use a path= line in your [homes] section then you may
123 find it useful to use the %S macro. For example path=/data/pchome/%S
124 would be useful if you have different home directories for your PCs
125 than for UNIX access.
127 This is a fast and simple way to give a large number of clients access to
128 their home directories with a minimum of fuss.
130 A similar process occurs if the requested service name is "homes", except that
131 the service name is not changed to that of the requesting user. This method
132 of using the [homes] section works well if different users share a client PC.
134 The [homes] section can specify all the parameters a normal service section
135 can specify, though some make more sense than others. The following is a
136 typical and suitable [homes] section:
144 If guest access is specified in the [homes] section, all home directories will
145 be accessible to all clients
146 .B without a password.
147 In the very unlikely event
148 that this is actually desirable, it would be wise to also specify read only
153 Note that the browseable flag for auto home directories will be
154 inherited from the global browseable flag, not the [homes] browseable
155 flag. This is useful as it means setting browseable=no in the [homes]
156 section will hide the [homes] service but make any auto home
159 .SS The [printers] section
161 This section works like [homes], but for printers.
163 If a [printers] section occurs in the configuration file, users are able
164 to connect to any printer specified in the local host's printcap file.
166 When a connection request is made, the existing services are scanned. If a
167 match is found, it is used. If no match is found, but a [homes] section
168 exists, it is used as described above. Otherwise, the requested service name is
169 treated as a printer name and the appropriate printcap file is scanned to
170 see if the requested service name is a valid printer name. If a match is
171 found, a new service is created by cloning the [printers] section.
173 A few modifications are then made to the newly created section:
176 The service name is set to the located printer name
178 If no printer name was given, the printer name is set to the located printer
181 If the service does not permit guest access and no username was given, the
182 username is set to the located printer name.
185 Note that the [printers] service MUST be printable - if you specify otherwise,
186 the server will refuse to load the configuration file.
188 Typically the path specified would be that of a world-writable spool directory
189 with the sticky bit set on it. A typical [printers] entry would look like this:
192 path = /usr/spool/public
197 All aliases given for a printer in the printcap file are legitimate printer
198 names as far as the server is concerned. If your printing subsystem doesn't
199 work like that, you will have to set up a pseudo-printcap. This is a file
200 consisting of one or more lines like this:
202 alias|alias|alias|alias...
204 Each alias should be an acceptable printer name for your printing
205 subsystem. In the [global] section, specify the new file as your printcap.
206 The server will then only recognise names found in your pseudo-printcap,
207 which of course can contain whatever aliases you like. The same technique
208 could be used simply to limit access to a subset of your local printers.
210 An alias, by the way, is defined as any component of the first entry of a
211 printcap record. Records are separated by newlines, components (if there are
212 more than one) are separated by vertical bar symbols ("|").
215 Parameters define the specific attributes of services.
217 Some parameters are specific to the [global] section (eg., security).
218 Some parameters are usable in all sections (eg., create mode). All others are
219 permissible only in normal sections. For the purposes of the following
220 descriptions the [homes] and [printers] sections will be considered normal.
221 The letter 'G' in parentheses indicates that a parameter is specific to the
222 [global] section. The letter 'S' indicates that a parameter can be
223 specified in a service specific section. Note that all S parameters
224 can also be specified in the [global] section - in which case they
225 will define the default behaviour for all services.
227 Parameters are arranged here in alphabetical order - this may not create
228 best bedfellows, but at least you can find them! Where there are synonyms,
229 the preferred synonym is described, others refer to the preferred synonym.
231 .SS VARIABLE SUBSTITUTIONS
233 Many of the strings that are settable in the config file can take
234 substitutions. For example the option "path = /tmp/%u" would be
235 interpreted as "path = /tmp/john" if the user connected with the
238 These substitutions are mostly noted in the descriptions below, but
239 there are some general substitutions which apply whenever they might be
242 %S = the name of the current service, if any
244 %P = the root directory of the current service, if any
246 %u = user name of the current service, if any
248 %g = primary group name of %u
250 %U = session user name (the user name that the client wanted, not
251 necessarily the same as the one they got)
253 %G = primary group name of %U
255 %H = the home directory of the user given by %u
257 %v = the Samba version
259 %h = the hostname that Samba is running on
261 %m = the netbios name of the client machine (very useful)
263 %L = the netbios name of the server. This allows you to change your
264 config based on what the client calls you. Your server can have a "dual
267 %M = the internet name of the client machine
269 %d = The process id of the current server process
271 %a = the architecture of the remote machine. Only some are recognised,
272 and those may not be 100% reliable. It currently recognises Samba,
273 WfWg, WinNT and Win95. Anything else will be known as "UNKNOWN". If it
274 gets it wrong then sending me a level 3 log should allow me to fix it.
276 %I = The IP address of the client machine
278 %T = the current date and time
280 There are some quite creative things that can be done with these
281 substitutions and other smb.conf options.
285 Samba supports "name mangling" so that DOS and Windows clients can use
286 files that don't conform to the 8.3 format. It can also be set to adjust
287 the case of 8.3 format filenames.
289 There are several options that control the way mangling is performed,
290 and they are grouped here rather than listed separately. For the
291 defaults look at the output of the testparm program.
293 All of these options can be set separately for each service (or
294 globally, of course).
298 "mangle case = yes/no" controls if names that have characters that
299 aren't of the "default" case are mangled. For example, if this is yes
300 then a name like "Mail" would be mangled. Default no.
302 "case sensitive = yes/no" controls whether filenames are case
303 sensitive. If they aren't then Samba must do a filename search and
304 match on passed names. Default no.
306 "default case = upper/lower" controls what the default case is for new
307 filenames. Default lower.
309 "preserve case = yes/no" controls if new files are created with the
310 case that the client passes, or if they are forced to be the "default"
313 "short preserve case = yes/no" controls if new files which conform to 8.3
314 syntax, that is all in upper case and of suitable length, are created
315 upper case, or if they are forced to be the "default" case. This option can
316 be use with "preserve case = yes" to permit long filenames to retain their
317 case, while short names are lowered. Default no.
319 .SS COMPLETE LIST OF GLOBAL PARAMETERS
321 Here is a list of all global parameters. See the section of each
322 parameter for details. Note that some are synonyms.
474 .SS COMPLETE LIST OF SERVICE PARAMETERS
476 Here is a list of all service parameters. See the section of each
477 parameter for details. Note that some are synonyms.
483 alternate permissions
633 .SS EXPLANATION OF EACH PARAMETER
638 This is a list of users who will be granted administrative privileges
639 on the share. This means that they will do all file operations as the
642 You should use this option very carefully, as any user in this list
643 will be able to do anything they like on the share, irrespective of
652 .SS auto services (G)
653 This is a list of services that you want to be automatically added to
654 the browse lists. This is most useful for homes and printers services
655 that would otherwise not be visible.
657 Note that if you just want all printers in your printcap file loaded
658 then the "load printers" option is easier.
664 auto services = fred lp colorlp
667 A synonym for this parameter is 'hosts allow'.
669 This parameter is a comma delimited set of hosts which are permitted to access
670 a services. If specified in the [global] section, matching hosts will be
671 allowed access to any service that does not specifically exclude them from
672 access. Specific services my have their own list, which override those
673 specified in the [global] section.
675 You can specify the hosts by name or IP number. For example, you could
676 restrict access to only the hosts on a Class C subnet with something like
677 "allow hosts = 150.203.5.". The full syntax of the list is described in
679 .BR hosts_access (5).
681 You can also specify hosts by network/netmask pairs and by netgroup
682 names if your system supports netgroups. The EXCEPT keyword can also
683 be used to limit a wildcard list. The following examples may provide
686 Example 1: allow all IPs in 150.203.*.* except one
688 hosts allow = 150.203. EXCEPT 150.203.6.66
690 Example 2: allow hosts that match the given network/netmask
692 hosts allow = 150.203.15.0/255.255.255.0
694 Example 3: allow a couple of hosts
696 hosts allow = lapland, arvidsjaur
698 Example 4: allow only hosts in netgroup "foonet" or localhost, but
699 deny access from one particular host
701 hosts allow = @foonet, localhost
704 Note that access still requires suitable user-level passwords.
708 for a way of testing your host access to see if it
709 does what you expect.
712 none (i.e., all hosts permitted access)
715 allow hosts = 150.203.5. myhost.mynet.edu.au
717 .SS alternate permissions (S)
719 This option affects the way the "read only" DOS attribute is produced
720 for UNIX files. If this is false then the read only bit is set for
721 files on writeable shares which the user cannot write to.
723 If this is true then it is set for files whos user write bit is not set.
725 The latter behaviour is useful for when users copy files from each
726 others directories, and use a file manager that preserves
727 permissions. Without this option they may get annoyed as all copied
728 files will have the "read only" bit set.
731 alternate permissions = no
734 alternate permissions = yes
737 This parameter lets you 'turn off' a service. If 'available = no', then
738 ALL attempts to connect to the service will fail. Such failures are logged.
746 This controls whether this share is seen in the list of available
747 shares in a net view and in the browse list.
755 This controls whether the smbd will serve a browse list to a client
756 doing a NetServerEnum call. Normally set to true. You should never
762 .SS case sensitive (G)
763 See the discussion on NAME MANGLING.
765 .SS case sig names (G)
768 .SS character set (G)
769 This allows a smbd to map incoming characters from a DOS 850 Code page
770 to either a Western European (ISO8859-1) or Easter European (ISO8859-2)
771 code page. Normally not set, meaning no filename translation is done.
779 character set = iso8859-1
782 This is a text field that is seen when a client does a net view to
783 list what shares are available. It will also be used when browsing is
790 comment = Fred's Files
794 This allows you to override the config file to use, instead of the
795 default (usually smb.conf). There is a chicken and egg problem here as
796 this option is set in the config file!
798 For this reason, if the name of the config file has changed when the
799 parameters are loaded then it will reload them from the new config
802 This option takes the usual substitutions, which can be very useful.
804 If the config file doesn't exist then it won't be loaded (allowing
805 you to special case the config files of just a few clients).
808 config file = /usr/local/samba/lib/smb.conf.%m
811 This parameter allows you to 'clone' service entries. The specified
812 service is simply duplicated under the current service's name. Any
813 parameters specified in the current section will override those in the
814 section being copied.
816 This feature lets you set up a 'template' service and create similar
817 services easily. Note that the service being copied must occur earlier
818 in the configuration file than the service doing the copying.
826 A synonym for this parameter is 'create mode'.
828 This parameter is the octal modes which are used when converting DOS modes
831 Note that Samba will or this value with 0700 as you must have at least
832 user read, write and execute for Samba to work properly.
843 The value of the parameter (a decimal integer) represents the number of
844 minutes of inactivity before a connection is considered dead, and it
845 is disconnected. The deadtime only takes effect if the number of open files
848 This is useful to stop a server's resources being exhausted by a large
849 number of inactive connections.
851 Most clients have an auto-reconnect feature when a connection is broken so
852 in most cases this parameter should be transparent to users.
854 Using this parameter with a timeout of a few minutes is recommended
857 A deadtime of zero indicates that no auto-disconnection should be performed.
865 The value of the parameter (an integer) allows the debug level
866 (logging level) to be specified in the
868 file. This is to give
869 greater flexibility in the configuration of the system.
871 The default will be the debug level specified on the command line.
880 See the section on "NAME MANGLING" Also note the addition of "short
883 .SS default service (G)
884 A synonym for this parameter is 'default'.
886 This parameter specifies the name of a service which will be connected to
887 if the service actually requested cannot be found. Note that the square
888 brackets are NOT given in the parameter value (see example below).
890 There is no default value for this parameter. If this parameter is not given,
891 attempting to connect to a nonexistent service results in an error.
893 Typically the default service would be a public, read-only service.
895 Also note that as of 1.9.14 the apparent service name will be changed to
896 equal that of the requested service, this is very useful as it allows
897 you to use macros like %S to make a wildcard service.
899 Note also that any _ characters in the name of the service used in the
900 default service will get mapped to a /. This allows for interesting
905 default service = pub
911 .SS delete readonly (S)
912 This parameter allows readonly files to be deleted. This is not normal DOS
913 semantics, but is allowed by UNIX.
915 This option may be useful for running applications such as rcs, where UNIX
916 file ownership prevents changing file permissions, and DOS semantics prevent
917 deletion of a read only file.
923 delete readonly = Yes
925 A synonym for this parameter is 'hosts deny'.
927 The opposite of 'allow hosts' - hosts listed here are NOT permitted
928 access to services unless the specific services have their own lists to
929 override this one. Where the lists conflict, the 'allow' list takes precedence.
932 none (i.e., no hosts specifically excluded)
935 deny hosts = 150.203.4. badhost.mynet.edu.au
936 .SS dfree command (G)
937 The dfree command setting should only be used on systems where a
938 problem occurs with the internal disk space calculations. This has
939 been known to happen with Ultrix, but may occur with other operating
940 systems. The symptom that was seen was an error of "Abort Retry
941 Ignore" at the end of each directory listing.
943 This setting allows the replacement of the internal routines to
944 calculate the total disk space and amount available with an external
945 routine. The example below gives a possible script that might fulfill
948 The external program will be passed a single parameter indicating a
949 directory in the filesystem being queried. This will typically consist
950 of the string "./". The script should return two integers in ascii. The
951 first should be the total disk space in blocks, and the second should
952 be the number of available blocks. An optional third return value
953 can give the block size in bytes. The default blocksize is 1024 bytes.
955 Note: Your script should NOT be setuid or setgid and should be owned by
956 (and writable only by) root!
959 By default internal routines for determining the disk capacity
960 and remaining space will be used.
963 dfree command = /usr/local/samba/bin/dfree
965 Where the script dfree (which must be made executable) could be
969 df $1 | tail -1 | awk '{print $2" "$4}'
972 or perhaps (on Sys V)
976 /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
979 Note that you may have to replace the command names with full
980 path names on some systems.
985 .SS directory mask (S)
986 A synonym for this parameter is 'directory mode'.
988 This parameter is the octal modes which are used when converting DOS modes
989 to UNIX modes when creating UNIX directories.
991 Note that Samba will bit-wise 'OR' this value with 0700 as you must have at
992 least user read, write and execute for Samba to work properly.
995 directory mask = 0755
998 directory mask = 0775
999 .SS directory mode (S)
1002 .SS domain controller (G)
1004 Specifies the DNS name or IP address of the machine to refer domain
1005 logons from Win95 machines to. You should never need to set this parameter.
1010 .SS domain master (G)
1012 Enable WAN-wide browse list collation. Local master browsers on
1013 broadcast-isolated subnets will give samba their local browse lists, and
1014 ask for a complete copy of the browse list for the whole wide area network.
1015 Browser clients will then contact their local master browser, and will
1016 receive the domain-wide browse list, instead of just the list for their
1017 broadcast-isolated subnet.
1022 .SS dont descend (S)
1023 There are certain directories on some systems (eg., the /proc tree under
1024 Linux) that are either not of interest to clients or are infinitely deep
1025 (recursive). This parameter allows you to specify a comma-delimited list
1026 of directories that the server should always show as empty.
1028 Note that Samba can be very fussy about the exact format of the "dont
1029 descend" entries. For example you may need "./proc" instead of just
1030 "/proc". Experimentation is the best policy :-)
1033 none (i.e., all directories are OK to descend)
1036 dont descend = /proc,/dev
1038 .SS encrypt passwords (G)
1040 This boolean controls whether encrypted passwords will be negotiated
1041 with the client. Note that this option has no effect if you haven't
1042 compiled in the necessary des libraries and encryption code. It
1047 This is an alias for preexec
1049 .SS fake oplocks (S)
1051 Oplocks are the way that SMB clients get permission from a server to
1052 locally cache file operations. If a server grants an oplock
1053 (opportunistic lock) then the client is free to assume that it is the
1054 only one accessing the file and it will aggressively cache file
1055 data. With some oplock types the client may even cache file open/close
1056 operations. This can give enormous performance benefits.
1058 Samba does not support opportunistic locks because they are very
1059 difficult to do under Unix. Samba can fake them, however, by granting
1060 a oplock whenever a client asks for one. This is controlled using the
1061 smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
1062 you are telling the client that it may aggressively cache the file
1065 By enabling this option on all read-only shares or shares that you know
1066 will only be accessed from one client at a time you will see a big
1067 performance improvement on many operations. If you enable this option
1068 on shares where multiple clients may be accessing the files read-write
1069 at the same time you can get data corruption. Use this option
1072 This option is disabled by default.
1076 This specifies a group name that all connections to this service
1077 should be made as. This may be useful for sharing files.
1083 force group = agroup
1086 This specifies a user name that all connections to this service
1087 should be made as. This may be useful for sharing files. You should
1088 also use it carefully as using it incorrectly can cause security
1091 This user name only gets used once a connection is established. Thus
1092 clients still need to connect as a valid user and supply a valid
1093 password. Once connected, all file operations will be performed as the
1094 "forced user", not matter what username the client connected as.
1103 This is a tuning option. When this is enabled a cacheing algorithm will
1104 be used to reduce the time taken for getwd() calls. This can have a
1105 significant impact on performance, especially when widelinks is False.
1114 This is an alias for "force group" and is only kept for compatibility
1115 with old versions of Samba. It may be removed in future versions.
1117 .SS guest account (S)
1118 This is a username which will be used for access to services which are
1119 specified as 'guest ok' (see below). Whatever privileges this user has
1120 will be available to any client connecting to the guest
1121 service. Typically this user will exist in the password file, but will
1122 not have a valid login. If a username is specified in a given service,
1123 the specified username overrides this one.
1125 One some systems the account "nobody" may not be able to print. Use
1126 another account in this case. You should test this by trying to log in
1127 as your guest user (perhaps by using the "su \-" command) and trying to
1131 Note that as of version 1.9 of Samba this option may be set
1132 differently for each service.
1135 specified at compile time
1138 guest account = nobody
1143 If this parameter is 'yes' for a service, then only guest connections to the
1144 service are permitted. This parameter will have no affect if "guest ok" or
1145 "public" is not set for the service.
1147 See the section below on user/password validation for more information about
1155 .SS hide dot files (S)
1156 This is a boolean parameter that controls whether files starting with
1157 a dot appear as hidden files.
1160 hide dot files = yes
1165 If "nis homedir" is true, this parameter specifies the NIS (or YP) map
1166 from which the server for the user's home directory should be extracted.
1167 At present, only the Sun auto.home map format is understood. The form of
1170 username server:/some/file/system
1172 and the program will extract the servername from before the first ':'.
1173 There should probably be a better parsing system that copes with different
1174 map formats and also Amd (another automounter) maps.
1176 NB: The -DNETGROUP option is required in the Makefile for option to work
1177 and on some architectures the line -lrpcsvc needs to be added to the
1178 LIBSM variable. This is required for Solaris 2, FreeBSD and HPUX.
1180 See also "nis homedir"
1183 homedir map = auto.home
1186 homedir map = amd.homedir
1195 If this global parameter is a non-null string, it specifies the name of
1196 a file to read for the names of hosts and users who will be allowed access
1197 without specifying a password.
1199 This is not be confused with
1201 which is about hosts access to services and is more useful for guest services.
1203 may be useful for NT clients which will not supply passwords to samba.
1205 NOTE: The use of hosts.equiv can be a major security hole. This is
1206 because you are trusting the PC to supply the correct username. It is
1207 very easy to get a PC to supply a false username. I recommend that the
1208 hosts.equiv option be only used if you really know what you are doing,
1209 or perhaps on a home network where you trust your wife and kids :-)
1212 No host equivalences
1215 hosts equiv = /etc/hosts.equiv
1219 This allows you to include one config file inside another. The file is
1220 included literally, as though typed in place.
1222 It takes the standard substitutions, except %u, %P and %S
1226 This option allows you to setup multiple network interfaces, so that
1227 Samba can properly handle browsing on all interfaces.
1229 The option takes a list of ip/netmask pairs. The netmask may either be
1230 a bitmask, or a bitlength.
1232 For example, the following line:
1234 interfaces = 192.168.2.10/24 192.168.3.10/24
1236 would configure two network interfaces with IP addresses 192.168.2.10
1237 and 192.168.3.10. The netmasks of both interfaces would be set to
1240 You could produce an equivalent result by using:
1242 interfaces = 192.168.2.10/255.255.255.0 192.168.3.10/255.255.255.0
1244 if you prefer that format.
1246 If this option is not set then Samba will attempt to find a primary
1247 interface, but won't attempt to configure more than one interface.
1249 .SS invalid users (S)
1250 This is a list of users that should not be allowed to login to this
1251 service. This is really a "paranoid" check to absolutely ensure an
1252 improper setting does not breach your security.
1254 A name starting with @ is interpreted as a UNIX group.
1256 The current servicename is substituted for %S. This is useful in the
1259 See also "valid users"
1265 invalid users = root fred admin @wheel
1268 The value of the parameter (an integer) represents the number of seconds
1269 between 'keepalive' packets. If this parameter is zero, no keepalive packets
1270 will be sent. Keepalive packets, if sent, allow the server to tell whether a
1271 client is still present and responding.
1273 Keepalives should, in general, not be needed if the socket being used
1274 has the SO_KEEPALIVE attribute set on it (see "socket
1275 options"). Basically you should only use this option if you strike
1283 .SS load printers (G)
1284 A boolean variable that controls whether all printers in the printcap
1285 will be loaded for browsing by default.
1293 .SS local master (G)
1294 This option allows the nmbd to become a local master browser on a
1295 subnet. If set to False then nmbd will not attempt to become a local
1296 master browser on a subnet and will also lose in all browsing elections.
1297 By default this value is set to true. Setting this value to true doesn't
1298 mean that Samba will become the local master browser on a subnet, just
1299 that the nmbd will participate in elections for local master browser.
1304 .SS lock directory (G)
1305 This option specifies the directory where lock files will be placed.
1306 The lock files are used to implement the "max connections" option.
1309 lock directory = /tmp/samba
1312 lock directory = /usr/local/samba/var/locks
1314 This controls whether or not locking will be performed by the server in
1315 response to lock requests from the client.
1317 If "locking = no", all lock and unlock requests will appear to succeed and
1318 all lock queries will indicate that the queried lock is clear.
1320 If "locking = yes", real locking will be performed by the server.
1322 This option may be particularly useful for read-only filesystems which
1323 do not need locking (such as cdrom drives).
1325 Be careful about disabling locking either globally or in a specific
1326 service, as lack of locking may result in data corruption.
1336 This options allows you to override the name of the Samba log file
1337 (also known as the debug file).
1339 This option takes the standard substitutions, allowing you to have
1340 separate log files for each user or machine.
1343 log file = /usr/local/samba/var/log.%m
1350 This parameter specifies the home directory where roaming profiles
1351 (USER.DAT / USER.MAN files) are stored.
1353 This option takes the standard substitutions, allowing you to have
1354 separate logon scripts for each user or machine. It also specifies
1355 the directory from which the "desktop", "start menu", "nethood" and
1356 "programs" folders, and their contents, are loaded and displayed
1357 on your Windows 95 client.
1359 The share and the path must be readable by the user for the preferences
1360 and directories to be loaded onto the Windows 95 client. The share
1361 must be writeable when the logs in for the first time, in order that
1362 the Windows 95 client can create the user.dat and other directories.
1364 Thereafter, the directories and any of contents can, if required,
1365 be made read-only. It is not adviseable that the USER.DAT file be made
1366 read-only - rename it to USER.MAN to achieve the desired effect
1367 (a MANdatory profile).
1370 logon path = \\\\%L\\%U
1373 logon path = \\\\PROFILESERVER\\HOME_DIR\\%U
1375 .SS logon script (G)
1377 This parameter specifies the batch file (.bat) or NT command file (.cmd)
1378 to be downloaded and run on a machine when a user successfully logs in.
1379 The file must contain the DOS style cr/lf line endings. Using a DOS-style
1380 editor to create the file is recommended.
1382 The script must be a relative path to the [netlogon] service. If the
1383 [netlogon] service specifies a path of /usr/local/samba/netlogon, and
1384 logon script = STARTUP.BAT, then file that will be downloaded is:
1386 .B /usr/local/samba/netlogon/STARTUP.BAT
1388 The contents of the batch file is entirely your choice. A suggested
1389 command would be to add NET TIME \\\\SERVER /SET /YES, to force every
1390 machine to synchronise clocks with the same time server. Another use
1391 would be to add NET USE U: \\\\SERVER\\UTILS for commonly used utilities,
1392 or NET USE Q: \\\\SERVER\\ISO9001_QA.
1394 Note that it is particularly important not to allow write access to
1395 the [netlogon] share, or to grant users write permission on the
1396 batch files in a secure environment, as this would allow the batch
1397 files to be arbitrarily modified.
1400 This option takes the standard substitutions, allowing you to have
1401 separate logon scripts for each user or machine.
1404 logon script = scripts/%U.bat
1406 .SS lppause command (S)
1407 This parameter specifies the command to be executed on the server host in
1408 order to stop printing or spooling a specific print job.
1410 This command should be a program or script which takes a printer name and
1411 job number to pause the print job. Currently I don't know of any print
1412 spooler system that can do this with a simple option, except for the PPR
1413 system from Trinity College (ppr\-dist.trincoll.edu/pub/ppr). One way
1414 of implementing this is by using job priorities, where jobs having a too
1415 low priority won't be sent to the printer. See also the
1419 If a %p is given then the printername is put in its place. A %j is
1420 replaced with the job number (an integer).
1421 On HPUX (see printing=hpux), if the -p%p option is added to the lpq
1422 command, the job will show up with the correct status, i.e. if the job
1423 priority is lower than the set fence priority it will have the PAUSED
1424 status, whereas if the priority is equal or higher it will have the
1425 SPOOLED or PRINTING status.
1427 Note that it is good practice to include the absolute path in the lppause
1428 command as the PATH may not be available to the server.
1431 Currently no default value is given to this string
1433 .B Example for HPUX:
1434 lppause command = /usr/bin/lpalt %p-%j -p0
1436 .SS lpq cache time (G)
1438 This controls how long lpq info will be cached for to prevent the lpq
1439 command being called too often. A separate cache is kept for each
1440 variation of the lpq command used by the system, so if you use
1441 different lpq commands for different users then they won't share cache
1444 The cache files are stored in /tmp/lpq.xxxx where xxxx is a hash
1445 of the lpq command in use.
1447 The default is 10 seconds, meaning that the cached results of a
1448 previous identical lpq command will be used if the cached data is less
1449 than 10 seconds old. A large value may be advisable if your lpq
1450 command is very slow.
1452 A value of 0 will disable cacheing completely.
1461 This parameter specifies the command to be executed on the server host in
1462 order to obtain "lpq"-style printer status information.
1464 This command should be a program or script which takes a printer name
1465 as its only parameter and outputs printer status information.
1467 Currently six styles of printer status information are supported; BSD,
1468 SYSV, AIX, HPUX, QNX, LPRNG and PLP. This covers most UNIX systems. You
1469 control which type is expected using the "printing =" option.
1471 Some clients (notably Windows for Workgroups) may not correctly send the
1472 connection number for the printer they are requesting status information
1473 about. To get around this, the server reports on the first printer service
1474 connected to by the client. This only happens if the connection number sent
1477 If a %p is given then the printername is put in its place. Otherwise
1478 it is placed at the end of the command.
1480 Note that it is good practice to include the absolute path in the lpq
1481 command as the PATH may not be available to the server.
1484 depends on the setting of "printing ="
1487 lpq command = /usr/bin/lpq %p
1489 .SS lpresume command (S)
1490 This parameter specifies the command to be executed on the server host in
1491 order to restart or continue printing or spooling a specific print job.
1493 This command should be a program or script which takes a printer name and
1494 job number to resume the print job. See also the lppause command.
1496 If a %p is given then the printername is put in its place. A %j is
1497 replaced with the job number (an integer).
1499 Note that it is good practice to include the absolute path in the lpresume
1500 command as the PATH may not be available to the server.
1503 Currently no default value is given to this string
1505 .B Example for HPUX:
1506 lpresume command = /usr/bin/lpalt %p-%j -p2
1508 .SS lprm command (S)
1509 This parameter specifies the command to be executed on the server host in
1510 order to delete a print job.
1512 This command should be a program or script which takes a printer name
1513 and job number, and deletes the print job.
1515 Currently seven styles of printer control are supported; BSD, SYSV, AIX
1516 HPUX, QNX, LPRNG and PLP. This covers most UNIX systems. You control
1517 which type is expected using the "printing =" option.
1519 If a %p is given then the printername is put in its place. A %j is
1520 replaced with the job number (an integer).
1522 Note that it is good practice to include the absolute path in the lprm
1523 command as the PATH may not be available to the server.
1526 depends on the setting of "printing ="
1529 lprm command = /usr/bin/lprm -P%p %j
1532 lprm command = /usr/bin/cancel %p-%j
1534 .SS magic output (S)
1535 This parameter specifies the name of a file which will contain output
1536 created by a magic script (see
1540 Warning: If two clients use the same magic script in the same directory the
1541 output file content is undefined.
1543 magic output = <magic script name>.out
1546 magic output = myfile.txt
1547 .SS magic script (S)
1548 This parameter specifies the name of a file which, if opened, will be
1549 executed by the server when the file is closed. This allows a UNIX script
1550 to be sent to the Samba host and executed on behalf of the connected user.
1552 Scripts executed in this way will be deleted upon completion, permissions
1555 If the script generates output, output will be sent to the file specified by
1558 parameter (see above).
1560 Note that some shells are unable to interpret scripts containing
1561 carriage-return-linefeed instead of linefeed as the end-of-line
1562 marker. Magic scripts must be executable "as is" on the host, which
1563 for some hosts and some shells will require filtering at the DOS end.
1565 Magic scripts are EXPERIMENTAL and should NOT be relied upon.
1568 None. Magic scripts disabled.
1571 magic script = user.csh
1575 See the section on "NAME MANGLING"
1578 This is for those who want to directly map UNIX file names which are
1579 not representable on DOS. The mangling of names is not always what is
1580 needed. In particular you may have documents with file extensions
1581 that differ between DOS and UNIX. For example, under UNIX it is common
1582 to use .html for HTML files, whereas under DOS .htm is more commonly
1585 So to map 'html' to 'htm' you put:
1587 mangled map = (*.html *.htm)
1589 One very useful case is to remove the annoying ;1 off the ends of
1590 filenames on some CDROMS (only visible under some UNIXes). To do this
1591 use a map of (*;1 *)
1597 mangled map = (*;1 *)
1599 .SS mangled names (S)
1600 This controls whether non-DOS names under UNIX should be mapped to
1601 DOS-compatible names ("mangled") and made visible, or whether non-DOS names
1602 should simply be ignored.
1604 See the section on "NAME MANGLING" for details on how to control the
1607 If mangling is used then the mangling algorithm is as follows:
1609 - the first (up to) five alphanumeric characters before the rightmost dot of
1610 the filename are preserved, forced to upper case, and appear as the first (up
1611 to) five characters of the mangled name.
1613 - a tilde ("~") is appended to the first part of the mangled name, followed
1614 by a two-character unique sequence, based on the original root name
1615 (i.e., the original filename minus its final extension). The final
1616 extension is included in the hash calculation only if it contains any upper
1617 case characters or is longer than three characters.
1619 Note that the character to use may be specified using the "mangling
1620 char" option, if you don't like ~.
1622 - the first three alphanumeric characters of the final extension are preserved,
1623 forced to upper case and appear as the extension of the mangled name. The
1624 final extension is defined as that part of the original filename after the
1625 rightmost dot. If there are no dots in the filename, the mangled name will
1626 have no extension (except in the case of hidden files - see below).
1628 - files whose UNIX name begins with a dot will be presented as DOS hidden
1629 files. The mangled name will be created as for other filenames, but with the
1630 leading dot removed and "___" as its extension regardless of actual original
1631 extension (that's three underscores).
1634 The two-digit hash value consists of upper case alphanumeric characters.
1636 This algorithm can cause name collisions only if files in a directory share
1637 the same first five alphanumeric characters. The probability of such a clash
1640 The name mangling (if enabled) allows a file to be copied between UNIX
1641 directories from DOS while retaining the long UNIX filename. UNIX files can
1642 be renamed to a new extension from DOS and will retain the same basename.
1643 Mangled names do not change between sessions.
1650 .SS mangling char (S)
1651 This controls what character is used as the "magic" character in name
1652 mangling. The default is a ~ but this may interfere with some
1653 software. Use this option to set it to whatever you prefer.
1661 .SS mangled stack (G)
1662 This parameter controls the number of mangled names that should be cached in
1665 This stack is a list of recently mangled base names (extensions are only
1666 maintained if they are longer than 3 characters or contains upper case
1669 The larger this value, the more likely it is that mangled names can be
1670 successfully converted to correct long UNIX names. However, large stack
1671 sizes will slow most directory access. Smaller stacks save memory in the
1672 server (each stack element costs 256 bytes).
1674 It is not possible to absolutely guarantee correct long file names, so
1675 be prepared for some surprises!
1684 This controls whether the DOS archive attribute should be mapped to UNIX
1685 execute bits. The DOS archive bit is set when a file has been modified
1686 since its last backup. One motivation for this option it to keep Samba/your
1687 PC from making any file it touches from becoming executable under UNIX.
1688 This can be quite annoying for shared source code, documents, etc...
1697 This controls whether DOS style hidden files should be mapped to UNIX
1706 This controls whether DOS style system files should be mapped to UNIX
1714 .SS max connections (S)
1715 This option allows the number of simultaneous connections to a
1716 service to be limited. If "max connections" is greater than 0 then
1717 connections will be refused if this number of connections to the
1718 service are already open. A value of zero mean an unlimited number of
1719 connections may be made.
1721 Record lock files are used to implement this feature. The lock files
1722 will be stored in the directory specified by the "lock directory" option.
1728 max connections = 10
1730 .SS max disk size (G)
1731 This option allows you to put an upper limit on the apparent size of
1732 disks. If you set this option to 100 then all shares will appear to be
1733 not larger than 100 MB in size.
1735 Note that this option does not limit the amount of data you can put on
1736 the disk. In the above case you could still store much more than 100
1737 MB on the disk, but if a client ever asks for the amount of free disk
1738 space or the total disk size then the result will be bounded by the
1739 amount specified in "max disk size".
1741 This option is primarily useful to work around bugs in some pieces of
1742 software that can't handle very large disks, particularly disks over
1745 A "max disk size" of 0 means no limit.
1751 max disk size = 1000
1753 .SS max log size (G)
1755 This option (an integer in kilobytes) specifies the max size the log
1756 file should grow to. Samba periodically checks the size and if it is
1757 exceeded it will rename the file, adding a .old extension.
1759 A size of 0 means no limit.
1769 This option controls the maximum number of simultaneous reads that
1770 samba tells the client it will allow. You should never need to set this
1778 A synonym for this parameter is 'packet size'.
1782 This option tells nmbd what the default 'time to live' of NetBIOS
1783 names should be (in seconds). You should never need to change this parameter.
1789 This option controls the maximum packet size that will be negotiated
1790 by Samba. The default is 65535, which is the maximum. In some cases
1791 you may find you get better performance with a smaller value. A value
1792 below 2048 is likely to cause problems.
1800 .SS message command (G)
1802 This specifies what command to run when the server receives a WinPopup
1805 This would normally be a command that would deliver the message
1806 somehow. How this is to be done is up to your imagination.
1810 message command = csh -c 'xedit %s;rm %s' &
1812 This delivers the message using xedit, then removes it
1813 afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN
1814 IMMEDIATELY. That's why I have the & on the end. If it doesn't return
1815 immediately then your PCs may freeze when sending messages (they
1816 should recover after 30secs, hopefully).
1818 All messages are delivered as the global guest user. The command takes
1819 the standard substitutions, although %u won't work (%U may be better
1822 Apart from the standard substitutions, some additional ones apply. In
1825 %s = the filename containing the message
1827 %t = the destination that the message was sent to (probably the server
1830 %f = who the message is from
1832 You could make this command send mail, or whatever else takes your
1833 fancy. Please let me know of any really interesting ideas you have.
1835 Here's a way of sending the messages as mail to root:
1837 message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
1839 If you don't have a message command then the message won't be
1840 delivered and Samba will tell the sender there was an
1841 error. Unfortunately WfWg totally ignores the error code and carries
1842 on regardless, saying that the message was delivered.
1844 If you want to silently delete it then try "message command = rm %s".
1846 For the really adventurous, try something like this:
1848 message command = csh -c 'csh < %s |& /usr/local/samba/bin/smbclient \e
1851 this would execute the command as a script on the server, then give
1852 them the result in a WinPopup message. Note that this could cause a
1853 loop if you send a message from the server using smbclient! You better
1854 wrap the above in a script that checks for this :-)
1860 message command = csh -c 'xedit %s;rm %s' &
1862 .SS min print space (S)
1864 This sets the minimum amount of free disk space that must be available
1865 before a user will be able to spool a print job. It is specified in
1866 kilobytes. The default is 0, which means no limit.
1872 min print space = 2000
1874 .SS netbios name (G)
1876 This sets the NetBIOS name by which a Samba server is known. By
1877 default it is the same as the first component of the host's DNS name.
1880 Get the home share server from a NIS (or YP) map. For unix systems that
1881 use an automounter, the user's home directory will often be mounted on
1882 a workstation on demand from a remote server. When the Samba logon server
1883 is not the actual home directory server, two network hops are required
1884 to access the home directory and this can be very slow especially with
1885 writing via Samba to an NFS mounted directory. This option allows samba
1886 to return the home share as being on a different server to the logon
1887 server and as long as a samba daemon is running on the home directory
1888 server, it will be mounted on the Samba client directly from the directory
1889 server. When Samba is returning the home share to the client, it will
1890 consult the NIS (or YP) map specified in "homedir map" and return the
1891 server listed there.
1899 .SS null passwords (G)
1900 Allow or disallow access to accounts that have null passwords.
1906 null passwords = yes
1909 A synonym for this command is 'guest only'.
1912 This is a boolean option that controls whether connections with
1913 usernames not in the user= list will be allowed. By default this
1914 option is disabled so a client can supply a username to be used by
1917 Note that this also means Samba won't try to deduce usernames from the
1918 service name. This can be annoying for the [homes] section. To get
1919 around this you could use "user = %S" which means your "user" list
1920 will be just the service name, which for home directories is the name
1930 This integer value controls what level Samba advertises itself as for
1931 browse elections. See BROWSING.txt for details.
1934 The maximum transmit packet size during a raw read. This option is no
1935 longer implemented as of version 1.7.00, and is kept only so old
1936 configuration files do not become invalid.
1939 This string controls the "chat" conversation that takes places
1940 between smbd and the local password changing program to change the
1941 users password. The string describes a sequence of response-receive
1942 pairs that smbd uses to determine what to send to the passwd program
1943 and what to expect back. If the expected output is not received then
1944 the password is not changed.
1946 This chat sequence is often quite site specific, depending on what
1947 local methods are used for password control (such as NIS+ etc).
1949 The string can contain the macros %o and %n which are substituted for
1950 the old and new passwords respectively. It can also contain the
1951 standard macros \en \er \et and \es to give line-feed, carriage-return,
1954 The string can also contain a * which matches any sequence of
1957 Double quotes can be used to collect strings with spaces in them into
1960 If the send string in any part of the chat sequence is a fullstop "."
1961 then no string is sent. Similarly, is the expect string is a fullstop
1962 then no string is expected.
1965 passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en \e
1966 "*Reenter NEW password*" %n\en "*Password changed*"
1970 passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed*
1972 .SS passwd program (G)
1973 The name of a program that can be used to set user passwords.
1975 This is only necessary if you have enabled remote password changing at
1976 compile time. Any occurrences of %u will be replaced with the user
1979 Also note that many passwd programs insist in "reasonable" passwords,
1980 such as a minimum length, or the inclusion of mixed case chars and
1981 digits. This can pose a problem as some clients (such as Windows for
1982 Workgroups) uppercase the password before sending it.
1985 passwd program = /bin/passwd
1988 passwd program = /sbin/passwd %u
1990 .SS password level (G)
1991 Some client/server combinations have difficulty with mixed-case passwords.
1992 One offending client is Windows for Workgroups, which for some reason forces
1993 passwords to upper case when using the LANMAN1 protocol, but leaves them alone
1994 when using COREPLUS!
1996 This parameter defines the maximum number of characters that may be upper case
1999 For example, say the password given was "FRED". If
2001 is set to 1 (one), the following combinations would be tried if "FRED" failed:
2002 "Fred", "fred", "fRed", "frEd", "freD". If
2003 .B password level was set to 2 (two), the following combinations would also be
2004 tried: "FRed", "FrEd", "FreD", "fREd", "fReD", "frED". And so on.
2006 The higher value this parameter is set to the more likely it is that a mixed
2007 case password will be matched against a single case password. However, you
2008 should be aware that use of this parameter reduces security and increases the
2009 time taken to process a new connection.
2011 A value of zero will cause only two attempts to be made - the password as is
2012 and the password in all-lower case.
2014 If you find the connections are taking too long with this option then
2015 you probably have a slow crypt() routine. Samba now comes with a fast
2016 "ufc crypt" that you can select in the Makefile. You should also make
2017 sure the PASSWORD_LENGTH option is correct for your system in local.h
2018 and includes.h. On most systems only the first 8 chars of a password
2019 are significant so PASSWORD_LENGTH should be 8, but on some longer
2020 passwords are significant. The includes.h file tries to select the
2021 right length for your system.
2029 .SS password server (G)
2031 By specifying the name of another SMB server (such as a WinNT box)
2032 with this option, and using "security = server" you can get Samba to
2033 do all its username/password validation via a remote server.
2035 This options sets the name of the password server to use. It must be a
2036 netbios name, so if the machine's netbios name is different from its
2037 internet name then you may have to add its netbios name to
2040 The password server much be a machine capable of using the "LM1.2X002"
2041 or the "LM NT 0.12" protocol, and it must be in user level security
2044 NOTE: Using a password server means your UNIX box (running Samba) is
2045 only as secure as your password server. DO NOT CHOOSE A PASSWORD
2046 SERVER THAT YOU DON'T COMPLETELY TRUST.
2048 Never point a Samba server at itself for password serving. This will
2049 cause a loop and could lock up your Samba server!
2051 The name of the password server takes the standard substitutions, but
2052 probably the only useful one is %m, which means the Samba server will
2053 use the incoming client as the password server. If you use this then
2054 you better trust your clients, and you better restrict them with hosts
2057 If you list several hosts in the "password server" option then smbd
2058 will try each in turn till it finds one that responds. This is useful
2059 in case your primary server goes down.
2062 A synonym for this parameter is 'directory'.
2064 This parameter specifies a directory to which the user of the service is to
2065 be given access. In the case of printable services, this is where print data
2066 will spool prior to being submitted to the host for printing.
2068 For a printable service offering guest access, the service should be readonly
2069 and the path should be world-writable and have the sticky bit set. This is not
2070 mandatory of course, but you probably won't get the results you expect if you
2073 Any occurrences of %u in the path will be replaced with the username
2074 that the client is connecting as. Any occurrences of %m will be
2075 replaced by the name of the machine they are connecting from. These
2076 replacements are very useful for setting up pseudo home directories
2079 Note that this path will be based on 'root dir' if one was specified.
2088 This option specifies a command to be run whenever the service is
2089 disconnected. It takes the usual substitutions. The command may be run
2090 as the root on some systems.
2092 An interesting example may be do unmount server resources:
2094 postexec = /etc/umount /cdrom
2099 none (no command executed)
2102 postexec = echo \e"%u disconnected from %S from %m (%I)\e" >> /tmp/log
2105 This parameter forces a printer to interpret the print files as
2106 postscript. This is done by adding a %! to the start of print output.
2108 This is most useful when you have lots of PCs that persist in putting
2109 a control-D at the start of print jobs, which then confuses your
2120 This option specifies a command to be run whenever the service is
2121 connected to. It takes the usual substitutions.
2123 An interesting example is to send the users a welcome message every
2124 time they log in. Maybe a message of the day? Here is an example:
2126 preexec = csh -c 'echo \e"Welcome to %S!\e" | \e
2127 /usr/local/samba/bin/smbclient -M %m -I %I' &
2129 Of course, this could get annoying after a while :-)
2134 none (no command executed)
2137 preexec = echo \e"%u connected to %S from %m (%I)\e" >> /tmp/log
2139 .SS preferred master (G)
2140 This boolean parameter controls if Samba is a preferred master browser
2142 If this is set to true, on startup, samba will force an election,
2143 and it will have a slight advantage in winning the election.
2144 It is recommended that this parameter is used in conjunction
2145 with domain master = yes, so that samba can guarantee becoming
2148 Use this option with caution, because if there are several hosts
2149 (whether samba servers, Windows 95 or NT) that are preferred master
2150 browsers on the same subnet, they will each periodically and continuously
2151 attempt to become the local master browser. This will result in
2152 unnecessary broadcast traffic and reduced browsing capabilities.
2158 preferred master = no
2161 This is an alias for "auto services"
2163 .SS preserve case (S)
2165 This controls if new filenames are created with the case that the
2166 client passes, or if they are forced to be the "default" case.
2171 See the section on "NAME MANGLING" for a fuller discussion.
2173 .SS print command (S)
2174 After a print job has finished spooling to a service, this command will be
2175 used via a system() call to process the spool file. Typically the command
2176 specified will submit the spool file to the host's printing subsystem, but
2177 there is no requirement that this be the case. The server will not remove the
2178 spool file, so whatever command you specify should remove the spool file when
2179 it has been processed, otherwise you will need to manually remove old spool
2182 The print command is simply a text string. It will be used verbatim,
2183 with two exceptions: All occurrences of "%s" will be replaced by the
2184 appropriate spool file name, and all occurrences of "%p" will be
2185 replaced by the appropriate printer name. The spool file name is
2186 generated automatically by the server, the printer name is discussed
2189 The full path name will be used for the filename if %s is not preceded
2190 by a /. If you don't like this (it can stuff up some lpq output) then
2191 use %f instead. Any occurrences of %f get replaced by the spool
2192 filename without the full path at the front.
2194 The print command MUST contain at least one occurrence of "%s" or %f -
2195 the "%p" is optional. At the time a job is submitted, if no printer
2196 name is supplied the "%p" will be silently removed from the printer
2199 If specified in the [global] section, the print command given will be used
2200 for any printable service that does not have its own print command specified.
2202 If there is neither a specified print command for a printable service nor a
2203 global print command, spool files will be created but not processed and (most
2204 importantly) not removed.
2206 Note that printing may fail on some UNIXes from the "nobody"
2207 account. If this happens then create an alternative guest account that
2208 can print and set the "guest account" in the [global] section.
2210 You can form quite complex print commands by realising that they are
2211 just passed to a shell. For example the following will log a print
2212 job, print the file, then remove it. Note that ; is the usual
2213 separator for command in shell scripts.
2215 print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s
2217 You may have to vary this command considerably depending on how you
2218 normally print files on your system.
2221 print command = lpr -r -P %p %s
2224 print command = /usr/local/samba/bin/myprintscript %p %s
2229 A synonym for this parameter is 'print ok'.
2231 If this parameter is 'yes', then clients may open, write to and submit spool
2232 files on the directory specified for the service.
2234 Note that a printable service will ALWAYS allow writing to the service path
2235 (user privileges permitting) via the spooling of print data. The 'read only'
2236 parameter controls only non-printing access to the resource.
2244 .SS printcap name (G)
2245 This parameter may be used to override the compiled-in default printcap
2246 name used by the server (usually /etc/printcap). See the discussion of the
2247 [printers] section above for reasons why you might want to do this.
2249 For those of you without a printcap (say on SysV) you can just create a
2250 minimal file that looks like a printcap and set "printcap name =" in
2251 [global] to point at it.
2253 A minimal printcap file would look something like this:
2265 where the | separates aliases of a printer. The fact that the second
2266 alias has a space in it gives a hint to Samba that it's a comment.
2268 NOTE: Under AIX the default printcap name is "/etc/qconfig". Samba
2269 will assume the file is in AIX "qconfig" format if the string
2270 "/qconfig" appears in the printcap filename.
2273 printcap name = /etc/printcap
2276 printcap name = /etc/myprintcap
2278 A synonym for this parameter is 'printer name'.
2280 This parameter specifies the name of the printer to which print jobs spooled
2281 through a printable service will be sent.
2283 If specified in the [global] section, the printer name given will be used
2284 for any printable service that does not have its own printer name specified.
2287 none (but may be 'lp' on many systems)
2290 printer name = laserwriter
2292 .SS printer driver (S)
2293 This option allows you to control the string that clients receive when
2294 they ask the server for the printer driver associated with a
2295 printer. If you are using Windows95 or WindowsNT then you can use this
2296 to automate the setup of printers on your system.
2298 You need to set this parameter to the exact string (case sensitive)
2299 that describes the appropriate printer driver for your system.
2300 If you don't know the exact string to use then you should first try
2301 with no "printer driver" option set and the client will give you a
2302 list of printer drivers. The appropriate strings are shown in a
2303 scrollbox after you have chosen the printer manufacturer.
2306 printer driver = HP LaserJet 4L
2308 .SS printer name (S)
2313 This parameters controls how printer status information is interpreted
2314 on your system, and also affects the default values for the "print
2315 command", "lpq command" and "lprm command".
2317 Currently six printing styles are supported. They are "printing =
2318 bsd", "printing = sysv", "printing = hpux", "printing = aix",
2319 "printing = qnx" and "printing = plp".
2321 To see what the defaults are for the other print commands when using
2322 these three options use the "testparm" program.
2326 The value of the parameter (a string) is the highest protocol level that will
2327 be supported by the server.
2329 Possible values are CORE, COREPLUS, LANMAN1, LANMAN2 and NT1. The relative
2330 merits of each are discussed in the README file.
2332 Normally this option should not be set as the automatic negotiation
2333 phase in the SMB protocol takes care of choosing the appropriate protocol.
2341 A synonym for this parameter is 'guest ok'.
2343 If this parameter is 'yes' for a service, then no password is required
2344 to connect to the service. Privileges will be those of the guest
2347 See the section below on user/password validation for more information about
2356 This is a list of users that are given read-only access to a
2357 service. If the connecting user is in this list then they will
2358 not be given write access, no matter what the "read only" option
2359 is set to. The list can include group names using the @group syntax.
2361 See also the "write list" option
2367 read list = mary, @students
2374 Note that this is an inverted synonym for writable and write ok.
2375 .SS read prediction (G)
2376 This options enables or disables the read prediction code used to
2377 speed up reads from the server. When enabled the server will try to
2378 pre-read data from the last accessed file that was opened read-only
2379 while waiting for packets.
2382 read prediction = False
2385 read prediction = True
2387 This parameter controls whether or not the server will support raw reads when
2388 transferring data to clients.
2390 If enabled, raw reads allow reads of 65535 bytes in one packet. This
2391 typically provides a major performance benefit.
2393 However, some clients either negotiate the allowable block size incorrectly
2394 or are incapable of supporting larger block sizes, and for these clients you
2395 may need to disable raw reads.
2397 In general this parameter should be viewed as a system tuning tool and left
2398 severely alone. See also
2408 The option "read size" affects the overlap of disk reads/writes with
2409 network reads/writes. If the amount of data being transferred in
2410 several of the SMB commands (currently SMBwrite, SMBwriteX and
2411 SMBreadbraw) is larger than this value then the server begins writing
2412 the data before it has received the whole packet from the network, or
2413 in the case of SMBreadbraw, it begins writing to the network before
2414 all the data has been read from disk.
2416 This overlapping works best when the speeds of disk and network access
2417 are similar, having very little effect when the speed of one is much
2418 greater than the other.
2420 The default value is 2048, but very little experimentation has been
2421 done yet to determine the optimal value, and it is likely that the best
2422 value will vary greatly between systems anyway. A value over 65536 is
2423 pointless and will cause you to allocate memory unnecessarily.
2431 .SS remote announce (G)
2433 This option allows you to setup nmbd to periodically announce itself
2434 to arbitrary IP addresses with an arbitrary workgroup name.
2436 This is useful if you want your Samba server to appear in a remote
2437 workgroup for which the normal browse propagation rules don't
2438 work. The remote workgroup can be anywhere that you can send IP
2443 remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
2445 the above line would cause nmbd to announce itself to the two given IP
2446 addresses using the given workgroup names. If you leave out the
2447 workgroup name then the one given in the "workgroup" option is used
2450 The IP addresses you choose would normally be the broadcast addresses
2451 of the remote networks, but can also be the IP addresses of known
2452 browse masters if your network config is that stable.
2454 This option replaces similar functionality from the nmbd lmhosts file.
2458 This options controls whether Samba will allow a previously validated
2459 username/password pair to be used to attach to a share. Thus if you
2460 connect to \e\eserver\eshare1 then to \e\eserver\eshare2 it won't
2461 automatically allow the client to request connection to the second
2462 share as the same username as the first without a password.
2464 If "revalidate" is True then the client will be denied automatic
2465 access as the same username.
2479 .SS root directory (G)
2480 Synonyms for this parameter are 'root dir' and 'root'.
2482 The server will chroot() to this directory on startup. This is not
2483 strictly necessary for secure operation. Even without it the server
2484 will deny access to files not in one of the service entries. It may
2485 also check for, and deny access to, soft links to other parts of the
2486 filesystem, or attempts to use .. in file names to access other
2487 directories (depending on the setting of the "wide links" parameter).
2489 Adding a "root dir" entry other than "/" adds an extra level of security,
2490 but at a price. It absolutely ensures that no access is given to files not
2491 in the sub-tree specified in the "root dir" option, *including* some files
2492 needed for complete operation of the server. To maintain full operability
2493 of the server you will need to mirror some system files into the "root dir"
2494 tree. In particular you will need to mirror /etc/passwd (or a subset of it),
2495 and any binaries or configuration files needed for printing (if required).
2496 The set of files that must be mirrored is operating system dependent.
2502 root directory = /homes/smb
2503 .SS root postexec (S)
2505 This is the same as postexec except that the command is run as
2506 root. This is useful for unmounting filesystems (such as cdroms) after
2507 a connection is closed.
2509 .SS root preexec (S)
2511 This is the same as preexec except that the command is run as
2512 root. This is useful for mounting filesystems (such as cdroms) before
2513 a connection is finalised.
2516 This option affects how clients respond to Samba.
2518 The option sets the "security mode bit" in replies to protocol negotiations
2519 to turn share level security on or off. Clients decide based on this bit
2520 whether (and how) to transfer user and password information to the server.
2522 The default is "security=SHARE", mainly because that was the only
2523 option at one stage.
2525 The alternatives are "security = user" or "security = server".
2527 If your PCs use usernames that are the same as their usernames on the
2528 UNIX machine then you will want to use "security = user". If you
2529 mostly use usernames that don't exist on the UNIX box then use
2532 There is a bug in WfWg that may affect your decision. When in user
2533 level security a WfWg client will totally ignore the password you type
2534 in the "connect drive" dialog box. This makes it very difficult (if
2535 not impossible) to connect to a Samba service as anyone except the
2536 user that you are logged into WfWg as.
2538 If you use "security = server" then Samba will try to validate the
2539 username/password by passing it to another SMB server, such as an NT
2540 box. If this fails it will revert to "security = USER".
2542 See the "password server" option for more details.
2549 .SS server string (G)
2550 This controls what string will show up in the printer comment box in
2551 print manager and next to the IPC connection in "net view". It can be
2552 any string that you wish to show to your users.
2554 It also sets what will appear in browse lists next to the machine name.
2556 A %v will be replaced with the Samba version number.
2558 A %h will be replaced with the hostname.
2561 server string = Samba %v
2564 server string = University of GNUs Samba Server
2566 .SS set directory (S)
2567 If 'set directory = no', then users of the service may not use the setdir
2568 command to change directory.
2570 The setdir command is only implemented in the Digital Pathworks client. See the
2571 Pathworks documentation for details.
2579 .SS shared file entries (G)
2580 This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES.
2581 It specifies the number of hash bucket entries used for share file locking.
2582 You should never change this parameter unless you have studied the source
2583 and know what you are doing.
2586 shared file entries = 113
2588 .SS shared mem size (G)
2589 This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES.
2590 It specifies the size of the shared memory (in bytes) to use between smbd
2591 processes. You should never change this parameter unless you have studied
2592 the source and know what you are doing.
2595 shared mem size = 102400
2597 .SS smb passwd file (G)
2598 This option sets the path to the encrypted smbpasswd file. This is a *VERY
2599 DANGEROUS OPTION* if the smb.conf is user writable. By default the path
2600 to the smbpasswd file is compiled into Samba.
2603 This sets the full path to the smbrun binary. This defaults to the
2604 value in the Makefile.
2606 You must get this path right for many services to work correctly.
2612 smbrun = /usr/local/samba/bin/smbrun
2616 This enables or disables the honouring of the "share modes" during a
2617 file open. These modes are used by clients to gain exclusive read or
2618 write access to a file.
2620 These open modes are not directly supported by UNIX, so they are
2621 simulated using lock files in the "lock directory". The "lock
2622 directory" specified in smb.conf must be readable by all users.
2624 The share modes that are enabled by this option are DENY_DOS,
2625 DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
2627 Enabling this option gives full share compatibility but may cost a bit
2628 of processing time on the UNIX server. They are enabled by default.
2636 .SS short preserve case (S)
2638 This controls if new short filenames are created with the case that
2639 the client passes, or if they are forced to be the "default" case.
2642 short preserve case = no
2644 See the section on "NAME MANGLING" for a fuller discussion.
2646 .SS socket address (G)
2648 This option allows you to control what address Samba will listen for
2649 connections on. This is used to support multiple virtual interfaces on
2650 the one server, each with a different configuration.
2652 By default samba will accept connections on any address.
2655 socket address = 192.168.2.20
2657 .SS socket options (G)
2658 This option (which can also be invoked with the -O command line
2659 option) allows you to set socket options to be used when talking with
2662 Socket options are controls on the networking layer of the operating
2663 systems which allow the connection to be tuned.
2665 This option will typically be used to tune your Samba server for
2666 optimal performance for your local network. There is no way that Samba
2667 can know what the optimal parameters are for your net, so you must
2668 experiment and choose them yourself. I strongly suggest you read the
2669 appropriate documentation for your operating system first (perhaps
2670 "man setsockopt" will help).
2672 You may find that on some systems Samba will say "Unknown socket
2673 option" when you supply an option. This means you either mis-typed it
2674 or you need to add an include file to includes.h for your OS. If the
2675 latter is the case please send the patch to me
2676 (samba-bugs@samba.anu.edu.au).
2678 Any of the supported socket options may be combined in any way you
2679 like, as long as your OS allows it.
2681 This is the list of socket options currently settable using this
2704 Those marked with a * take an integer argument. The others can
2705 optionally take a 1 or 0 argument to enable or disable the option, by
2706 default they will be enabled if you don't specify 1 or 0.
2708 To specify an argument use the syntax SOME_OPTION=VALUE for example
2709 SO_SNDBUF=8192. Note that you must not have any spaces before or after
2712 If you are on a local network then a sensible option might be
2714 socket options = IPTOS_LOWDELAY
2716 If you have an almost unloaded local network and you don't mind a lot
2717 of extra CPU usage in the server then you could try
2719 socket options = IPTOS_LOWDELAY TCP_NODELAY
2721 If you are on a wide area network then perhaps try setting
2724 Note that several of the options may cause your Samba server to fail
2725 completely. Use these options with caution!
2731 socket options = IPTOS_LOWDELAY
2737 This enables or disables logging of connections to a status file that
2743 won't be able to tell you what
2744 connections are active.
2752 .SS strict locking (S)
2753 This is a boolean that controls the handling of file locking in the
2754 server. When this is set to yes the server will check every read and
2755 write access for file locks, and deny access if locks exist. This can
2756 be slow on some systems.
2758 When strict locking is "no" the server does file lock checks only when
2759 the client explicitly asks for them.
2761 Well behaved clients always ask for lock checks when it is important,
2762 so in the vast majority of cases "strict locking = no" is preferable.
2768 strict locking = yes
2771 This is a boolean that controls whether to strip trailing dots off
2772 filenames. This helps with some CDROMs that have filenames ending in a
2775 NOTE: This option is now obsolete, and may be removed in future. You
2776 should use the "mangled map" option instead as it is much more
2780 This parameter maps how Samba debug messages are logged onto the
2781 system syslog logging levels. Samba debug level zero maps onto
2782 syslog LOG_ERR, debug level one maps onto LOG_WARNING, debug
2783 level two maps to LOG_NOTICE, debug level three maps onto LOG_INFO.
2784 The paramter sets the threshold for doing the mapping, all Samba
2785 debug messages above this threashold are mapped to syslog LOG_DEBUG
2793 If this parameter is set then Samba debug messages are logged into
2794 the system syslog only, and not to the debug log files.
2801 This is a boolean parameter that controls whether writes will always
2802 be written to stable storage before the write call returns. If this is
2803 false then the server will be guided by the client's request in each
2804 write call (clients can set a bit indicating that a particular write
2805 should be synchronous). If this is true then every write will be
2806 followed by a fsync() call to ensure the data is written to disk.
2815 This parameter is a setting in minutes to add to the normal GMT to
2816 local time conversion. This is useful if you are serving a lot of PCs
2817 that have incorrect daylight saving time handling.
2825 .SS unix realname (G)
2826 This boolean parameter when set causes samba to supply the real name field
2827 from the unix password file to the client. This is useful for setting up
2828 mail clients and WWW browsers on systems used by more than one person.
2840 A synonym for this parameter is 'user'.
2842 Multiple users may be specified in a comma-delimited list, in which case the
2843 supplied password will be tested against each username in turn (left to right).
2845 The username= line is needed only when the PC is unable to supply its own
2846 username. This is the case for the coreplus protocol or where your
2847 users have different WfWg usernames to UNIX usernames. In both these
2848 cases you may also be better using the \e\eserver\eshare%user syntax
2851 The username= line is not a great solution in many cases as it means Samba
2852 will try to validate the supplied password against each of the
2853 usernames in the username= line in turn. This is slow and a bad idea for
2854 lots of users in case of duplicate passwords. You may get timeouts or
2855 security breaches using this parameter unwisely.
2857 Samba relies on the underlying UNIX security. This parameter does not
2858 restrict who can login, it just offers hints to the Samba server as to
2859 what usernames might correspond to the supplied password. Users can
2860 login as whoever they please and they will be able to do no more
2861 damage than if they started a telnet session. The daemon runs as the
2862 user that they log in as, so they cannot do anything that user cannot
2865 To restrict a service to a particular set of users you can use the
2866 "valid users=" line.
2868 If any of the usernames begin with a @ then the name will be looked up
2869 in the groups file and will expand to a list of all users in the group
2870 of that name. Note that searching though a groups file can take quite
2871 some time, and some clients may time out during the search.
2873 See the section below on username/password validation for more information
2874 on how this parameter determines access to the services.
2877 The guest account if a guest service, else the name of the service.
2881 username = fred, mary, jack, jane, @users, @pcgroup
2883 .SS username map (G)
2885 This option allows you to to specify a file containing a mapping of
2886 usernames from the clients to the server. This can be used for several
2887 purposes. The most common is to map usernames that users use on DOS or
2888 Windows machines to those that the UNIX box uses. The other is to map
2889 multiple users to a single username so that they can more easily share
2892 The map file is parsed line by line. Each line should contain a single
2893 UNIX username on the left then a '=' followed by a list of usernames
2894 on the right. The list of usernames on the right may contain names of
2895 the form @group in which case they will match any UNIX username in
2896 that group. The special client name '*' is a wildcard and matches any
2899 The file is processed on each line by taking the supplied username and
2900 comparing it with each username on the right hand side of the '='
2901 signs. If the supplied name matches any of the names on the right
2902 hand side then it is replaced with the name on the left. Processing
2903 then continues with the next line.
2905 If any line begins with a '#' or a ';' then it is ignored
2907 For example to map from the name "admin" or "administrator" to the UNIX
2908 name "root" you would use
2910 root = admin administrator
2912 Or to map anyone in the UNIX group "system" to the UNIX name "sys" you
2917 You can have as many mappings as you like in a username map file.
2919 Note that the remapping is applied to all occurrences of
2920 usernames. Thus if you connect to "\e\eserver\efred" and "fred" is
2921 remapped to "mary" then you will actually be connecting to
2922 "\e\eserver\emary" and will need to supply a password suitable for
2923 "mary" not "fred". The only exception to this is the username passed
2924 to the "password server" (if you have one). The password server will
2925 receive whatever username the client supplies without modification.
2927 Also note that no reverse mapping is done. The main effect this has is
2928 with printing. Users who have been mapped may have trouble deleting
2929 print jobs as PrintManager under WfWg will think they don't own the
2936 username map = /usr/local/samba/lib/users.map
2940 The option allows you to specify additional characters that should be
2941 considered valid by the server in filenames. This is particularly
2942 useful for national character sets, such as adding u-umlaut or a-ring.
2944 The option takes a list of characters in either integer or character
2945 form with spaces between them. If you give two characters with a colon
2946 between them then it will be taken as an lowercase:uppercase pair.
2948 If you have an editor capable of entering the characters into the
2949 config file then it is probably easiest to use this method. Otherwise
2950 you can specify the characters in octal, decimal or hexadecimal form
2951 using the usual C notation.
2953 For example to add the single character 'Z' to the charset (which is a
2954 pointless thing to do as it's already there) you could do one of the
2959 valid chars = 0132:0172
2961 The last two examples above actually add two characters, and alter
2962 the uppercase and lowercase mappings appropriately.
2966 Samba defaults to using a reasonable set of valid characters
2971 valid chars = 0345:0305 0366:0326 0344:0304
2973 The above example allows filenames to have the swedish characters in
2976 NOTE: It is actually quite difficult to correctly produce a "valid
2977 chars" line for a particular system. To automate the process
2978 tino@augsburg.net has written a package called "validchars" which will
2979 automatically produce a complete "valid chars" line for a given client
2980 system. Look in the examples subdirectory for this package.
2983 This is a list of users that should be allowed to login to this
2984 service. A name starting with @ is interpreted as a UNIX group.
2986 If this is empty (the default) then any user can login. If a username
2987 is in both this list and the "invalid users" list then access is
2988 denied for that user.
2990 The current servicename is substituted for %S. This is useful in the
2993 See also "invalid users"
2996 No valid users list. (anyone can login)
2999 valid users = greg, @pcusers
3003 This is a list of files and directories that are neither visible nor
3004 accessible. Each entry in the list must be separate by a "/", which
3005 allows spaces to be included in the entry. Note that '*' and '?' at
3006 present cannot be used to specify multiple files or directories.
3009 No files or directories are vetoed.
3012 veto files = DesktopFolderDB/TrashFor%m/resource.frk
3014 The above example is based on files that the Macintosh client (DAVE)
3015 creates for internal use.
3018 This allows you to override the volume label returned for a
3019 share. Useful for CDROMs with installation programs that insist on a
3020 particular volume label.
3022 The default is the name of the share
3025 This parameter controls whether or not links in the UNIX file system may be
3026 followed by the server. Links that point to areas within the directory tree
3027 exported by the server are always allowed; this parameter controls access
3028 only to areas that are outside the directory tree being exported.
3038 This is a boolean that controls if nmbd will respond to broadcast name
3039 queries on behalf of other hosts. You may need to set this to no for
3046 This specifies the DNS name (or IP address) of the WINS server that Samba
3047 should register with. If you have a WINS server on your network then you
3048 should set this to the WINS servers name.
3050 You should point this at your WINS server if you have a multi-subnetted
3055 .SS wins support (G)
3057 This boolean controls if Samba will act as a WINS server. You should
3058 not set this to true unless you have a multi-subnetted network and
3059 you wish a particular nmbd to be your WINS server. Note that you
3060 should *NEVER* set this to true on more than one machine in your
3067 This controls what workgroup your server will appear to be in when
3077 A synonym for this parameter is 'write ok'. An inverted synonym is 'read only'.
3079 If this parameter is 'no', then users of a service may not create or modify
3080 files in the service's directory.
3082 Note that a printable service ('printable = yes') will ALWAYS allow
3083 writing to the directory (user privileges permitting), but only via
3084 spooling operations.
3094 This is a list of users that are given read-write access to a
3095 service. If the connecting user is in this list then they will be
3096 given write access, no matter what the "read only" option is set
3097 to. The list can include group names using the @group syntax.
3099 Note that if a user is in both the read list and the write list then
3100 they will be given write access.
3102 See also the "read list" option
3108 write list = admin, root, @staff
3116 This parameter controls whether or not the server will support raw writes when
3117 transferring data from clients.
3124 .SH NOTE ABOUT USERNAME/PASSWORD VALIDATION
3125 There are a number of ways in which a user can connect to a
3126 service. The server follows the following steps in determining if it
3127 will allow a connection to a specified service. If all the steps fail
3128 then the connection request is rejected. If one of the steps pass then
3129 the following steps are not checked.
3131 If the service is marked "guest only = yes" then steps 1 to 5 are skipped
3133 Step 1: If the client has passed a username/password pair and that
3134 username/password pair is validated by the UNIX system's password
3135 programs then the connection is made as that username. Note that this
3136 includes the \e\eserver\eservice%username method of passing a username.
3138 Step 2: If the client has previously registered a username with the
3139 system and now supplies a correct password for that username then the
3140 connection is allowed.
3142 Step 3: The client's netbios name and any previously used user names
3143 are checked against the supplied password, if they match then the
3144 connection is allowed as the corresponding user.
3146 Step 4: If the client has previously validated a username/password
3147 pair with the server and the client has passed the validation token
3148 then that username is used. This step is skipped if "revalidate = yes"
3151 Step 5: If a "user = " field is given in the smb.conf file for the
3152 service and the client has supplied a password, and that password
3153 matches (according to the UNIX system's password checking) with one of
3154 the usernames from the user= field then the connection is made as the
3155 username in the "user=" line. If one of the username in the user= list
3156 begins with a @ then that name expands to a list of names in the group
3159 Step 6: If the service is a guest service then a connection is made as
3160 the username given in the "guest account =" for the service,
3161 irrespective of the supplied password.
3163 Although the configuration file permits service names to contain spaces,
3164 your client software may not. Spaces will be ignored in comparisons anyway,
3165 so it shouldn't be a problem - but be aware of the possibility.
3167 On a similar note, many clients - especially DOS clients - limit service
3168 names to eight characters. Smbd has no such limitation, but attempts
3169 to connect from such clients will fail if they truncate the service names.
3170 For this reason you should probably keep your service names down to eight
3171 characters in length.
3173 Use of the [homes] and [printers] special sections make life for an
3174 administrator easy, but the various combinations of default attributes can be
3175 tricky. Take extreme care when designing these sections. In particular,
3176 ensure that the permissions on spool directories are correct.
3178 This man page is (mostly) correct for version 1.9.16 of the Samba suite, plus some
3179 of the recent patches to it. These notes will necessarily lag behind
3180 development of the software, so it is possible that your version of
3181 the server has extensions or parameter semantics that differ from or are not
3182 covered by this man page. Please notify these to the address below for
3185 Prior to version 1.5.21 of the Samba suite, the configuration file was
3186 radically different (more primitive). If you are using a version earlier than
3187 1.8.05, it is STRONGLY recommended that you upgrade.
3192 .SH ENVIRONMENT VARIABLES
3201 .BR hosts_access (5)
3203 [This section under construction]
3205 Most diagnostics issued by the server are logged in a specified log file. The
3206 log file name is specified at compile time, but may be overridden on the
3207 smbd command line (see
3210 The number and nature of diagnostics available depends on the debug level used
3211 by the server. If you have problems, set the debug level to 3 and peruse the
3214 Most messages are reasonably self-explanatory. Unfortunately, at time of
3215 creation of this man page the source code is still too fluid to warrant
3216 describing each and every diagnostic. At this stage your best bet is still
3217 to grep the source code and inspect the conditions that gave rise to the
3218 diagnostics you are seeing.
3222 Please send bug reports, comments and so on to:
3225 .B samba-bugs@samba.anu.edu.au (Andrew Tridgell)
3228 or to the mailing list:
3231 .B samba@listproc.anu.edu.au
3234 You may also like to subscribe to the announcement channel:
3237 .B samba-announce@listproc.anu.edu.au
3240 To subscribe to these lists send a message to
3241 listproc@listproc.anu.edu.au with a body of "subscribe samba Your
3242 Name" or "subscribe samba-announce Your Name".
3244 Errors or suggestions for improvements to the Samba man pages should be
3248 .B samba-bugs@samba.anu.edu.au (Andrew Tridgell)