smb.conf.5

samba-3.0.22.tar.gz 编译smb服务器的源码

Note that the parameter debug timestamp must be on for this to have an effect\&.

Default: \fB\fIdebug pid\fR = no \fR 

.TP
timestamp logs
This parameter is a synonym for debug timestamp\&.

.TP
debug timestamp (G)
Samba debug log messages are timestamped by default\&. If you are running at a high debug level these timestamps can be distracting\&. This boolean parameter allows timestamping to be turned off\&.

Default: \fB\fIdebug timestamp\fR = yes \fR 

.TP
debug uid (G)
Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on\&.

Note that the parameter debug timestamp must be on for this to have an effect\&.

Default: \fB\fIdebug uid\fR = no \fR 

.TP
default case (S)
See the section on name mangling \&. Also note the short preserve case parameter\&.

Default: \fB\fIdefault case\fR = lower \fR 

.TP
default devmode (S)
This parameter is only applicable to printable services\&. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings\&. The device mode can only correctly be generated by the printer driver itself (which can only be executed on a Win32 platform)\&. Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL\&.

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 \fBdefault devmode = yes\fR will instruct smbd to generate a default one\&.

For more information on Windows NT/2k printing and Device Modes, see the MSDN documentation\&.

Default: \fB\fIdefault devmode\fR = no \fR 

.TP
default
This parameter is a synonym for default service\&.

.TP
default service (G)
This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found\&. Note that the square brackets are \fBNOT\fR given in the parameter value (see example below)\&.

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 \fI%S\fR 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\&.

Default: \fB\fIdefault service\fR = \fR 

Example: \fB\fIdefault service\fR = pub \fR 

.TP
defer sharing violations (G)
Windows allows specifying how a file will be shared with other processes when it is opened\&. Sharing violations occur when a file is opened by a different process using options that violate the share settings specified by other processes\&. This parameter causes smbd to act as a Windows server does, and defer returning a "sharing violation" error message for up to one second, allowing the client to close the file causing the violation in the meantime\&.

UNIX by default does not have this behaviour\&.

There should be no reason to turn off this parameter, as it is designed to enable Samba to more correctly emulate Windows\&.

Default: \fB\fIdefer sharing violations\fR = True \fR 

.TP
delete group script (G)
This is the full pathname to a script that will be run \fBAS ROOT\fR  \fBsmbd\fR(8) when a group is requested to be deleted\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&.

Default: \fB\fIdelete group script\fR = \fR 

.TP
deleteprinter command (G)
With the introduction of MS\-RPC based printer support for Windows NT/2000 clients in Samba 2\&.2, it is now possible to delete printer at run time by issuing the DeletePrinter() RPC call\&.

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 \fIsmb\&.conf\fR\&.

The deleteprinter command is automatically called with only one parameter: printer name\&.

Once the deleteprinter command has been executed, \fBsmbd\fR will reparse the \fI smb\&.conf\fR to associated printer no longer exists\&. If the sharename is still valid, then \fBsmbd \fR will return an ACCESS_DENIED error to the client\&.

Default: \fB\fIdeleteprinter command\fR = \fR 

Example: \fB\fIdeleteprinter command\fR = /usr/bin/removeprinter \fR 

.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: \fB\fIdelete readonly\fR = no \fR 

.TP
delete share command (G)
Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The\fIdelete share command\fR is used to define an external program or script which will remove an existing service definition from \fIsmb\&.conf\fR\&. In order to successfully execute the \fIdelete share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&.

When executed, \fBsmbd\fR will automatically invoke the\fIdelete share command\fR with two parameters\&.


.RS
.TP 3
\(bu
\fIconfigFile\fR \- the location of the global \fIsmb\&.conf\fR file\&.
.TP
\(bu
\fIshareName\fR \- the name of the existing service\&.
.LP
.RE
.IP
This parameter is only used to remove file shares\&. To delete printer shares, see the deleteprinter command\&.

Default: \fB\fIdelete share command\fR = \fR 

Example: \fB\fIdelete share command\fR = /usr/local/bin/delshare \fR 

.TP
delete user from group script (G)
Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools\&. It will be run by \fBsmbd\fR(8)  \fBAS ROOT\fR\&. Any \fI%g\fR will be replaced with the group name and any \fI%u\fR will be replaced with the user name\&.

Default: \fB\fIdelete user from group script\fR = \fR 

Example: \fB\fIdelete user from group script\fR = /usr/sbin/deluser %u %g \fR 

.TP
delete user script (G)
This is the full pathname to a script that will be run by \fBsmbd\fR(8) when managing users with remote RPC (NT) tools\&.

This script is called when a remote client removes a user from the server, normally using 'User Manager for Domains' or\fBrpcclient\fR\&.

This script should delete the given UNIX username\&.

Default: \fB\fIdelete user script\fR = \fR 

Example: \fB\fIdelete user script\fR = /usr/local/samba/bin/del_user %u \fR 

.TP
delete veto files (S)
This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the veto files option)\&. If this option is set to \fBno\fR (the default) then if a vetoed directory contains any non\-vetoed files or directories then the directory delete will fail\&. This is usually what you want\&.

If this option is set to \fByes\fR, 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\&. \fI\&.AppleDouble\fR)

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)\&.

Default: \fB\fIdelete veto files\fR = no \fR 

.TP
dfree cache time (S)
The \fIdfree cache time\fR should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&.

This is a new parameter introduced in Samba version 3\&.0\&.21\&. It specifies in seconds the time that smbd will cache the output of a disk free query\&. If set to zero (the default) no caching is done\&. This allows a heavily loaded server to prevent rapid spawning of dfree command scripts increasing the load\&.

By default this parameter is zero, meaning no caching will be done\&.

\fBNo default\fR

Example: \fB\fIdfree cache time\fR = dfree cache time = 60 \fR 

.TP
dfree command (S)
The \fIdfree command\fR setting should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&.

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\&.

In Samba version 3\&.0\&.21 this parameter has been changed to be a per\-share parameter, and in addition the parameter dfree cache time was added to allow the output of this script to be cached for systems under heavy load\&.

The external program will be passed a single parameter indicating a directory in the filesystem being queried\&. This will typically consist of the string \fI\&./\fR\&. 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 \fBNOT\fR be setuid or setgid and should be owned by (and writeable only by) root!

Where the script dfree (which must be made executable) could be: 
.nf
 
#!/bin/sh
df $1 | tail \-1 | awk '{print $2" "$4}'
.fi
 or perhaps (on Sys V based systems): 
.nf
 
#!/bin/sh
/usr/bin/df \-k $1 | tail \-1 | awk '{print $3" "$5}'
.fi
 Note that you may have to replace the command names with full path names on some systems\&.

By default internal routines for determining the disk capacity and remaining space will be used\&.

\fBNo default\fR

Example: \fB\fIdfree command\fR = /usr/local/samba/bin/dfree \fR 

.TP
directory mode
This parameter is a synonym for directory mask\&.

.TP
directory mask (S)
This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&.

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 \fBnot\fR 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\&.

Default: \fB\fIdirectory mask\fR = 0755 \fR 

Example: \fB\fIdirectory mask\fR = 0775 \fR 

.TP
directory security mask (S)
This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&.

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\&. Make sure not to mix up this parameter with force directory security mode, which works similar like this one but uses logical OR instead of AND\&. 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\&.

\fBNote\fR 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 \fB0777\fR\&.

Default: \fB\fIdirectory security mask\fR = 0777 \fR 

Example: \fB\fIdirectory security mask\fR = 0700 \fR 

.TP
disable netbios (G)
Enabling this parameter will disable netbios support in Samba\&. Netbios is the only available form of browsing