The smb.conf file is a configuration file for the Samba suite. smb.conf contains runtime configuration information for the Samba programs. The smb.conf file is designed to be configured and administered by the swat(8) program. The complete description of the file format and possible parameters held within are here for reference purposes.
The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain parameters of the form
name = value .PP The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter.
Section and parameter names are not case sensitive.
Only the first equals sign in a parameter is significant. Whitespace before or after the first equals sign is discarded. Leading, trailing and internal whitespace in section and parameter names is irrelevant. Leading and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value is retained verbatim.
Any line beginning with a semicolon (';') or a hash ('#') character is ignored, as are lines containing only whitespace.
Any line ending in a '\' is continued on the next line in the customary UNIX fashion.
The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or true/false. Case is not significant in boolean values, but is preserved in string values. Some items such as create modes are numeric.
Each section in the configuration file (except for the [global] section) describes a shared resource (known as a "share"). The section name is the name of the shared resource and the parameters within the section define the shares attributes.
There are three special sections, [global], [homes] and [printers], which are described under special sections. The following notes apply to ordinary section descriptions.
A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service. Some housekeeping options are also specifiable.
Sections are either file share services (used by the client as an extension of their native file systems) or printable services (used by the client to access print services on the host running the server).
Sections may be designated guest services, in which case no password is required to access them. A specified UNIX guest account is used to define access privileges in this case.
Sections other than guest services will require a password to access them. The client provides the username. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the "user =" option in the share definition. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary.
Note that the access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system. The server does not grant more access than the host system grants.
The following sample section defines a file space share. The user has write access to the path /home/bar. The share is accessed via the share name "foo":
[foo]
path = /home/bar
writeable = true
The following sample section defines a printable share. The share is readonly, but printable. That is, the only write access permitted is via calls to open, write to and close a spool file. The guest ok parameter means access will be permitted as the default guest user (specified elsewhere):
[aprinter]
path = /usr/spool/public
writeable = false
printable = true
guest ok = true
parameters in this section apply to the server as a whole, or are defaults for sections which do not specifically define certain items. See the notes under PARAMETERS for more information.
If a section called homes is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server.
When the connection request is made, the existing sections are scanned. If a match is found, it is used. If no match is found, the requested section name is treated as a user name and looked up in the local password file. If the name exists and the correct password has been given, a share is created by cloning the [homes] section.
Some modifications are then made to the newly created share:
If you decide to use a path = line in your [homes] section then you may find it useful to use the %S macro. For example :
path = /data/pchome/%S
would be useful if you have different home directories for your PCs than for UNIX access.
This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss.
A similar process occurs if the requested section name is "homes", except that the share name is not changed to that of the requesting user. This method of using the [homes] section works well if different users share a client PC.
The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others. The following is a typical and suitable [homes] section:
[homes]
writeable = yes
An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients without a password. In the very unlikely event that this is actually desirable, it would be wise to also specify read only access.
Note that the browseable flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as it means setting browseable = no in the [homes] section will hide the [homes] share but make any auto home directories visible.
This section works like [homes], but for printers.
If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host's printcap file.
When a connection request is made, the existing sections are scanned. If a match is found, it is used. If no match is found, but a [homes] section exists, it is used as described above. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name. If a match is found, a new printer share is created by cloning the [printers] section.
A few modifications are then made to the newly created share:
Note that the [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file.
Typically the path specified would be that of a world-writeable spool directory with the sticky bit set on it. A typical [printers] entry would look like this:
[printers]
path = /usr/spool/public
guest ok = yes
printable = yes
All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file consisting of one or more lines like this:
alias|alias|alias|alias...
Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify the new file as your printcap. The server will then only recognize names found in your pseudo-printcap, which of course can contain whatever aliases you like. The same technique could be used simply to limit access to a subset of your local printers.
An alias, by the way, is defined as any component of the first entry of a printcap record. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols ('|').
NOTE: On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use "printcap name = lpstat" to automatically obtain a list of printers. See the "printcap name" option for more details.
parameters define the specific attributes of sections.
Some parameters are specific to the [global] section (e.g., security). Some parameters are usable in all sections (e.g., create mode). All others are permissible only in normal sections. For the purposes of the following descriptions the [homes] and [printers] sections will be considered normal. The letter G in parentheses indicates that a parameter is specific to the [global] section. The letter S indicates that a parameter can be specified in a service specific section. Note that all S parameters can also be specified in the [global] section - in which case they will define the default behavior for all services.
parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred synonym.
Many of the strings that are settable in the config file can take substitutions. For example the option "path = /tmp/%u" would be interpreted as "path = /tmp/john" if the user connected with the username john.
These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant. These are:
Note that this paramater is not available when Samba listens on port 445, as clients no longer send this information
There are some quite creative things that can be done with these substitutions and other smb.conf options.
Samba supports "name mangling" so that DOS and Windows clients can use files that don't conform to the 8.3 format. It can also be set to adjust the case of 8.3 format filenames.
There are several options that control the way mangling is performed, and they are grouped here rather than listed separately. For the defaults look at the output of the testparm program.
All of these options can be set separately for each service (or globally, of course).
The options are:
By default, Samba 2.2 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving.
There are a number of ways in which a user can connect to a service. The server uses the following steps in determining if it will allow a connection to a specified service. If all the steps fail, then the connection request is rejected. However, if one of the steps succeeds, then the following steps are not checked.
If the service is marked "guest only = yes" and the server is running with share-level security ("security = share") then steps 1 to 5 are skipped.
Here is a list of all global parameters. See the section of each parameter for details. Note that some are synonyms.
Here is a list of all service parameters. See the section on each parameter for details. Note that some are synonyms.
For a Samba host this means that the printer must be physically added to the underlying printing system. The add printer command defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the smb.conf file in order that it can be shared by smbd(8)
The add printer command is automatically invoked with the following parameter (in order:
All parameters are filled in from the PRINTER_INFO_2 structure sent by the Windows NT/2000 client with one exception. The "Windows 9x driver location" parameter is included for backwards compatibility only. The remaining fields in the structure are generated from answers to the APW questions.
Once the add printer command has been executed, smbd will reparse the smb.conf to determine if the share defined by the APW exists. If the sharename is still invalid, then smbd will return an ACCESS_DENIED error to the client.
See also delete printer command, printing, show add printer wizard
Default: none
Example: addprinter command = /usr/bin/addprinter .PP
When executed, smbd will automatically invoke the add share command with four parameters.
This parameter is only used for add file shares. To add printer shares, see the add printer command.
See also change share command, delete share command.
Default: none
Example: add share command = /usr/local/bin/addshare
Normally, a Samba server requires that UNIX users are created for all users accessing files on this server. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task. This option allows smbdto create the required UNIX users ON DEMAND when a user accesses the Samba server.
In order to use this option, smbd must NOT be set to security = share and add user script must be set to a full pathname for a script that will create a UNIX user given one argument of %u, which expands into the UNIX user name to create.
When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time, smbdcontacts the password server and attempts to authenticate the given user with the given password. If the authentication succeeds then smbd attempts to find a UNIX user in the UNIX password database to map the Windows user into. If this lookup fails, and add user script is set then smbd will call the specified script AS ROOT, expanding any %u argument to be the user name to create.
If this script successfully creates the user then smbd will continue on as though the UNIX user already existed. In this way, UNIX users are dynamically created to match existing Windows NT accounts.
See also security, password server, delete user script.
Default: add user script = <empty string> Example: add user script = /usr/local/samba/bin/add_user %u
You should use this option very carefully, as any user in this list will be able to do anything they like on the share, irrespective of file permissions.
Default: no admin users
Example: admin users = jason
This is useful if you only want your Samba server to serve resources to users in the domain it is a member of. As an example, suppose that there are two domains DOMA and DOMB. DOMB is trusted by DOMA, which contains the Samba server. Under normal circumstances, a user with an account in DOMB can then access the resources of a UNIX account with the same account name on the Samba server even if they do not have an account in DOMA. This can make implementing a security boundary difficult.
Default: allow trusted domains = yes
Default: announce as = NT Server
Example: announce as = Win95
Default: announce version = 4.5
Example: announce version = 2.0
Default: available = yes
For name service it causes nmbd to bind to ports 137 and 138 on the interfaces listed in the interfaces parameter. nmbd also binds to the "all addresses" interface (0.0.0.0) on ports 137 and 138 for the purposes of reading broadcast messages. If this option is not set then nmbd will service name requests on all of these sockets. If bind interfaces only is set then nmbd will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the interfaces parameter list. As unicast packets are received on the other sockets it allows nmbd to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the interfaces list. IP Source address spoofing does defeat this simple check, however so it must not be used seriously as a security feature for nmbd.
For file service it causes smbd(8) to bind only to the interface list given in the interfaces parameter. This restricts the networks that smbd will serve to packets coming in those interfaces. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces.
If bind interfaces only is set then unless the network address 127.0.0.1 is added to the interfaces parameter list smbpasswd(8) and swat(8)may not work as expected due to the reasons covered below.
To change a users SMB password, the smbpasswd by default connects to the localhost - 127.0.0.1 address as an SMB client to issue the password change request. If bind interfaces only is set then unless the network address 127.0.0.1 is added to the interfaces parameter list then smbpasswd will fail to connect in it's default mode. smbpasswd can be forced to use the primary IP interface of the local host by using its -r remote machine parameter, with remote machine set to the IP name of the primary interface of the local host.
The swat status page tries to connect with smbd and nmbd at the address 127.0.0.1 to determine if they are running. Not adding 127.0.0.1 will cause smbd and nmbd to always show "not running" even if they really are. This can prevent swat from starting/stopping/restarting smbd and nmbd.
Default: bind interfaces only = no
Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code. As this is an experimental option it may be removed in a future release.
Changing this option does not change the disk free reporting size, just the block size unit reported to the client.
Default: block size = 1024
Example: block size = 65536
If this parameter is set and the lock range requested cannot be immediately satisfied, Samba 2.2 will internally queue the lock request, and periodically attempt to obtain the lock until the timeout period expires.
If this parameter is set to false, then Samba 2.2 will behave as previous versions of Samba would and will fail the lock request immediately if the lock range cannot be obtained.
Default: blocking locks = yes
Default: browse list = yes
Default: browseable = yes
Default: case sensitive = no
Default: change notify timeout = 60
Example: change notify timeout = 300
Would change the scan time to every 5 minutes.
When executed, smbd will automatically invoke the change share command with four parameters.
This parameter is only used modify existing file shares definitions. To modify printer shares, use the "Printers..." folder as seen when browsing the Samba host.
See also add share command, delete share command.
Default: none
Example: change share command = /usr/local/bin/addshare
BUG. These MSDOS code page to UNIX character set mappings should be dynamic, like the loading of MS DOS code pages, not static.
Normally this parameter is not set, meaning no filename translation is done.
Default: character set = <empty string>
Example: character set = ISO8859-1
This parameter tells smbd(8) which of the codepage.XXX files to dynamically load on startup. These files, described more fully in the manual page make_smbcodepage(1), tell smbd how to map lower to upper case characters to provide the case insensitivity of filenames that Windows clients expect.
Samba currently ships with the following code page files :
Thus this parameter may have any of the values 437, 737, 850, 852, 861, 932, 936, 949, or 950. If you don't find the codepage you need, read the comments in one of the other codepage files and the make_smbcodepage(1) man page and write one. Please remember to donate it back to the Samba user community.
This parameter co-operates with the valid chars parameter in determining what characters are valid in filenames and how capitalization is done. If you set both this parameter and the valid chars parameter the client code page parameter MUST be set before the valid chars parameter in the smb.conf file. The valid chars string will then augment the character settings in the client code page parameter.
If not set, client code page defaults to 850.
See also : valid chars, code page directory
Default: client code page = 850
Example: client code page = 936
See also client code page
Default: code page directory = ${prefix}/lib/codepages Example: code page directory = /usr/share/samba/codepages .TP coding system (G) This parameter is used to determine how incoming Shift-JIS Japanese characters are mapped from the incoming client code page used by the client, into file names in the UNIX filesystem. Only useful if client code page is set to 932 (Japanese Shift-JIS). The options are :
Default: coding system = <empty value>
If you want to set the string that is displayed next to the machine name then see the server string parameter.
Default: No comment string
Example: comment = Fred's Files
For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file.
This option takes the usual substitutions, which can be very useful.
If the config file doesn't exist then it won't be loaded (allowing you to special case the config files of just a few clients).
Example: config file = /usr/local/samba/lib/smb.conf.%m .TP copy (S) This parameter allows you to "clone" service entries. The specified service is simply duplicated under the current service's name. Any parameters specified in the current section will override those in the section being copied.
This feature lets you set up a 'template' service and create similar services easily. Note that the service being copied must occur earlier in the configuration file than the service doing the copying.
Default: no value
Example: copy = otherservice
When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit not set here will be removed from the modes set on a file when it is created.
The default value of this parameter removes the 'group' and 'other' write and execute bits from the UNIX modes.
Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force create mode parameter which is set to 000 by default.
This parameter does not affect directory modes. See the parameter directory mode for details.
See also the force create mode parameter for forcing particular mode bits to be set on created files. See also the directory mode parameter for masking mode bits on created directories. See also the inherit permissions parameter.
Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the security mask.
Default: create mask = 0744
Example: create mask = 0775
These values correspond to those used on Windows servers.
For example, shares containing roaming profiles can have offline caching disabled using csc policy = disable .
Default: csc policy = manual
Example: csc policy = programs
This is useful to stop a server's resources being exhausted by a large number of inactive connections.
Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users.
Using this parameter with a timeout of a few minutes is recommended for most systems.
A deadtime of zero indicates that no auto-disconnection should be performed.
Default: deadtime = 0
Example: deadtime = 15
Note that the parameter debug timestamp must be on for this to have an effect.
Default: debug hires timestamp = no
Note that the parameter debug timestamp must be on for this to have an effect.
Default: debug pid = no
Default: debug timestamp = yes
Note that the parameter debug timestamp must be on for this to have an effect.
Default: debug uid = no
Default: default case = lower
Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode. Certain drivers will do things such as crashing the client's Explorer.exe with a NULL devmode. However, other printer drivers can cause the client's spooler service (spoolsv.exe) to die if the devmode was not created by the driver itself (i.e. smbd generates a default devmode).
This parameter should be used with care and tested with the printer driver in question. It is better to leave the device mode to NULL and let the Windows client set the correct values. Because drivers do not do this all the time, setting default devmode = yes will instruct smbd to generate a default one.
For more information on Windows NT/2k printing and Device Modes, see the MSDN documentation <URL:http://msdn.microsoft.com/>.
Default: default devmode = no
There is no default value for this parameter. If this parameter is not given, attempting to connect to a nonexistent service results in an error.
Typically the default service would be a guest ok, read-only service.
Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like %S to make a wildcard service.
Note also that any "_" characters in the name of the service used in the default service will get mapped to a "/". This allows for interesting things.
Example:
[global]
default service = pub
[pub]
path = /%S
For a Samba host this means that the printer must be physically deleted from underlying printing system. The deleteprinter command defines a script to be run which will perform the necessary operations for removing the printer from the print system and from smb.conf.
The delete printer command is automatically called with only one parameter: "printer name".
Once the delete printer command has been executed, smbd will reparse the smb.conf to associated printer no longer exists. If the sharename is still valid, then smbd will return an ACCESS_DENIED error to the client.
See also add printer command, printing, show add printer wizard
Default: none
Example: deleteprinter command = /usr/bin/removeprinter .TP delete readonly (S) This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX.
This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file.
Default: delete readonly = no
When executed, smbd will automatically invoke the delete share command with two parameters.
This parameter is only used to remove file shares. To delete printer shares, see the delete printer command.
See also add share command, change share command.
Default: none
Example: delete share command = /usr/local/bin/delshare
Normally, a Samba server requires that UNIX users are created for all users accessing files on this server. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task. This option allows smbd to delete the required UNIX users ON DEMAND when a user accesses the Samba server and the Windows NT user no longer exists.
In order to use this option, smbd must be set to security = domain or security = user and delete user script must be set to a full pathname for a script that will delete a UNIX user given one argument of %u, which expands into the UNIX user name to delete.
When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time, smbd contacts the password server and attempts to authenticate the given user with the given password. If the authentication fails with the specific Domain error code meaning that the user no longer exists then smbd attempts to find a UNIX user in the UNIX password database that matches the Windows user account. If this lookup succeeds, and delete user script is set then smbd will all the specified script AS ROOT, expanding any %u argument to be the user name to delete.
This script should delete the given UNIX username. In this way, UNIX users are dynamically deleted to match existing Windows NT accounts.
See also security = domain, password server , add user script .
Default: delete user script = <empty string> Example: delete user script = /usr/local/samba/bin/del_user %u
If this option is set to true, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file serving systems such as NetAtalk which create meta-files within directories you might normally veto DOS/Windows users from seeing (e.g. .AppleDouble)
Setting delete veto files = yes allows these directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so).
See also the veto files parameter.
Default: delete veto files = no
This setting allows the replacement of the internal routines to calculate the total disk space and amount available with an external routine. The example below gives a possible script that might fulfill this function.
The external program will be passed a single parameter indicating a directory in the filesystem being queried. This will typically consist of the string ./. The script should return two integers in ASCII. The first should be the total disk space in blocks, and the second should be the number of available blocks. An optional third return value can give the block size in bytes. The default blocksize is 1024 bytes.
Note: Your script should NOT be setuid or setgid and should be owned by (and writeable only by) root!
Default: By default internal routines for determining the disk capacity and remaining space will be used. Example: dfree command = /usr/local/samba/bin/dfree Where the script dfree (which must be made executable) could be:
#!/bin/sh
df $1 | tail -1 | awk '{print $2" "$4}'
or perhaps (on Sys V based systems):
#!/bin/sh
/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
Note that you may have to replace the command names with full path names on some systems.
When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a directory. Any bit not set here will be removed from the modes set on a directory when it is created.
The default value of this parameter removes the 'group' and 'other' write bits from the UNIX mode, allowing only the user who owns the directory to modify it.
Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force directory mode parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).
Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the directory security mask.
See the force directory mode parameter to cause particular mode bits to always be set on created directories.
See also the create mode parameter for masking mode bits on created files, and the directory security mask parameter.
Also refer to the inherit permissions parameter.
Default: directory mask = 0755
Example: directory mask = 0775
This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change.
If not set explicitly this parameter is set to 0777 meaning a user is allowed to modify all the user/group/world permissions on a directory.
Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it as the default of 0777.
See also the force directory security mode, security mask, force security mode parameters.
Default: directory security mask = 0777
Example: directory security mask = 0700
See also use client driver
Default : disable spoolss = no
Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum.
nmbd spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action.
See also the parameter wins support.
Default: dns proxy = yes
See also domain guest group, domain logons
Default: no domain administrators
Example: domain admin group = root @wheel
See also domain admin group, domain logons
Default: no domain guests
Example: domain guest group = nobody @guest
Default: domain logons = no
Note that Windows NT Primary Domain Controllers expect to be able to claim this workgroup specific special NetBIOS name that identifies them as domain master browsers for that workgroup by default (i.e. there is no way to prevent a Windows NT PDC from attempting to do this). This means that if this parameter is set and nmbd claims the special name for a workgroup before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail.
If domain logons = yes , then the default behavior is to enable the domain master parameter. If domain logons is not enabled (the default setting), then neither will domain master be enabled by default.
Default: domain master = auto
Note that Samba can be very fussy about the exact format of the "dont descend" entries. For example you may need ./proc instead of just /proc. Experimentation is the best policy :-)
Default: none (i.e., all directories are OK to descend)
Example: dont descend = /proc,/dev
Default: dos filemode = no
This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. If oplocks are enabled on a share, Visual C++ uses two different time reading calls to check if a file has changed since it was last read. One of these calls uses a one-second granularity, the other uses a two second granularity. As the two second call rounds any odd second down, then if the file has a timestamp of an odd number of seconds then the two timestamps will not match and Visual C++ will keep reporting the file has changed. Setting this option causes the two timestamps to match, and Visual C++ is happy.
Default: dos filetime resolution = no
Default: dos filetimes = no
In order for encrypted passwords to work correctly smbd(8)must either have access to a local smbpasswd(5) program for information on how to set up and maintain this file), or set the security = [server|domain] parameter which causes smbd to authenticate against another server.
Default: encrypt passwords = no
The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs.
You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists. Due to the restrictions of the browse protocols these enhancements can cause a empty workgroup to stay around forever which can be annoying.
In general you should leave this option enabled as it makes cross-subnet browse propagation much more reliable.
Default: enhanced browsing = yes
Default: no enumports command
Example: enumports command = /usr/bin/listports .TP exec (S) This is a synonym for preexec.
This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. Visual C++ generated makefiles have the object directory as a dependency for each object file, and a make rule to create the directory. Also, when NMAKE compares timestamps it uses the creation time when examining a directory. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains.
However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or or deleted in the directory. NMAKE finds all object files in the object directory. The timestamp of the last one built is then compared to the timestamp of the object directory. If the directory's timestamp if newer, then all object files will be rebuilt. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected.
Default: fake directory create times = no
When you set fake oplocks = yes, smbd(8)will always grant oplock requests no matter how many clients are using the file.
It is generally much better to use the real oplocks support rather than this parameter.
If you enable this option on all read-only shares or shares that you know will only be accessed from one client at a time such as physically read-only media like CDROMs, you will see a big performance improvement on many operations. If you enable this option on shares where multiple clients may be accessing the files read-write at the same time you can get data corruption. Use this option carefully!
Default: fake oplocks = no
This option is enabled (i.e. smbd will follow symbolic links) by default.
Default: follow symlinks = yes
See also the parameter create mask for details on masking mode bits on files.
See also the inherit permissions parameter.
Default: force create mode = 000
Example: force create mode = 0755
would force all created files to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'.
See also the parameter directory mask for details on masking mode bits on created directories.
See also the inherit permissions parameter.
Default: force directory mode = 000
Example: force directory mode = 0755
would force all created directories to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'.
This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'.
If not set explicitly this parameter is 000, which allows a user to modify all the user/group/world permissions on a directory without restrictions.
Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it set as 0000.
See also the directory security mask, security mask, force security mode parameters.
Default: force directory security mode = 0
Example: force directory security mode = 700
In Samba 2.0.5 and above this parameter has extended functionality in the following way. If the group name listed here has a '+' character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group. This gives a finer granularity of ownership assignment. For example, the setting force group = +sys means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share. All other users will retain their ordinary primary group.
If the force user parameter is also set the group specified in force group will override the primary group set in force user.
See also force user.
Default: no forced group
Example: force group = agroup
This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.
If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world permissions on a file, with no restrictions.
Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave this set to 0000.
See also the force directory security mode, directory security mask, security mask parameters.
Default: force security mode = 0
Example: force security mode = 700
This is designed to allow Windows NT clients to copy files and folders containing ACLs that were created locally on the client machine and contain users local to that machine only (no domain users) to be copied to a Samba server (usually with XCOPY /O) and have the unknown userid and groupid of the file owner map to the current connected user. This can only be fixed correctly when winbindd allows arbitrary mapping from any Windows NT SID to a UNIX uid or gid.
Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.
See also force group Default: False
Example: force unknown acl user = yes
This user name only gets used once a connection is established. Thus clients still need to connect as a valid user and supply a valid password. Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as. This can be very useful.
In Samba 2.0.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity. Prior to 2.0.5 the primary group was left as the primary group of the connecting user (this was a bug).
See also force group Default: no forced user
Example: force user = auser
Default: fstype = NTFS
Example: fstype = Samba
Default: getwd cache = yes
One some systems the default guest account "nobody" may not be able to print. Use another account in this case. You should test this by trying to log in as your guest user (perhaps by using the su - command) and trying to print using the system print command such as lpr(1) or lp(1).
Default: specified at compile time, usually "nobody"
Example: guest account = ftp
See the section below on security for more information about this option.
Default: guest ok = no
See the section below on security for more information about this option.
Default: guest only = no
Default: hide dot files = yes
Each entry in the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards.
Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator '/'.
Note that the case sensitivity option is applicable in hiding files.
Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned.
See also hide dot files, veto files and case sensitive.
Default: no file are hidden
Example: hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/
The above example is based on files that the Macintosh SMB client (DAVE) available from Thursby <URL:http://www.thursby.com> creates for internal use, and also still hides all files beginning with a dot.
Default: hide local users = no
Default: hide unreadable = no
username server:/some/file/system
and the program will extract the servername from before the first ':'. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps.
NOTE :A working NIS client is required on the system for this option to work.
See also nis homedir , domain logons .
Default: homedir map = <empty string>
Example: homedir map = amd.homedir
See also the msdfs root share level parameter. For more information on setting up a Dfs tree on Samba, refer to msdfs_setup.html.
Default: host msdfs = no
This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service.
If specified in the [global] section then it will apply to all services, regardless of whether the individual service has a different setting.
You can specify the hosts by name or IP number. For example, you could restrict access to only the hosts on a Class C subnet with something like allow hosts = 150.203.5. . The full syntax of the list is described in the man page hosts_access(5). Note that this man page may not be present on your system, so a brief description will be given here also.
Note that the localhost address 127.0.0.1 will always be allowed access unless specifically denied by a hosts deny option.
You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The EXCEPT keyword can also be used to limit a wildcard list. The following examples may provide some help:
Example 1: allow all IPs in 150.203.*.*; except one
hosts allow = 150.203. EXCEPT 150.203.6.66
Example 2: allow hosts that match the given network/netmask
hosts allow = 150.203.15.0/255.255.255.0
Example 3: allow a couple of hosts
hosts allow = lapland, arvidsjaur
Example 4: allow only hosts in NIS netgroup "foonet", but deny access from one particular host
hosts allow = @foonet
hosts deny = pirate
Note that access still requires suitable user-level passwords.
See testparm(1) for a way of testing your host access to see if it does what you expect.
Default: none (i.e., all hosts permitted access) Example: allow hosts = 150.203.5. myhost.mynet.edu.au .TP hosts deny (S) The opposite of hosts allow - hosts listed here are NOT permitted access to services unless the specific services have their own lists to override this one. Where the lists conflict, the allow list takes precedence.
Default: none (i.e., no hosts specifically excluded) Example: hosts deny = 150.203.4. badhost.mynet.edu.au .TP hosts equiv (G) If this global parameter is a non-null string, it specifies the name of a file to read for the names of hosts and users who will be allowed access without specifying a password.
This is not be confused with hosts allow which is about hosts access to services and is more useful for guest services. hosts equiv may be useful for NT clients which will not supply passwords to Samba.
NOTE : The use of hosts equiv can be a major security hole. This is because you are trusting the PC to supply the correct username. It is very easy to get a PC to supply a false username. I recommend that the hosts equiv option be only used if you really know what you are doing, or perhaps on a home network where you trust your spouse and kids. And only if you really trust them :-).
Default: no host equivalences
Example: hosts equiv = /etc/hosts.equiv
It takes the standard substitutions, except %u , %P and %S.
Default: no file included
Example: include = /usr/local/samba/lib/admin_smb.conf .TP inherit acls (S) This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a subdirectory. The default behavior is to use the mode specified when creating the directory. Enabling this option sets the mode to 0777, thus guaranteeing that default directory acls are propagated.
Default: inherit acls = no
New directories inherit the mode of the parent directory, including bits such as setgid.
New files inherit their read/write bits from the parent directory. Their execute bits continue to be determined by map archive , map hidden and map system as usual.
Note that the setuid bit is never set via inheritance (the code explicitly prohibits this).
This can be particularly useful on large systems with many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user.
See also create mask , directory mask, force create mode and force directory mode .
Default: inherit permissions = no
The option takes a list of interface strings. Each string can be in any of the following forms:
The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form.
The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms.
For example, the following line:
interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 .PP
would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0.
See also bind interfaces only.
Default: all active interfaces except 127.0.0.1 that are broadcast capable
A name starting with a '@' is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database.
A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters '+' and '&' may be used at the start of the name in either order so the value +&group means check the UNIX group database, followed by the NIS netgroup database, and the value &+group means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix).
The current servicename is substituted for %S. This is useful in the [homes] section.
See also valid users .
Default: no invalid users
Example: invalid users = root fred admin @wheel .TP keepalive (G) The value of the parameter (an integer) represents the number of seconds between keepalive packets. If this parameter is zero, no keepalive packets will be sent. Keepalive packets, if sent, allow the server to tell whether a client is still present and responding.
Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set on it (see socket options). Basically you should only use this option if you strike difficulties.
Default: keepalive = 300
Example: keepalive = 600
Kernel oplocks support allows Samba oplocks to be broken whenever a local UNIX process or NFS operation accesses a file that smbd(8) has oplocked. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a very cool feature :-).
This parameter defaults to on, but is translated to a no-op on systems that no not have the necessary kernel support. You should never need to touch this parameter.
See also the oplocks and level2 oplocks parameters.
Default: kernel oplocks = yes
Default : lanman auth = yes
Default : large readwrite = no
The ldap admin dn defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information. The ldap admin dn is used in conjunction with the admin dn password stored in the private/secrets.tdb file. See the smbpasswd(8)man page for more information on how to accmplish this.
Default : none
This parameter specifies the RFC 2254 compliant LDAP search filter. The default is to match the login name with the uid attribute for all entries matching the sambaAccount objectclass. Note that this filter should only return one entry.
Default : ldap filter = (&(uid=%u)(objectclass=sambaAccount))
This option is used to control the tcp port number used to contact the ldap server. The default is to use the stand LDAPS port 636.
See Also: ldap ssl
Default : ldap port = 636 ; if ldap ssl = on
Default : ldap port = 389 ; if ldap ssl = off
This parameter should contains the FQDN of the ldap directory server which should be queried to locate user account information.
Default : ldap server = localhost
This option is used to define whether or not Samba should use SSL when connecting to the ldap server. This is NOT related to Samba SSL support which is enabled by specifying the --with-ssl option to the configure script (see ssl).
The ldap ssl can be set to one of three values: (a) on - Always use SSL when contacting the ldap server, (b) off - Never use SSL when querying the directory, or (c) start_tls - Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server.
Default : ldap ssl = on
Default : none
Level2, or read-only oplocks allow Windows NT clients that have an oplock on a file to downgrade from a read-write oplock to a read-only oplock once a second client opens the file (instead of releasing all oplocks on a second open, as in traditional, exclusive oplocks). This allows all openers of the file that support level2 oplocks to cache the file for read-ahead only (ie. they may not cache writes or lock requests) and increases performance for many accesses of files that are not commonly written (such as application .EXE files).
Once one of the clients which have a read-only oplock writes to the file all clients are notified (no reply is needed or waited for) and told to break their oplocks to "none" and delete any read-ahead caches.
It is recommended that this parameter be turned on to speed access to shared executables.
For more discussions on level2 oplocks see the CIFS spec.
Currently, if kernel oplocks are supported then level2 oplocks are not granted (even if this parameter is set to yes). Note also, the oplocks parameter must be set to true on this share in order for this parameter to have any effect.
See also the oplocks and kernel oplocks parameters.
Default: level2 oplocks = yes
See also lm interval .
Default: lm announce = auto
Example: lm announce = yes
See also lm announce.
Default: lm interval = 60
Example: lm interval = 120
Default: load printers = yes
Setting this value to false will cause nmbd never to become a local master browser.
Default: local master = yes
Default: lock directory = ${prefix}/var/locks
Example: lock directory = /var/run/samba/locks
Default: lock spin count = 2
Default: lock spin time = 10
If locking = no, all lock and unlock requests will appear to succeed and all lock queries will report that the file in question is available for locking.
If locking = yes, real locking will be performed by the server.
This option may be useful for read-only filesystems which may not need locking (such as CDROM drives), although setting this parameter of no is not really recommended even in this case.
Be careful about disabling locking either globally or in a specific service, as lack of locking may result in data corruption. You should never need to set this parameter.
Default: locking = yes
This option takes the standard substitutions, allowing you to have separate log files for each user or machine.
Example: log file = /usr/local/samba/var/log.%m .TP log level (G) The value of the parameter (an integer) allows the debug level (logging level) to be specified in the smb.conf file. This is to give greater flexibility in the configuration of the system.
The default will be the log level specified on the command line or level zero if none was specified.
Example: log level = 3
Note that this option is only useful if Samba is set up as a logon server.
Default: logon drive = z:
Example: logon drive = h:
C:\> NET USE H: /HOME
from a command prompt, for example.
This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user's home directory. This is done in the following way:
logon home = \\%N\%U\profile
This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request. Win9X clients truncate the info to \\server\share when a user does net use /home but use the whole string when dealing with profiles.
Note that in prior versions of Samba, the logon path was returned rather than logon home. This broke net use /home but allowed profiles outside the home directory. The current implementation is correct, and can be used for profiles if you use the above trick.
This option is only useful if Samba is set up as a logon server.
Default: logon home = "\\%N\%U"
Example: logon home = "\\remote_smb_server\%U"
This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. It also specifies the directory from which the "Application Data", (desktop, start menu, network neighborhood, programs and other folders, and their contents, are loaded and displayed on your Windows NT client.
The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories.
Thereafter, the directories and any of the contents can, if required, be made read-only. It is not advisable that the NTuser.dat file be made read-only - rename it to NTuser.man to achieve the desired effect (a MANdatory profile).
Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in. Therefore, it is vital that the logon path does not include a reference to the homes share (i.e. setting this parameter to \%N\%U\profile_path will cause problems).
This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
Note that this option is only useful if Samba is set up as a logon server.
Default: logon path = \\%N\%U\profile
Example: logon path = \\PROFILESERVER\PROFILE\%U
The script must be a relative path to the [netlogon] service. If the [netlogon] service specifies a path of /usr/local/samba/netlogon , and logon script = STARTUP.BAT, then the file that will be downloaded is:
/usr/local/samba/netlogon/STARTUP.BAT
The contents of the batch file are entirely your choice. A suggested command would be to add NET TIME \\SERVER /SET /YES, to force every machine to synchronize clocks with the same time server. Another use would be to add NET USE U: \\SERVER\UTILS for commonly used utilities, or NET USE Q: \\SERVER\ISO9001_QA for example.
Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached.
This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
This option is only useful if Samba is set up as a logon server.
Default: no logon script defined
Example: logon script = scripts\%U.bat
This command should be a program or script which takes a printer name and job number to pause the print job. One way of implementing this is by using job priorities, where jobs having a too low priority won't be sent to the printer.
If a %p is given then the printer name is put in its place. A %j is replaced with the job number (an integer). On HPUX (see printing=hpux ), if the -p%p option is added to the lpq command, the job will show up with the correct status, i.e. if the job priority is lower than the set fence priority it will have the PAUSED status, whereas if the priority is equal or higher it will have the SPOOLED or PRINTING status.
Note that it is good practice to include the absolute path in the lppause command as the PATH may not be available to the server.
See also the printing parameter.
Default: Currently no default value is given to this string, unless the value of the printing parameter is SYSV, in which case the default is :
lp -i %p-%j -H hold
or if the value of the printing parameter is SOFTQ, then the default is:
qstat -s -j%j -h
Example for HPUX: lppause command = /usr/bin/lpalt %p-%j -p0
The cache files are stored in /tmp/lpq.xxxx where xxxx is a hash of the lpq command in use.
The default is 10 seconds, meaning that the cached results of a previous identical lpq command will be used if the cached data is less than 10 seconds old. A large value may be advisable if your lpq command is very slow.
A value of 0 will disable caching completely.
See also the printing parameter.
Default: lpq cache time = 10
Example: lpq cache time = 30
This command should be a program or script which takes a printer name as its only parameter and outputs printer status information.
Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. This covers most UNIX systems. You control which type is expected using the printing = option.
Some clients (notably Windows for Workgroups) may not correctly send the connection number for the printer they are requesting status information about. To get around this, the server reports on the first printer service connected to by the client. This only happens if the connection number sent is invalid.
If a %p is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
Note that it is good practice to include the absolute path in the lpq command as the $PATH may not be available to the server. When compiled with the CUPS libraries, no lpq command is needed because smbd will make a library call to obtain the print queue listing.
See also the printing parameter.
Default: depends on the setting of printing
Example: lpq command = /usr/bin/lpq -P%p
This command should be a program or script which takes a printer name and job number to resume the print job. See also the lppause command parameter.
If a %p is given then the printer name is put in its place. A %j is replaced with the job number (an integer).
Note that it is good practice to include the absolute path in the lpresume command as the PATH may not be available to the server.
See also the printing parameter.
Default: Currently no default value is given to this string, unless the value of the printing parameter is SYSV, in which case the default is :
lp -i %p-%j -H resume
or if the value of the printing parameter is SOFTQ, then the default is:
qstat -s -j%j -r
Example for HPUX: lpresume command = /usr/bin/lpalt %p-%j -p2
This command should be a program or script which takes a printer name and job number, and deletes the print job.
If a %p is given then the printer name is put in its place. A %j is replaced with the job number (an integer).
Note that it is good practice to include the absolute path in the lprm command as the PATH may not be available to the server.
See also the printing parameter.
Default: depends on the setting of printing Example 1: lprm command = /usr/bin/lprm -P%p %j Example 2: lprm command = /usr/bin/cancel %p-%j .TP machine password timeout (G) If a Samba server is a member of a Windows NT Domain (see the security = domain) parameter) then periodically a running smbd(8)process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called private/secrets.tdb . This parameter specifies how often this password will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.
See also smbpasswd(8) , and the security = domain) parameter.
Default: machine password timeout = 604800
Warning: If two clients use the same magic script in the same directory the output file content is undefined.
Default: magic output = <magic script name>.out Example: magic output = myfile.txt
Scripts executed in this way will be deleted upon completion assuming that the user has the appropriate level of privilege and the file permissions allow the deletion.
If the script generates output, output will be sent to the file specified by the magic output parameter (see above).
Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker. Magic scripts must be executable as is on the host, which for some hosts and some shells will require filtering at the DOS end.
Magic scripts are EXPERIMENTAL and should NOT be relied upon.
Default: None. Magic scripts disabled.
Example: magic script = user.csh
Default: mangle case = no
So to map html to htm you would use:
mangled map = (*.html *.htm)
One very useful case is to remove the annoying ;1 off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).
Default: no mangled map
Example: mangled map = (*;1 *;)
See the section on NAME MANGLING for details on how to control the mangling process.
If mangling algorithm "hash" is used then the mangling algorithm is as follows:
Note that the character to use may be specified using the mangling char option, if you don't like '~'.
The two-digit hash value consists of upper case alphanumeric characters.
This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters. The probability of such a clash is 1/1300.
If mangling algorithm "hash2" is used then the mangling algorithm is as follows:
Note that the character to use may be specified using the mangling char option, if you don't like '~'.
The name mangling (if enabled) allows a file to be copied between UNIX directories from Windows/DOS while retaining the long UNIX filename. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename. Mangled names do not change between sessions.
Default: mangled names = yes
This stack is a list of recently mangled base names (extensions are only maintained if they are longer than 3 characters or contains upper case characters).
The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names. However, large stack sizes will slow most directory accesses. Smaller stacks save memory in the server (each stack element costs 256 bytes).
It is not possible to absolutely guarantee correct long filenames, so be prepared for some surprises!
Default: mangled stack = 50
Example: mangled stack = 100
Default: mangling char = ~
Example: mangling char = ^
Default: mangling method = hash
Example: mangling method = hash2
Note that this requires the create mask parameter to be set such that owner execute bit is not masked out (i.e. it must include 100). See the parameter create mask for details.
Default: map archive = yes
Note that this requires the create mask to be set such that the world execute bit is not masked out (i.e. it must include 001). See the parameter create mask for details.
Default: map hidden = no
Note that this requires the create mask to be set such that the group execute bit is not masked out (i.e. it must include 010). See the parameter create mask for details.
Default: map system = no
This parameter can take three different values, which tell smbd(8)what to do with user login requests that don't match a valid UNIX user in some way.
The three settings are :
Note that this parameter is needed to set up "Guest" share services when using security modes other than share. This is because in these modes the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for "Guest" shares.
For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the GUEST_SESSSETUP value in local.h.
Default: map to guest = Never
Example: map to guest = Bad User
Record lock files are used to implement this feature. The lock files will be stored in the directory specified by the lock directory option.
Default: max connections = 0
Example: max connections = 10
Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.
This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.
A max disk size of 0 means no limit.
Default: max disk size = 0
Example: max disk size = 1000
A size of 0 means no limit.
Default: max log size = 5000
Example: max log size = 1000
Default: max mux = 50
The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter.
Default: max open files = 10000
Default: max print jobs = 1000
Example: max print jobs = 5000
Possible values are :
Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.
See also min protocol
Default: max protocol = NT1
Example: max protocol = LANMAN1
Default: max smbd processes = 0 ## no limit
Example: max smbd processes = 1000
Default: max ttl = 259200
See also the min wins ttl parameter.
Default: max wins ttl = 518400
Default: max xmit = 65535
Example: max xmit = 8192
This would normally be a command that would deliver the message somehow. How this is to be done is up to your imagination.
An example is:
message command = csh -c 'xedit %s;rm %s' &
This delivers the message using xedit, then removes it afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).
All messages are delivered as the global guest user. The command takes the standard substitutions, although %u won't work (%U may be better in this case).
Apart from the standard substitutions, some additional ones apply. In particular:
You could make this command send mail, or whatever else takes your fancy. Please let us know of any really interesting ideas you have.
Here's a way of sending the messages as mail to root:
message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
If you don't have a message command then the message won't be delivered and Samba will tell the sender there was an error. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered.
If you want to silently delete it then try:
message command = rm %s
Default: no message command
Example: message command = csh -c 'xedit %s; rm %s' &
See also unix password sync, passwd program and passwd chat debug .
Default: min password length = 5
See also the printing parameter.
Default: min print space = 0
Example: min print space = 2000
If you are viewing this parameter as a security measure, you should also refer to the lanman auth parameter. Otherwise, you should never need to change this parameter.
Default : min protocol = CORE
Example : min protocol = NT1 # disable DOS clients
Default: min wins ttl = 21600
See also host msdfs Default: msdfs root = no
The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :
Default: name resolve order = lmhosts host wins bcast .PP
Example: name resolve order = lmhosts bcast host .PP
This will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup.
See also netbios name.
Default: empty string (no additional names)
Example: netbios aliases = TEST TEST1 TEST2
See also netbios aliases.
Default: machine DNS name
Example: netbios name = MYNAME
When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS). This can be very slow.
This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server. When Samba is returning the home share to the client, it will consult the NIS map specified in homedir map and return the server listed there.
Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server.
Default: nis homedir = no
Default: nt acl support = yes
Default: nt pipe support = yes
You should not need to ever disable this parameter.
Default: nt smb support = yes
You should not need to ever disable this parameter.
Default: nt status support = yes
See also smbpasswd (5).
Default: null passwords = no
Default: obey pam restrictions = no
Note that this also means Samba won't try to deduce usernames from the service name. This can be annoying for the [homes] section. To get around this you could use user = %S which means your user list will be just the service name, which for home directories is the name of the user.
See also the user parameter.
Default: only user = no
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
Default: oplock break wait time = 0
In brief it specifies a number, which causes smbdnot to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes smbd to behave in a similar way to Windows NT.
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
Default: oplock contention limit = 2
Oplocks may be selectively turned off on certain files with a share. See the veto oplock files parameter. On some systems oplocks are recognized by the underlying operating system. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process. See the kernel oplocks parameter for details.
See also the kernel oplocks and level2 oplocks parameters.
Default: oplocks = yes
Note :By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes. See BROWSING.txt in the Samba docs/ directory for details.
Default: os level = 20
Example: os level = 65
<nt driver name> = <os2 driver name>.<device name>
For example, a valid entry using the HP LaserJet 5 printer driver would appear as HP LaserJet 5L = LASERJET.HP LaserJet 5L.
The need for the file is due to the printer driver namespace problem described in the Samba Printing HOWTO. For more details on OS/2 clients, please refer to the OS2-Client-HOWTO containing in the Samba documentation.
Default: os2 driver map = <empty string> .TP pam password change (G) With the addition of better PAM support in Samba 2.2, this parameter, it is possible to use PAM's password change control flag for Samba. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in passwd program. It should be possible to enable this without changing your passwd chat parameter for most setups.
Default: pam password change = no
Default: panic action = <empty string>
Example: panic action = "/bin/sleep 90000"
This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc).
Note that this parameter only is only used if the unix password sync parameter is set to yes. This sequence is then called AS ROOT when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext. This means that root must be able to reset the user's password without knowing the text of the previous password. In the presence of NIS/YP, this means that the passwd program must be executed on the NIS master.
The string can contain the macro %n which is substituted for the new password. The chat sequence can also contain the standard macros \n, \r, \t and \s to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces in them into a single string.
If the send string in any part of the chat sequence is a full stop ".", then no string is sent. Similarly, if the expect string is a full stop then no string is expected.
If the pam password change parameter is set to true, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output. The \n macro is ignored for PAM conversions.
See also unix password sync, passwd program , passwd chat debug and pam password change.
Default: passwd chat = *new*password* %n\n *new*password* %n\n *changed*
Example: passwd chat = "*Enter OLD password*" %o\n "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"
See also passwd chat , pam password change , passwd program .
Default: passwd chat debug = no
Also note that many passwd programs insist in reasonable passwords, such as a minimum length, or the inclusion of mixed case chars and digits. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it.
Note that if the unix password sync parameter is set to true then this program is called AS ROOT before the SMB password in the smbpasswd(5) file is changed. If this UNIX password change fails, then smbd will fail to change the SMB password also (this is by design).
If the unix password sync parameter is set this parameter MUST USE ABSOLUTE PATHS for ALL programs called, and must be examined for security implications. Note that by default unix password sync is set to false.
See also unix password sync.
Default: passwd program = /bin/passwd
Example: passwd program = /sbin/npasswd %u
This parameter defines the maximum number of characters that may be upper case in passwords.
For example, say the password given was "FRED". If password level is set to 1, the following combinations would be tried if "FRED" failed:
"Fred", "fred", "fRed", "frEd","freD"
If password level was set to 2, the following combinations would also be tried:
"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..
And so on.
The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection.
A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case.
Default: password level = 0
Example: password level = 4
This option sets the name of the password server to use. It must be a NetBIOS name, so if the machine's NetBIOS name is different from its Internet name then you may have to add its NetBIOS name to the lmhosts file which is stored in the same directory as the smb.conf file.
The name of the password server is looked up using the parameter name resolve order and so may resolved by any method and order described in that parameter.
The password server much be a machine capable of using the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.
NOTE: Using a password server means your UNIX box (running Samba) is only as secure as your password server. DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST.
Never point a Samba server at itself for password serving. This will cause a loop and could lock up your Samba server!
The name of the password server takes the standard substitutions, but probably the only useful one is %m , which means the Samba server will use the incoming client as the password server. If you use this then you better trust your clients, and you had better restrict them with hosts allow!
If the security parameter is set to domain, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character '*', as the Samba server is effectively in that domain, and will use cryptographically authenticated RPC calls to authenticate the user logging on. The advantage of using security = domain is that if you list several hosts in the password server option then smbd will try each in turn till it finds one that responds. This is useful in case your primary server goes down.
If the password server option is set to the character '*', then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name WORKGROUP<1C> and then contacting each server returned in the list of IP addresses from the name resolution source.
If the security parameter is set to server, then there are different restrictions that security = domain doesn't suffer from:
See also the security parameter.
Default: password server = <empty string>
Example: password server = NT-PDC, NT-BDC1, NT-BDC2 .PP
Example: password server = *
For a printable service offering guest access, the service should be readonly and the path should be world-writeable and have the sticky bit set. This is not mandatory of course, but you probably won't get the results you expect if you do otherwise.
Any occurrences of %u in the path will be replaced with the UNIX username that the client is using on this connection. Any occurrences of %m will be replaced by the NetBIOS name of the machine they are connecting from. These replacements are very useful for setting up pseudo home directories for users.
Note that this path will be based on root dir if one was specified.
Default: none
Example: path = /home/fred
Default: pid directory = ${prefix}/var/locks
Example: pid directory = /var/run/
Default: posix locking = yes
An interesting example may be to unmount server resources:
postexec = /etc/umount /cdrom
See also preexec .
Default: none (no command executed)
Example: postexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log
This is most useful when you have lots of PCs that persist in putting a control-D at the start of print jobs, which then confuses your printer.
Default: postscript = no
An interesting example is to send the users a welcome message every time they log in. Maybe a message of the day? Here is an example:
preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &
Of course, this could get annoying after a while :-)
See also preexec close and postexec .
Default: none (no command executed)
Example: preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log
Default: preexec close = no
If this is set to true, on startup, nmbd will force an election, and it will have a slight advantage in winning the election. It is recommended that this parameter is used in conjunction with domain master = yes, so that nmbd can guarantee becoming a domain master.
Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser. This will result in unnecessary broadcast traffic and reduced browsing capabilities.
See also os level .
Default: preferred master = auto
Note that if you just want all printers in your printcap file loaded then the load printers option is easier.
Default: no preloaded services
Example: preload = fred lp colorlp
Default: preserve case = yes
See the section on NAME MANGLING for a fuller discussion.
The print command is simply a text string. It will be used verbatim after macro substitutions have been made:
s, %p - the path to the spool file name
%p - the appropriate printer name
%J - the job name as transmitted by the client.
%c - The number of printed pages of the spooled job (if known).
%z - the size of the spooled print job (in bytes)
The print command MUST contain at least one occurrence of %s or %f - the %p is optional. At the time a job is submitted, if no printer name is supplied the %p will be silently removed from the printer command.
If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified.
If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed and (most importantly) not removed.
Note that printing may fail on some UNIXes from the nobody account. If this happens then create an alternative guest account that can print and set the guest account in the [global] section.
You can form quite complex print commands by realizing that they are just passed to a shell. For example the following will log a print job, print the file, then remove it. Note that ';' is the usual separator for command in shell scripts.
print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s
You may have to vary this command considerably depending on how you normally print files on your system. The default for the parameter varies depending on the setting of the printing parameter.
Default: For printing = BSD, AIX, QNX, LPRNG or PLP :
print command = lpr -r -P%p %s
For printing = SYSV or HPUX :
print command = lp -c -d%p %s; rm %s
For printing = SOFTQ :
print command = lp -d%p -s %s; rm %s
For printing = CUPS : If SAMBA is compiled against libcups, then printcap = cups uses the CUPS API to submit jobs, etc. Otherwise it maps to the System V commands with the -oraw option for printing, i.e. it uses lp -c -d%p -oraw; rm %s. With printing = cups, and if SAMBA is compiled against libcups, any manually set print command will be ignored.
Example: print command = /usr/local/samba/bin/myprintscript %p %s
Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data. The writeable parameter controls only non-printing access to the resource.
Default: printable = no
To use the CUPS printing interface set printcap name = cups . This should be supplemented by an addtional setting printing = cups in the [global] section. printcap name = cups will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file.
On System V systems that use lpstat to list available printers you can use printcap name = lpstat to automatically obtain lists of available printers. This is the default for systems that define SYSV at configure time in Samba (this includes most System V based systems). If printcap name is set to lpstat on these systems then Samba will launch lpstat -v and attempt to parse the output to obtain a printer list.
A minimal printcap file would look something like this:
print1|My Printer 1
print2|My Printer 2
print3|My Printer 3
print4|My Printer 4
print5|My Printer 5
where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba that it's a comment.
NOTE: Under AIX the default printcap name is /etc/qconfig. Samba will assume the file is in AIX qconfig format if the string qconfig appears in the printcap filename.
Default: printcap name = /etc/printcap
Example: printcap name = /etc/myprintcap
Default: printer admin = <empty string>
Example: printer admin = admin, @staff
This option allows you to control the string that clients receive when they ask the server for the printer driver associated with a printer. If you are using Windows95 or Windows NT then you can use this to automate the setup of printers on your system.
You need to set this parameter to the exact string (case sensitive) that describes the appropriate printer driver for your system. If you don't know the exact string to use then you should first try with no printer driver option set and the client will give you a list of printer drivers. The appropriate strings are shown in a scroll box after you have chosen the printer manufacturer.
See also printer driver file.
Example: printer driver = HP LaserJet 4L
This parameter tells Samba where the printer driver definition file, used when serving drivers to Windows 95 clients, is to be found. If this is not set, the default is :
SAMBA_INSTALL_DIRECTORY /lib/printers.def
This file is created from Windows 95 msprint.inf files found on the Windows 95 client system. For more details on setting up serving of printer drivers to Windows 95 clients, see the outdated documentation file in the docs/ directory, PRINTER_DRIVER.txt.
See also printer driver location.
Default: None (set in compile).
Example: printer driver file = /usr/local/samba/printers/drivers.def
This parameter tells clients of a particular printer share where to find the printer driver files for the automatic installation of drivers for Windows 95 machines. If Samba is set up to serve printer drivers to Windows 95 machines, this should be set to
\\MACHINE\PRINTER$
Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$ is a share you set up for serving printer driver files. For more details on setting this up see the outdated documentation file in the docs/ directory, PRINTER_DRIVER.txt.
See also printer driver file.
Default: none
Example: printer driver location = \\MACHINE\PRINTER$ .TP printer name (S) This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent.
If specified in the [global] section, the printer name given will be used for any printable service that does not have its own printer name specified.
Default: none (but may be lp on many systems)
Example: printer name = laserwriter
Currently nine printing styles are supported. They are BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, SOFTQ, and CUPS.
To see what the defaults are for the other print commands when using the various options use the testparm(1)program.
This option can be set on a per printer basis
See also the discussion in the [printers] section.
This command should be a program or script which takes a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.
This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT.
If a %p is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server.
Default: depends on the setting of printing Example: queuepause command = disable %p
This command should be a program or script which takes a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer.
This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT.
If a %p is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server.
Default: depends on the setting of printing
Example: queuepause command = enable %p .TP read bmpx (G) This boolean parameter controls whether smbd(8)will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to no. You should never need to set this parameter.
Default: read bmpx = no
See also the write list parameter and the invalid users parameter.
Default: read list = <empty string>
Example: read list = mary, @students
If enabled, raw reads allow reads of 65535 bytes in one packet. This typically provides a major performance benefit.
However, some clients either negotiate the allowable block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads.
In general this parameter should be viewed as a system tuning tool and left severely alone. See also write raw.
Default: read raw = yes
This overlapping works best when the speeds of disk and network access are similar, having very little effect when the speed of one is much greater than the other.
The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is pointless and will cause you to allocate memory unnecessarily.
Default: read size = 16384
Example: read size = 8192
This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
For example:
remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
the above line would cause nmbd to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name then the one given in the workgroup parameter is used instead.
The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable.
See the documentation file BROWSING.txt in the docs/ directory.
Default: remote announce = <empty string> .TP remote browse sync (G) This option allows you to setup nmbd(8)to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This is done in a manner that does not work with any non-Samba servers.
This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
For example:
remote browse sync = 192.168.2.255 192.168.4.255 the above line would cause nmbd to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server.
The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment.
Default: remote browse sync = <empty string> .TP restrict anonymous (G) This is a boolean parameter. If it is true, then anonymous access to the server will be restricted, namely in the case where the server is expecting the client to send a username, but it doesn't. Setting it to true will force these anonymous connections to be denied, and the client will be required to always supply a username and password when connecting. Use of this parameter is only recommended for homogeneous NT client environments.
This parameter makes the use of macro expansions that rely on the username (%U, %G, etc) consistent. NT 4.0 likes to use anonymous connections when refreshing the share list, and this is a way to work around that.
When restrict anonymous is true, all anonymous connections are denied no matter what they are for. This can effect the ability of a machine to access the Samba Primary Domain Controller to revalidate its machine account after someone else has logged on the client interactively. The NT client will display a message saying that the machine's account in the domain doesn't exist or the password is bad. The best way to deal with this is to reboot NT client machines between interactive logons, using "Shutdown and Restart", rather than "Close all programs and logon as a different user".
Default: restrict anonymous = no
Adding a root directory entry other than "/" adds an extra level of security, but at a price. It absolutely ensures that no access is given to files not in the sub-tree specified in the root directory option, including some files needed for complete operation of the server. To maintain full operability of the server you will need to mirror some system files into the root directory tree. In particular you will need to mirror /etc/passwd (or a subset of it), and any binaries or configuration files needed for printing (if required). The set of files that must be mirrored is operating system dependent.
Default: root directory = /
Example: root directory = /homes/smb
See also postexec.
Default: root postexec = <empty string> .TP root preexec (S) This is the same as the preexec parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a connection is opened.
See also preexec and preexec close.
Default: root preexec = <empty string> .TP root preexec close (S) This is the same as the preexec close parameter except that the command is run as root.
See also preexec and preexec close.
Default: root preexec close = no
The option sets the "security mode bit" in replies to protocol negotiations with smbd(8) to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.
The default is security = user, as this is the most common setting needed when talking to Windows 98 and Windows NT.
The alternatives are security = share, security = server or security = domain .
In versions of Samba prior to 2.0.0, the default was security = share mainly because that was the only option at one stage.
There is a bug in WfWg that has relevance to this setting. When in user or server level security a WfWg client will totally ignore the password you type in the "connect drive" dialog box. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as.
If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use security = user. If you mostly use usernames that don't exist on the UNIX box then use security = share.
You should also use security = share if you want to mainly setup shares without a password (guest shares). This is commonly used for a shared printer server. It is more difficult to setup guest shares with security = user, see the map to guest parameter for details.
It is possible to use smbd in a hybrid mode where it is offers both user and share level security under different NetBIOS aliases.
The different settings will now be explained.
SECURITY = SHARE When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a security = share server). Instead, the clients send authentication information (passwords) on a per-share basis, at the time they attempt to connect to that share.
Note that smbd ALWAYS uses a valid UNIX user to act on behalf of the client, even in security = share level security.
As clients are not required to send a username to the server in share level security, smbd uses several techniques to determine the correct UNIX user to use on behalf of the client.
A list of possible UNIX usernames to match with the given client password is constructed using the following methods :
If the guest only parameter is not set, then this list is then tried with the supplied password. The first user for whom the password matches will be used as the UNIX user.
If the guest only parameter is set, or no username can be determined then if the share is marked as available to the guest account, then this guest user will be used, otherwise access is denied.
Note that it can be very confusing in share-level security as to which UNIX username will eventually be used in granting access.
See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
SECURITY = USER .PP
This is the default security setting in Samba 2.2. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the username map parameter). Encrypted passwords (see the encrypted passwords parameter) can also be used in this security mode. Parameters such as user and guest only if set are then applied and may change the UNIX user to use on this connection, but only after the user has been successfully authenticated.
Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the guest account. See the map to guest parameter for details on doing this.
See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
SECURITY = SERVER .PP
In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box. If this fails it will revert to security = user, but note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid smbpasswd file to check users against. See the documentation file in the docs/ directory ENCRYPTION.txt for details on how to set this up.
Note that from the client's point of view security = server is the same as security = user. It only affects how the server deals with the authentication, it does not in any way affect what the client sees.
Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the guest account. See the map to guest parameter for details on doing this.
See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
See also the password server parameter and the encrypted passwords parameter.
SECURITY = DOMAIN .PP
This mode will only work correctly if smbpasswd(8)has been used to add this machine into a Windows NT Domain. It expects the encrypted passwords parameter to be set to true. In this mode Samba will try to validate the username/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do.
Note that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to.
Note that from the client's point of view security = domain is the same as security = user . It only affects how the server deals with the authentication, it does not in any way affect what the client sees.
Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the guest account. See the map to guest parameter for details on doing this.
BUG: There is currently a bug in the implementation of security = domain with respect to multi-byte character set usernames. The communication with a Domain Controller must be done in UNICODE and Samba currently does not widen multi-byte user names to UNICODE correctly, thus a multi-byte username will not be recognized correctly at the Domain Controller. This issue will be addressed in a future release.
See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
See also the password server parameter and the encrypted passwords parameter.
Default: security = USER
Example: security = DOMAIN
This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change.
If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file.
Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it set to 0777.
See also the force directory security mode, directory security mask, force security mode parameters.
Default: security mask = 0777
Example: security mask = 0770
It also sets what will appear in browse lists next to the machine name.
A %v will be replaced with the Samba version number.
A %h will be replaced with the hostname.
Default: server string = Samba %v
Example: server string = University of GNUs Samba Server
The setdir command is only implemented in the Digital Pathworks client. See the Pathworks documentation for details.
Default: set directory = no
These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared memory (almost all do).
The share modes that are enabled by this option are DENY_DOS, DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
This option gives full share compatibility and enabled by default.
You should NEVER turn this parameter off as many Windows applications will break if you do so.
Default: share modes = yes
See the section on NAME MANGLING.
Default: short preserve case = yes
Under normal circumstances, the Windows NT/2000 client will open a handle on the printer server with OpenPrinterEx() asking for Administrator privileges. If the user does not have administrative access on the print server (i.e is not root or a member of the printer admin group), the OpenPrinterEx() call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.
Disabling the show add printer wizard parameter will always cause the OpenPrinterEx() on the server to fail. Thus the APW icon will never be displayed. Note :This does not prevent the same user from having administrative privilege on an individual printer.
See also addprinter command, deleteprinter command, printer admin
Default :show add printer wizard = yes
Default: smb passwd file = ${prefix}/private/smbpasswd Example: smb passwd file = /etc/samba/smbpasswd .TP socket address (G) This option allows you to control what address Samba will listen for connections on. This is used to support multiple virtual interfaces on the one server, each with a different configuration.
By default Samba will accept connections on any address.
Example: socket address = 192.168.2.20
Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned.
This option will typically be used to tune your Samba server for optimal performance for your local network. There is no way that Samba can know what the optimal parameters are for your net, so you must experiment and choose them yourself. We strongly suggest you read the appropriate documentation for your operating system first (perhaps man setsockopt will help).
You may find that on some systems Samba will say "Unknown socket option" when you supply an option. This means you either incorrectly typed it or you need to add an include file to includes.h for your OS. If the latter is the case please send the patch to samba@samba.org <URL:mailto:samba@samba.org>.
Any of the supported socket options may be combined in any way you like, as long as your OS allows it.
This is the list of socket options currently settable using this option:
Those marked with a '*' take an integer argument. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don't specify 1 or 0.
To specify an argument use the syntax SOME_OPTION = VALUE for example SO_SNDBUF = 8192. Note that you must not have any spaces before or after the = sign.
If you are on a local network then a sensible option might be
socket options = IPTOS_LOWDELAY
If you have a local network then you could try:
socket options = IPTOS_LOWDELAY TCP_NODELAY
If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT.
Note that several of the options may cause your Samba server to fail completely. Use these options with caution!
Default: socket options = TCP_NODELAY
Example: socket options = IPTOS_LOWDELAY
If the value of this parameter starts with a "|" character then Samba will treat that value as a pipe command to open and will set the environment variables from the output of the pipe.
The contents of the file or the output of the pipe should be formatted as the output of the standard Unix env(1) command. This is of the form :
Example environment entry:
SAMBA_NETBIOS_NAME = myhostname
Default: No default value
Examples: source environment = |/etc/smb.conf.sh Example: source environment = /usr/local/smb_env_vars
This variable enables or disables the entire SSL mode. If it is set to no, the SSL-enabled Samba behaves exactly like the non-SSL Samba. If set to yes, it depends on the variables ssl hosts and ssl hosts resign whether an SSL connection will be required.
Default: ssl = no
This variable defines where to look up the Certification Authorities. The given directory should contain one file for each CA that Samba will trust. The file name must be the hash value over the "Distinguished Name" of the CA. How this directory is set up is explained later in this document. All files within the directory that don't fit into this naming scheme are ignored. You don't need this variable if you don't verify client certificates.
Default: ssl CA certDir = /usr/local/ssl/certs .TP ssl CA certFile (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This variable is a second way to define the trusted CAs. The certificates of the trusted CAs are collected in one big file and this variable points to the file. You will probably only use one of the two ways to define your CAs. The first choice is preferable if you have many CAs or want to be flexible, the second is preferable if you only have one CA and want to keep things simple (you won't need to create the hashed file names). You don't need this variable if you don't verify client certificates.
Default: ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem .TP ssl ciphers (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This variable defines the ciphers that should be offered during SSL negotiation. You should not set this variable unless you know what you are doing.
The certificate in this file is used by smbclient(1)if it exists. It's needed if the server requires a client certificate.
Default: ssl client cert = /usr/local/ssl/certs/smbclient.pem .TP ssl client key (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This is the private key for smbclient(1). It's only needed if the client should have a certificate.
Default: ssl client key = /usr/local/ssl/private/smbclient.pem .TP ssl compatibility (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This variable defines whether OpenSSL should be configured for bug compatibility with other SSL implementations. This is probably not desirable because currently no clients with SSL implementations other than OpenSSL exist.
Default: ssl compatibility = no
This option is used to define the location of the communiation socket of an EGD or PRNGD daemon, from which entropy can be retrieved. This option can be used instead of or together with the ssl entropy file directive. 255 bytes of entropy will be retrieved from the daemon.
Default: none
This parameter is used to define the number of bytes which should be read from the ssl entropy file If a -1 is specified, the entire file will be read.
Default: ssl entropy bytes = 255
This parameter is used to specify a file from which processes will read "random bytes" on startup. In order to seed the internal pseudo random number generator, entropy must be provided. On system with a /dev/urandom device file, the processes will retrieve its entropy from the kernel. On systems without kernel entropy support, a file can be supplied that will be read on startup and that will be used to seed the PRNG.
Default: none
These two variables define whether Samba will go into SSL mode or not. If none of them is defined, Samba will allow only SSL connections. If the ssl hosts variable lists hosts (by IP-address, IP-address range, net group or name), only these hosts will be forced into SSL mode. If the ssl hosts resign variable lists hosts, only these hosts will NOT be forced into SSL mode. The syntax for these two variables is the same as for the hosts allow and hosts deny pair of variables, only that the subject of the decision is different: It's not the access right but whether SSL is used or not.
The example below requires SSL connections from all hosts outside the local net (which is 192.168.*.*).
Default: ssl hosts = <empty string>
ssl hosts resign = <empty string>
Example: ssl hosts resign = 192.168.
If this variable is set to yes, the server will not tolerate connections from clients that don't have a valid certificate. The directory/file given in ssl CA certDir and ssl CA certFile will be used to look up the CAs that issued the client's certificate. If the certificate can't be verified positively, the connection will be terminated. If this variable is set to no, clients don't need certificates. Contrary to web applications you really should require client certificates. In the web environment the client's data is sensitive (credit card numbers) and the server must prove to be trustworthy. In a file server environment the server's data will be sensitive and the clients must prove to be trustworthy.
Default: ssl require clientcert = no
If this variable is set to yes, the smbclient(1) will request a certificate from the server. Same as ssl require clientcert for the server.
Default: ssl require servercert = no
This is the file containing the server's certificate. The server must have a certificate. The file may also contain the server's private key. See later for how certificates and private keys are created.
Default: ssl server cert = <empty string> .TP ssl server key (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This file contains the private key of the server. If this variable is not defined, the key is looked up in the certificate file (it may be appended to the certificate). The server must have a private key and the certificate must match this private key.
Default: ssl server key = <empty string> .TP ssl version (G) This variable is part of SSL-enabled Samba. This is only available if the SSL libraries have been compiled on your system and the configure option --with-ssl was given at configure time.
This enumeration variable defines the versions of the SSL protocol that will be used. ssl2or3 allows dynamic negotiation of SSL v2 or v3, ssl2 results in SSL v2, ssl3 results in SSL v3 and tls1 results in TLS v1. TLS (Transport Layer Security) is the new standard for SSL.
Default: ssl version = "ssl2or3"
Default: stat cache = yes
Default: stat cache size = 50
With this disabled smbstatus won't be able to tell you what connections are active. You should never need to change this parameter.
Default: status = yes
When strict allocate is no the server does sparse disk block allocation when a file is extended.
Setting this to yes can help Samba return out of quota messages on systems that are restricting the disk quota of users.
Default: strict allocate = no
When strict locking is no the server does file lock checks only when the client explicitly asks for them.
Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases strict locking = no is preferable.
Default: strict locking = no
See also the sync always> parameter.
Default: strict sync = no
Default: strip dot = no
See also the strict sync parameter.
Default: sync always = no
This parameter sets the threshold for sending messages to syslog. Only messages with debug level less than this value will be sent to syslog.
Default: syslog = 1
Default: syslog only = no
Default: template homedir = /home/%D/%U
Default: template shell = /bin/false
Default: time offset = 0
Example: time offset = 60
Default: time server = no
Default: total print jobs = 0
Example: total print jobs = 5000
Default: unix extensions = no
See also passwd program, passwd chat.
Default: unix password sync = no
In order for this parameter to work correctly the encrypt passwords parameter must be set to no when this parameter is set to yes.
Note that even when this parameter is set a user authenticating to smbd must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords.
Default: update encrypted = no
The differentiating factor is that under normal circumstances, the NT/2000 client will attempt to open the network printer using MS-RPC. The problem is that because the client considers the printer to be local, it will attempt to issue the OpenPrinterEx() call requesting access rights associated with the logged on user. If the user possesses local administator rights but not root privilegde on the Samba host (often the case), the OpenPrinterEx() call will fail. The result is that the client will now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed).
If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() call to succeed. This parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server.
See also disable spoolss
Default: use client driver = no
Default: use mmap = yes
NOTE: The use of use rhosts can be a major security hole. This is because you are trusting the PC to supply the correct username. It is very easy to get a PC to supply a false username. I recommend that the use rhosts option be only used if you really know what you are doing.
Default: use rhosts = no
The username line is needed only when the PC is unable to supply its own username. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames. In both these cases you may also be better using the \\server\share%user syntax instead.
The username line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the username line in turn. This is slow and a bad idea for lots of users in case of duplicate passwords. You may get timeouts or security breaches using this parameter unwisely.
Samba relies on the underlying UNIX security. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do.
To restrict a service to a particular set of users you can use the valid users parameter.
If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name.
If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name.
If any of the usernames begin with a '&'then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.
Note that searching though a groups database can take quite some time, and some clients may time out during the search.
See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how this parameter determines access to the services.
Default: The guest account if a guest service, else <empty string>.
Examples:username = fred, mary, jack, jane, @users, @pcgroup
If this parameter is set to non-zero the behavior changes. This parameter is a number that specifies the number of uppercase combinations to try while trying to determine the UNIX user name. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be. Use this parameter when you have strange usernames on your UNIX machine, such as AstrangeUser .
Default: username level = 0
Example: username level = 5
The map file is parsed line by line. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group. The special client name '*' is a wildcard and matches any name. Each line of the map file may be up to 1023 characters long.
The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left. Processing then continues with the next line.
If any line begins with a '#' or a ';' then it is ignored
If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line. Otherwise mapping continues with every line being processed. Using '!' is most useful when you have a wildcard mapping line later in the file.
For example to map from the name admin or administrator to the UNIX name root you would use:
root = admin administrator
Or to map anyone in the UNIX group system to the UNIX name sys you would use:
sys = @system
You can have as many mappings as you like in a username map file.
If your system supports the NIS NETGROUP option then the netgroup database is checked before the /etc/group database for matching groups.
You can map Windows usernames that have spaces in them by using double quotes around the name. For example:
tridge = "Andrew Tridgell"
would map the windows username "Andrew Tridgell" to the unix username "tridge".
The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line.
!sys = mary fred
guest = *
Note that the remapping is applied to all occurrences of usernames. Thus if you connect to \\server\fred and fred is remapped to mary then you will actually be connecting to \\server\mary and will need to supply a password suitable for mary not fred. The only exception to this is the username passed to the password server (if you have one). The password server will receive whatever username the client supplies without modification.
Also note that no reverse mapping is done. The main effect this has is with printing. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.
Default: no username map
Example: username map = /usr/local/samba/lib/users.map .TP utmp (G) This boolean parameter is only available if Samba has been configured and compiled with the option --with-utmp. If set to true then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.
See also the utmp directory parameter.
Default: utmp = no
Default: no utmp directory
The option takes a list of characters in either integer or character form with spaces between them. If you give two characters with a colon between them then it will be taken as an lowercase:uppercase pair.
If you have an editor capable of entering the characters into the config file then it is probably easiest to use this method. Otherwise you can specify the characters in octal, decimal or hexadecimal form using the usual C notation.
For example to add the single character 'Z' to the charset (which is a pointless thing to do as it's already there) you could do one of the following
valid chars = Z
valid chars = z:Z
valid chars = 0132:0172
The last two examples above actually add two characters, and alter the uppercase and lowercase mappings appropriately.
Note that you MUST specify this parameter after the client code page parameter if you have both set. If client code page is set after the valid chars parameter the valid chars settings will be overwritten.
See also the client code page parameter.
Default: Samba defaults to using a reasonable set of valid characters for English systems
Example: valid chars = 0345:0305 0366:0326 0344:0304 The above example allows filenames to have the Swedish characters in them.
NOTE: It is actually quite difficult to correctly produce a valid chars line for a particular system. To automate the process tino@augsburg.net <URL:mailto:tino@augsburg.net> has written a package called validchars which will automatically produce a complete valid chars line for a given client system. Look in the examples/validchars/ subdirectory of your Samba source code distribution for this package.
If this is empty (the default) then any user can login. If a username is in both this list and the invalid users list then access is denied for that user.
The current servicename is substituted for %S . This is useful in the [homes] section.
See also invalid users Default: No valid users list (anyone can login) Example: valid users = greg, @pcusers
Each entry must be a unix path, not a DOS path and must not include the unix directory separator '/'.
Note that the case sensitive option is applicable in vetoing files.
One feature of the veto files parameter that it is important to be aware of is Samba's behaviour when trying to delete a directory. If a directory that is to be deleted contains nothing but veto files this deletion will fail unless you also set the delete veto files parameter to yes.
Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned.
See also hide files and case sensitive.
Default: No files or directories are vetoed. Examples:
; Veto any files containing the word Security, ; any ending in .tmp, and any directory containing the ; word root. veto files = /*Security*/*.tmp/*root*/ ; Veto the Apple specific files that a NetAtalk server ; creates. veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
Default: No files are vetoed for oplock grants
You might want to do this on files that you know will be heavily contended for by clients. A good example of this is in the NetBench SMB benchmark program, which causes heavy client contention for files ending in .SEM. To cause Samba not to grant oplocks on these files you would use the line (either in the [global] section or in the section for the particular NetBench share :
Example: veto oplock files = /*.SEM/ .TP vfs object (S) This parameter specifies a shared object file that is used for Samba VFS I/O operations. By default, normal disk I/O operations are used but these can be overloaded with a VFS object. The Samba VFS layer is new to Samba 2.2 and must be enabled at compile time with --with-vfs.
Default : no value
Default : no value
Default: the name of the share
Note that setting this parameter can have a negative effect on your server performance due to the extra system calls that Samba has to do in order to perform the link checks.
Default: wide links = yes
Default: winbind cache type = 15
Warning: Turning off user enumeration may cause some programs to behave oddly. For example, the finger program relies on having access to the full user list when searching for matching usernames.
Default: winbind enum users = yes
Warning: Turning off group enumeration may cause some programs to behave oddly.
Default: winbind enum groups = yes
Default: winbind gid = <empty string> Example: winbind gid = 10000-20000
Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group.
Default: winbind separator = '\'
Example: winbind separator = +
Default: winbind uid = <empty string> Example: winbind uid = 10000-20000
Default: winbind use default domain = <falseg> Example: winbind use default domain = true
The wins hook parameter specifies the name of a script or executable that will be called as follows:
wins_hook operation name nametype ttl IP_list .RS
An example script that calls the BIND dynamic DNS update program nsupdate is provided in the examples directory of the Samba source code.
Default: wins proxy = no
You should point this at your WINS server if you have a multi-subnetted network.
NOTE. You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.
See the documentation file BROWSING.txt in the docs/ directory of your Samba source distribution.
Default: not enabled
Example: wins server = 192.9.200.1
Default: wins support = no
Default: set at compile time to WORKGROUP
Example: workgroup = MYGROUP
This cache allows Samba to batch client writes into a more efficient write size for RAID disks (i.e. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs.
The integer parameter specifies the size of this cache (per oplocked file) in bytes.
Default: write cache size = 0
Example: write cache size = 262144
for a 256k cache size per file.
Note that if a user is in both the read list and the write list then they will be given write access.
See also the read list option.
Default: write list = <empty string> Example: write list = admin, root, @staff .TP write ok (S) Synonym for writeable.
Default: write raw = yes
If this parameter is no, then users of a service may not create or modify files in the service's directory.
Note that a printable service (printable = yes) will ALWAYS allow writing to the directory (user privileges permitting), but only via spooling operations.
Default: writeable = no
Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility.
On a similar note, many clients - especially DOS clients - limit service names to eight characters. smbd(8) has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters in length.
Use of the [homes] and [printers] special sections make life for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme care when designing these sections. In particular, ensure that the permissions on spool directories are correct.
This man page is correct for version 2.2 of the Samba suite.
samba(7), smbpasswd(8), swat(8), smbd(8), nmbd(8), smbclient(1), nmblookup(1), testparm(1), testprns(1)
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter