.SS admin users (G)
-This is a list of users who will be granted administrative privilages
+This is a list of users who will be granted administrative privileges
on the share. This means that they will do all file operations as the
super-user (root).
.SS include (G)
-This allows you to include one config file inside another. the file is
+This allows you to include one config file inside another. The file is
included literally, as though typed in place.
It takes the standard substitutions, except %u, %P and %S
.SS mangled map (S)
This is for those who want to directly map UNIX file names which are
not representable on DOS. The mangling of names is not always what is
-needed. In particular you may have documents with file extensiosn
+needed. In particular you may have documents with file extensions
that differ between DOS and UNIX. For example, under UNIX it is common
to use .html for HTML files, whereas under DOS .htm is more commonly
used.
to) five characters of the mangled name.
- a tilde ("~") is appended to the first part of the mangled name, followed
-by a two-character unique sequence, based on the origonal root name
+by a two-character unique sequence, based on the original root name
(i.e., the original filename minus its final extension). The final
extension is included in the hash calculation only if it contains any upper
case characters or is longer than three characters.
Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
(opportunistic lock) then the client is free to assume that it is the
-only one accessing the file and it will agressively cache file
+only one accessing the file and it will aggressively cache file
data. With some oplock types the client may even cache file open/close
operations. This can give enormous performance benefits.
difficult to do under Unix. Samba can fake them, however, by granting
a oplock whenever a client asks for one. This is controlled using the
smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
-you are telling the client that it may agressively cache the file
+you are telling the client that it may aggressively cache the file
data.
By enabling this option on all read-only shares or shares that you know
local methods are used for password control (such as NIS+ etc).
The string can contain the macros %o and %n which are substituted for
-the old and new passwords respectively. It can aso contain the
-standard macros \\n \\r \\t and \\s to give line-feed, carriage-return,
+the old and new passwords respectively. It can also contain the
+standard macros \en \er \et and \es to give line-feed, carriage-return,
tab and space.
The string can also contain a * which matches any sequence of
then no string is expected.
.B Example:
- passwd chat = "*Enter OLD password*" %o\\n "*Enter NEW password*" %n\\n \\
- "*Reenter NEW password*" %n\\n "*Password changed*"
+ passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en \e
+ "*Reenter NEW password*" %n\en "*Password changed*"
+
.B Default:
- passwd chat = *old*password* %o\\n *new*password* %n\\n *new*password* %n\\n *changed*
+ passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed*
.SS passwd program (G)
The name of a program that can be used to set user passwords.
This is only necessary if you have enabled remote password changing at
-compile time. Any occurances of %u will be replaced with the user
+compile time. Any occurrences of %u will be replaced with the user
name.
Also note that many passwd programs insist in "reasonable" passwords,
passwd program = /sbin/passwd %u
.SS password level (G)
-Some client/server conbinations have difficulty with mixed-case passwords.
+Some client/server combinations have difficulty with mixed-case passwords.
One offending client is Windows for Workgroups, which for some reason forces
passwords to upper case when using the LANMAN1 protocol, but leaves them alone
when using COREPLUS!
mandatory of course, but you probably won't get the results you expect if you
do otherwise.
-Any occurances of %u in the path will be replaced with the username
-that the client is connecting as. Any occurances of %m will be
+Any occurrences of %u in the path will be replaced with the username
+that the client is connecting as. Any occurrences of %m will be
replaced by the name of the machine they are connecting from. These
replacements are very useful for setting up pseudo home directories
for users.
none (no command executed)
.B Example:
- postexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log
+ postexec = echo \e"%u disconnected from %S from %m (%I)\e" >> /tmp/log
.SS postscript (S)
This parameter forces a printer to interpret the print files as
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!\" | \
+preexec = csh -c 'echo \e"Welcome to %S!\e" | \e
/usr/local/samba/bin/smbclient -M %m -I %I' &
Of course, this could get annoying after a while :-)
none (no command executed)
.B Example:
- preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log
+ preexec = echo \e"%u connected to %S from %m (%I)\e" >> /tmp/log
.SS preferred master (G)
This boolean parameter controls if Samba is a preferred master browser
The full path name will be used for the filename if %s is not preceded
by a /. If you don't like this (it can stuff up some lpq output) then
-use %f instead. Any occurances of %f get replaced by the spool
+use %f instead. Any occurrences of %f get replaced by the spool
filename without the full path at the front.
The print command MUST contain at least one occurrence of "%s" or %f -
to arbitrary IP addresses with an arbitrary workgroup name.
This is useful if you want your Samba server to appear in a remote
-workgroup for which the normal browse propogation rules don't
+workgroup for which the normal browse propagation rules don't
work. The remote workgroup can be anywhere that you can send IP
packets to.
This options controls whether Samba will allow a previously validated
username/password pair to be used to attach to a share. Thus if you
-connect to \\\\server\\share1 then to \\\\server\\share2 it won't
+connect to \e\eserver\eshare1 then to \e\eserver\eshare2 it won't
automatically allow the client to request connection to the second
share as the same username as the first without a password.
If 'set directory = no', then users of the service may not use the setdir
command to change directory.
-The setdir comand is only implemented in the Digital Pathworks client. See the
+The setdir command is only implemented in the Digital Pathworks client. See the
Pathworks documentation for details.
.B Default:
The share modes that are enabled by this option are DENY_DOS,
DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB.
-Enabling this option gives full share compatability but may cost a bit
+Enabling this option gives full share compatibility but may cost a bit
of processing time on the UNIX server. They are enabled by default.
.B Default:
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
+cases you may also be better using the \e\eserver\eshare%user syntax
instead.
The username= line is not a great solution in many cases as it means Samba
You can have as many mappings as you like in a username map file.
-Note that the remapping is applied to all occurances of
-usernames. Thus if you connect to "\\\\server\\fred" and "fred" is
+Note that the remapping is applied to all occurrences of
+usernames. Thus if you connect to "\e\eserver\efred" and "fred" is
remapped to "mary" then you will actually be connecting to
-"\\\\server\\mary" and will need to supply a password suitable for
+"\e\eserver\emary" 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.
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 hexidecimal form
+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
Step 1: If the client has passed a username/password pair and that
username/password pair is validated by the UNIX system's password
programs then the connection is made as that username. Note that this
-includes the \\\\server\\service%username method of passing a username.
+includes the \e\eserver\eservice%username method of passing a username.
Step 2: If the client has previously registered a username with the
system and now supplies a correct password for that username then the
git.samba.org / kai / samba.git / blobdiff