diff options
| author | Andrew Tridgell <tridge@samba.org> | 2000-05-12 13:05:25 +0000 |
|---|---|---|
| committer | Andrew Tridgell <tridge@samba.org> | 2000-05-12 13:05:25 +0000 |
| commit | faa3f49430775fd1bd327237f369f7b5df6fc0c6 (patch) | |
| tree | b31814c4d9d1bbbb709d7f680a6483467d3e5b42 | |
| parent | 3fed01f9c311bb81ce3013453a5dc9630201ccf1 (diff) | |
| download | samba-faa3f49430775fd1bd327237f369f7b5df6fc0c6.tar.gz | |
- added example config section to winbindd man page
- reran yodldocs with newer version of yodl
37 files changed, 4010 insertions, 3699 deletions
diff --git a/docs/htmldocs/DOMAIN_MEMBER.html b/docs/htmldocs/DOMAIN_MEMBER.html index 409534c99ef..847c6c51891 100644 --- a/docs/htmldocs/DOMAIN_MEMBER.html +++ b/docs/htmldocs/DOMAIN_MEMBER.html @@ -3,9 +3,10 @@ + <html><head><title>Joining an NT Domain with Samba 2.0</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,79 +16,79 @@ <h2>Jeremy Allison, Samba Team</h2> <h2>7th October 1999</h2> - +<h1>Table of Contents </h1><p></p> <p><hr><p><br> -<p><br><center>Joining an NT Domain with Samba 2.0 </center> +<p><center>Joining an NT Domain with Samba 2.0 </center> <center>----------------------------------- </center> -<p><br>In order for a Samba-2 server to join an NT domain, you must first add +<p>In order for a Samba-2 server to join an NT domain, you must first add the NetBIOS name of the Samba server to the NT domain on the PDC using Server Manager for Domains. This creates the machine account in the domain (PDC) SAM. Note that you should add the Samba server as a "Windows NT Workstation or Server", <em>NOT</em> as a Primary or backup domain controller. -<p><br>Assume you have a Samba-2 server with a NetBIOS name of <code>SERV1</code> and are +<p>Assume you have a Samba-2 server with a NetBIOS name of <code>SERV1</code> and are joining an NT domain called <code>DOM</code>, which has a PDC with a NetBIOS name of <code>DOMPDC</code> and two backup domain controllers with NetBIOS names <code>DOMBDC1</code> and <code>DOMBDC2</code>. -<p><br>In order to join the domain, first stop all Samba daemons and run the +<p>In order to join the domain, first stop all Samba daemons and run the command -<p><br><code>smbpasswd -j DOM -r DOMPDC</code> -<p><br>as we are joining the domain DOM and the PDC for that domain (the only -machine that has write access to the domain SAM database). If this is +<p><code>smbpasswd -j DOM -r DOMPDC</code> +<p>as we are joining the domain DOM and the PDC for that domain (the only +machine that has write access to the domain SAM database) is DOMPDC. If this is successful you will see the message: -<p><br><code>smbpasswd: Joined domain DOM.</code> -<p><br>in your terminal window. See the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> +<p><code>smbpasswd: Joined domain DOM.</code> +<p>in your terminal window. See the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> man page for more details. -<p><br>This command goes through the machine account password change +<p>This command goes through the machine account password change protocol, then writes the new (random) machine account password for -this Samba server into the a file in the same directory in which an -smbpasswd file would be stored (normally : -<p><br><code>/usr/local/samba/private</code> -<p><br>The filename looks like this: -<p><br><code><NT DOMAIN NAME>.<Samba Server Name>.mac</code> -<p><br>The <code>.mac</code> suffix stands for machine account password file. So in +this Samba server into a file in the same directory in which an +smbpasswd file would be stored - normally : +<p><code>/usr/local/samba/private</code> +<p>The filename looks like this: +<p><code><NT DOMAIN NAME>.<Samba Server Name>.mac</code> +<p>The <code>.mac</code> suffix stands for machine account password file. So in our example above, the file would be called: -<p><br><code>DOM.SERV1.mac</code> -<p><br>This file is created and owned by root and is not readable by any +<p><code>DOM.SERV1.mac</code> +<p>This file is created and owned by root and is not readable by any other user. It is the key to the domain-level security for your system, and should be treated as carefully as a shadow password file. -<p><br>Now, before restarting the Samba daemons you must edit your +<p>Now, before restarting the Samba daemons you must edit your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file to tell Samba it should now use domain security. -<p><br>Change (or add) your -<p><br><a href="smb.conf.5.html#security"><strong>"security ="</strong></a> -<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section of your +<p>Change (or add) your +<p><a href="smb.conf.5.html#security"><strong>"security ="</strong></a> +<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section of your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> to read: -<p><br><code>security = domain</code> -<p><br>Next change the -<p><br><a href="smb.conf.5.html#workgroup"><strong>"workgroup ="</strong></a> -<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read: -<p><br><code>workgroup = DOM</code> -<p><br>as this is the name of the domain we are joining. -<p><br>You must also have the parameter <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt passwords"</strong></a> +<p><code>security = domain</code> +<p>Next change the +<p><a href="smb.conf.5.html#workgroup"><strong>"workgroup ="</strong></a> +<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read: +<p><code>workgroup = DOM</code> +<p>as this is the name of the domain we are joining. +<p>You must also have the parameter <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt passwords"</strong></a> set to <code>"yes"</code> in order for your users to authenticate to the NT PDC. -<p><br>Finally, add (or modify) a: -<p><br><a href="smb.conf.5.html#passwordserver"><strong>"password server ="</strong></a> -<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read: -<p><br><code>password server = DOMPDC DOMBDC1 DOMBDC2</code> -<p><br>These are the primary and backup domain controllers Samba will attempt +<p>Finally, add (or modify) a: +<p><a href="smb.conf.5.html#passwordserver"><strong>"password server ="</strong></a> +<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read: +<p><code>password server = DOMPDC DOMBDC1 DOMBDC2</code> +<p>These are the primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load among domain controllers. -<p><br>Alternatively, if you want smbd to automatically determine the +<p>Alternatively, if you want smbd to automatically determine the list of Domain controllers to use for authentication, you may set this line to be : -<p><br><code>password server = *</code> -<p><br>This method, which is new in Samba 2.0.6 and above, allows Samba +<p><code>password server = *</code> +<p>This method, which is new in Samba 2.0.6 and above, allows Samba to use exactly the same mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against. -<p><br>Finally, restart your Samba daemons and get ready for clients to begin +<p>Finally, restart your Samba daemons and get ready for clients to begin using domain security! -<p><br><center>Why is this better than security = server? </center> +<p><center>Why is this better than security = server? </center> <center>------------------------------------------ </center> -<p><br>Currently, domain security in Samba doesn't free you from having to +<p>Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching to your server. This means that if domain user <code>DOM\fred</code> attaches to your domain security Samba server, there needs to be a local Unix user fred @@ -95,14 +96,14 @@ to represent that user in the Unix filesystem. This is very similar to the older Samba security mode <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a>, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would. -<p><br>The advantage to domain-level security is that the authentication in +<p>The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource domain PDC to an account domain PDC. -<p><br>In addition, with <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> every Samba daemon on a +<p>In addition, with <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run out of available @@ -110,7 +111,7 @@ connections. With <a href="smb.conf.5.html#securityequaldomain"><strong>"securit daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. -<p><br>And finally, acting in the same manner as an NT server authenticating +<p>And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such as the user SID, the list of NT groups the user belongs to, etc. All this information @@ -120,7 +121,7 @@ users will be necessary, and Samba will generate Unix uids and gids from the information passed back from the PDC when a user is authenticated, making a Samba server truly plug and play in an NT domain environment. Watch for this code soon. -<p><br><em>NOTE:</em> Much of the text of this document was first published in the +<p><em>NOTE:</em> Much of the text of this document was first published in the Web magazine <a href="http://www.linuxworld.com"><strong>"LinuxWorld"</strong></a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"><strong>"Doing the NIS/NT Samba"</strong></a>. </body> </html> diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index ece68eb5114..af88b4aded0 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -3,9 +3,10 @@ + <html><head><title>lmhosts (5)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,79 +16,78 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> lmhosts - The Samba NetBIOS hosts file -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br>lmhosts is the <strong>Samba</strong> NetBIOS name to IP address mapping file. -<p><br><a name="DESCRIPTION"></a> +<p>lmhosts is the <strong>Samba</strong> NetBIOS name to IP address mapping file. +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This file is part of the <strong>Samba</strong> suite. -<p><br><strong>lmhosts</strong> is the <strong>Samba</strong> NetBIOS name to IP address mapping file. It +<p>This file is part of the <strong>Samba</strong> suite. +<p><strong>lmhosts</strong> is the <strong>Samba</strong> NetBIOS name to IP address mapping file. It is very similar to the <strong>/etc/hosts</strong> file format, except that the hostname component must correspond to the NetBIOS naming format. -<p><br><a name="FILEFORMAT"></a> +<p><a name="FILEFORMAT"></a> <h2>FILE FORMAT</h2> -<p><br>It is an ASCII file containing one line for NetBIOS name. The two +<p>It is an ASCII file containing one line for NetBIOS name. The two fields on each line are separated from each other by white space. Any entry beginning with # is ignored. Each line in the lmhosts file contains the following information : -<p><br><ul> -<p><br><li > <strong>IP Address</strong> - in dotted decimal format. -<p><br><li > <strong>NetBIOS Name</strong> - This name format is a maximum fifteen +<p><dl> +<p><li > <strong>IP Address</strong> - in dotted decimal format. +<p><li > <strong>NetBIOS Name</strong> - This name format is a maximum fifteen character host name, with an optional trailing <code>'#'</code> character followed by the NetBIOS name type as two hexadecimal digits. -<p><br>If the trailing <code>'#'</code> is omitted then the given IP address will be +<p>If the trailing <code>'#'</code> is omitted then the given IP address will be returned for all names that match the given name, whatever the NetBIOS name type in the lookup. -<p><br></ul> -<p><br>An example follows : -<p><br># <br> +<p></dl> +<p>An example follows : +<p># <br> # Sample Samba lmhosts file. <br> # <br> 192.9.200.1 TESTPC <br> 192.9.200.20 NTSERVER#20 <br> 192.9.200.21 SAMBASERVER <br> -<p><br>Contains three IP to NetBIOS name mappings. The first and third will +<p>Contains three IP to NetBIOS name mappings. The first and third will be returned for any queries for the names <code>"TESTPC"</code> and <code>"SAMBASERVER"</code> respectively, whatever the type component of the NetBIOS name requested. -<p><br>The second mapping will be returned only when the <code>"0x20"</code> name type +<p>The second mapping will be returned only when the <code>"0x20"</code> name type for a name <code>"NTSERVER"</code> is queried. Any other name type will not be resolved. -<p><br>The default location of the <strong>lmhosts</strong> file is in the same directory +<p>The default location of the <strong>lmhosts</strong> file is in the same directory as the <a href="smb.conf.html"><strong>smb.conf</strong></a> file. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smb.conf.5.html#nameresolveorder"><strong>smb.conf (5)</strong></a>, +<p><a href="smb.conf.5.html#nameresolveorder"><strong>smb.conf (5)</strong></a>, <a href="smbclient.1.html#minusR"><strong>smbclient (1)</strong></a>, <a href="smbpasswd.8.html#minusR"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba (7)</strong></a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/make_smbcodepage.1.html b/docs/htmldocs/make_smbcodepage.1.html index 3fa9a1c5357..558a559f03b 100644 --- a/docs/htmldocs/make_smbcodepage.1.html +++ b/docs/htmldocs/make_smbcodepage.1.html @@ -3,9 +3,10 @@ + <html><head><title>make_smbcodepage (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,45 +16,44 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> make_codepage - Construct a codepage file for Samba -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>make_smbcodepage</strong> [<a href="make_smbcodepage.1.html#cord">c|d</a>] <a href="make_smbcodepage.1.html#codepage">codepage</a> <a href="make_smbcodepage.1.html#inputfile">inputfile</a> <a href="make_smbcodepage.1.html#outputfile">outputfile</a> -<p><br><a name="DESCRIPTION"></a> +<p><strong>make_smbcodepage</strong> [<a href="make_smbcodepage.1.html#cord">c|d</a>] <a href="make_smbcodepage.1.html#codepage">codepage</a> <a href="make_smbcodepage.1.html#inputfile">inputfile</a> <a href="make_smbcodepage.1.html#outputfile">outputfile</a> +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>make_smbcodepage</strong> compiles or de-compiles codepage files for use +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>make_smbcodepage</strong> compiles or de-compiles codepage files for use with the internationalization features of Samba 2.0 -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="cord"></a> -<li><strong>c|d</strong> This tells <strong>make_smbcodepage</strong> if it is compiling (<strong>c</strong>) a text +<p><dl> +<p><a name="cord"></a> +<p></p><dt><strong>c|d</strong><dd> This tells <strong>make_smbcodepage</strong> if it is compiling (<strong>c</strong>) a text format code page file to binary, or (<strong>d</strong>) de-compiling a binary codepage file to text. -<p><br><a name="codepage"></a> -<li><strong>codepage</strong> This is the codepage we are processing (a number, e.g. 850). -<p><br><a name="inputfile"></a> -<li><strong>inputfile</strong> This is the input file to process. In the '<strong>c</strong>' case this +<p><a name="codepage"></a> +<p></p><dt><strong>codepage</strong><dd> This is the codepage we are processing (a number, e.g. 850). +<p><a name="inputfile"></a> +<p></p><dt><strong>inputfile</strong><dd> This is the input file to process. In the '<strong>c</strong>' case this will be a text codepage definition file such as the ones found in the Samba <em>source/codepages</em> directory. In the '<strong>d</strong>' case this will be the binary format codepage definition file normally found in the <em>lib/codepages</em> directory in the Samba install directory path. -<p><br><a name="outputfile"></a> -<li><strong>outputfile</strong> This is the output file to produce. -<p><br></ul> -<p><br><a name="SambaCodepageFiles"></a> +<p><a name="outputfile"></a> +<p></p><dt><strong>outputfile</strong><dd> This is the output file to produce. +<p></dl> +<p><a name="SambaCodepageFiles"></a> <h2>Samba Codepage Files</h2> -<p><br>A text Samba codepage definition file is a description that tells +<p>A text Samba codepage definition file is a description that tells Samba how to map from upper to lower case for characters greater than ascii 127 in the specified DOS code page. Note that for certain DOS codepages (437 for example) mapping from lower to upper case may be @@ -61,10 +61,10 @@ non-symmetrical. For example, in code page 437 lower case a acute maps to a plain upper case A when going from lower to upper case, but plain upper case A maps to plain lower case a when lower casing a character. -<p><br>A binary Samba codepage definition file is a binary representation of +<p>A binary Samba codepage definition file is a binary representation of the same information, including a value that specifies what codepage this file is describing. -<p><br>As Samba does not yet use UNICODE (current for Samba version 2.0) you +<p>As Samba does not yet use UNICODE (current for Samba version 2.0) you must specify the client code page that your DOS and Windows clients are using if you wish to have case insensitivity done correctly for your particular language. The default codepage Samba uses is 850 @@ -74,70 +74,70 @@ provided in the Samba distribution for codepages 437 (USA), 737 866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949 (Hangul) and 950 (Traditional Chinese). Users are encouraged to write text codepage definition files for their own code pages and donate -them to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. All codepage files in the +them to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. All codepage files in the Samba <em>source/codepages</em> directory are compiled and installed when a <em>'make install'</em> command is issued there. -<p><br>The client codepage used by the <a href="smbd.8.html"><strong>smbd</strong></a> server is +<p>The client codepage used by the <a href="smbd.8.html"><strong>smbd</strong></a> server is configured using the <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. -<p><br><a name="FILES"></a> +<p><a name="FILES"></a> <h2>FILES</h2> -<p><br><strong>codepage_def.<codepage></strong> -<p><br>These are the input (text) codepage files provided in the Samba +<p><strong>codepage_def.<codepage></strong> +<p>These are the input (text) codepage files provided in the Samba <em>source/codepages</em> directory. -<p><br>A text codepage definition file consists of multiple lines +<p>A text codepage definition file consists of multiple lines containing four fields. These fields are : -<p><br><ul> -<p><br><li > <strong>lower</strong>: which is the (hex) lower case character mapped on this +<p><dl> +<p><li > <strong>lower</strong>: which is the (hex) lower case character mapped on this line. -<p><br><li > <strong>upper</strong>: which is the (hex) upper case character that the lower +<p><li > <strong>upper</strong>: which is the (hex) upper case character that the lower case character will map to. -<p><br><li > <strong>map upper to lower</strong> which is a boolean value (put either True +<p><li > <strong>map upper to lower</strong> which is a boolean value (put either True or False here) which tells Samba if it is to map the given upper case character to the given lower case character when lower casing a filename. -<p><br><li > <strong>map lower to upper</strong> which is a boolean value (put either True +<p><li > <strong>map lower to upper</strong> which is a boolean value (put either True or False here) which tells Samba if it is to map the given lower case character to the given upper case character when upper casing a filename. -<p><br></ul> -<p><br><strong>codepage.<codepage></strong> These are the output (binary) codepage files +<p></dl> +<p><strong>codepage.<codepage></strong> These are the output (binary) codepage files produced and placed in the Samba destination <em>lib/codepage</em> directory. -<p><br><a name="INSTALLATION"></a> +<p><a name="INSTALLATION"></a> <h2>INSTALLATION</h2> -<p><br>The location of the server and its support files is a matter for +<p>The location of the server and its support files is a matter for individual system administrators. The following are thus suggestions only. -<p><br>It is recommended that the <strong>make_smbcodepage</strong> program be installed +<p>It is recommended that the <strong>make_smbcodepage</strong> program be installed under the <em>/usr/local/samba</em> hierarchy, in a directory readable by all, writeable only by root. The program itself should be executable by all. The program should NOT be setuid or setgid! -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 03fd3588e26..12f8178cfa3 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -3,9 +3,10 @@ + <html><head><title>nmbd</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,30 +16,29 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> nmbd - NetBIOS name server to provide NetBIOS over IP naming services to clients -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>nmbd</strong> [<a href="nmbd.8.html#minusD">-D</a>] [<a href="nmbd.8.html#minusa">-a</a>] [<a href="nmbd.8.html#minuso">-o</a>] [<a href="nmbd.8.html#minush">-h</a>] [<a href="nmbd.8.html#minusV">-V</a>] [<a href="nmbd.8.html#minusH">-H lmhosts file</a>] [<a href="nmbd.8.html#minusd">-d debuglevel</a>] [<a href="nmbd.8.html#minusl">-l log file basename</a>] [<a href="nmbd.8.html#minusn">-n primary NetBIOS name</a>] [<a href="nmbd.8.html#minusp">-p port number</a>] [<a href="nmbd.8.html#minuss">-s configuration file</a>] [<a href="nmbd.8.html#minusi">-i NetBIOS scope</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>nmbd</strong> [<a href="nmbd.8.html#minusD">-D</a>] [<a href="nmbd.8.html#minusa">-a</a>] [<a href="nmbd.8.html#minuso">-o</a>] [<a href="nmbd.8.html#minush">-h</a>] [<a href="nmbd.8.html#minusV">-V</a>] [<a href="nmbd.8.html#minusH">-H lmhosts file</a>] [<a href="nmbd.8.html#minusd">-d debuglevel</a>] [<a href="nmbd.8.html#minusl">-l log file basename</a>] [<a href="nmbd.8.html#minusn">-n primary NetBIOS name</a>] [<a href="nmbd.8.html#minusp">-p port number</a>] [<a href="nmbd.8.html#minuss">-s configuration file</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>nmbd</strong> is a server that understands and can reply to NetBIOS over IP +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>nmbd</strong> is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMBD/CIFS clients such as Windows 95/98, Windows NT and LanManager clients. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view. -<p><br>SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS +<p>SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server. That is, they wish to know what IP number a specified host is using. -<p><br>Amongst other services, <strong>nmbd</strong> will listen for such requests, +<p>Amongst other services, <strong>nmbd</strong> will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this @@ -46,37 +46,37 @@ can be overridden with the <strong>-n</strong> option (see <a href="nmbd.8.html# <strong>nmbd</strong> will reply to broadcast queries for its own name(s). Additional names for <strong>nmbd</strong> to respond on can be set via parameters in the <a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a> configuration file. -<p><br><strong>nmbd</strong> can also be used as a WINS (Windows Internet Name Server) +<p><strong>nmbd</strong> can also be used as a WINS (Windows Internet Name Server) server. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names. -<p><br>In addition, <strong>nmbd</strong> can act as a WINS proxy, relaying broadcast queries +<p>In addition, <strong>nmbd</strong> can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WIN server. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minusD"></a> -<li><strong><strong>-D</strong></strong> If specified, this parameter causes <strong>nmbd</strong> to operate +<p><dl> +<p><a name="minusD"></a> +<p></p><dt><strong><strong>-D</strong></strong><dd> If specified, this parameter causes <strong>nmbd</strong> to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. By default, <strong>nmbd</strong> will NOT operate as a daemon. nmbd can also be operated from the inetd meta-daemon, although this is not recommended. -<p><br><a name="minusa"></a> -<li><strong><strong>-a</strong></strong> If this parameter is specified, each new connection will +<p><a name="minusa"></a> +<p></p><dt><strong><strong>-a</strong></strong><dd> If this parameter is specified, each new connection will append log messages to the log file. This is the default. -<p><br><a name="minuso"></a> -<li><strong><strong>-o</strong></strong> If this parameter is specified, the log files will be +<p><a name="minuso"></a> +<p></p><dt><strong><strong>-o</strong></strong><dd> If this parameter is specified, the log files will be overwritten when opened. By default, the log files will be appended to. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> Prints the help information (usage) for <strong>nmbd</strong>. -<p><br><a name="minusV"></a> -<li><strong><strong>-V</strong></strong> Prints the version number for <strong>nmbd</strong>. -<p><br><a name="minusH"></a> -<li><strong><strong>-H filename</strong></strong> NetBIOS lmhosts file. -<p><br>The lmhosts file is a list of NetBIOS names to IP addresses that is +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> Prints the help information (usage) for <strong>nmbd</strong>. +<p><a name="minusV"></a> +<p></p><dt><strong><strong>-V</strong></strong><dd> Prints the version number for <strong>nmbd</strong>. +<p><a name="minusH"></a> +<p></p><dt><strong><strong>-H filename</strong></strong><dd> NetBIOS lmhosts file. +<p>The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> described in <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> to resolve any @@ -84,92 +84,85 @@ NetBIOS name queries needed by the server. Note that the contents of this file are <em>NOT</em> used by <strong>nmbd</strong> to answer any name queries. Adding a line to this file affects name NetBIOS resolution from this host <em>ONLY</em>. -<p><br>The default path to this file is compiled into Samba as part of the +<p>The default path to this file is compiled into Samba as part of the build process. Common defaults are <em>/usr/local/samba/lib/lmhosts</em>, <em>/usr/samba/lib/lmhosts</em> or <em>/etc/lmhosts</em>. See the <a href="lmhosts.5.html"><strong>lmhosts (5)</strong></a> man page for details on the contents of this file. -<p><br><a name="minusd"></a> -<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10. -<p><br>The default value if this parameter is not specified is zero. -<p><br>The higher this value, the more detail will be logged to the log files +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10. +<p>The default value if this parameter is not specified is zero. +<p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out. -<p><br>Levels above 1 will generate considerable amounts of log data, and +<p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. -<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log +<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. -<p><br><a name="minusl"></a> -<li><strong><strong>-l logfile</strong></strong> The <strong>-l</strong> parameter specifies a path and base +<p><a name="minusl"></a> +<p></p><dt><strong><strong>-l logfile</strong></strong><dd> The <strong>-l</strong> parameter specifies a path and base filename into which operational data from the running nmbd server will be logged. The actual log file name is generated by appending the extension ".nmb" to the specified base name. For example, if the name specified was "log" then the file log.nmb would contain the debugging data. -<p><br>The default log file path is compiled into Samba as part of the +<p>The default log file path is compiled into Samba as part of the build process. Common defaults are <em>/usr/local/samba/var/log.nmb</em>, <em>/usr/samba/var/log.nmb</em> or <em>/var/log/log.nmb</em>. -<p><br><a name="minusn"></a> -<li><strong><strong>-n primary NetBIOS name</strong></strong> This option allows you to override +<p><a name="minusn"></a> +<p></p><dt><strong><strong>-n primary NetBIOS name</strong></strong><dd> This option allows you to override the NetBIOS name that Samba uses for itself. This is identical to setting the <a href="smb.conf.5.html#netbiosname"><strong>NetBIOS name</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file but will override the setting in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. -<p><br><a name="minusp"></a> -<li><strong><strong>-p UDP port number</strong></strong> UDP port number is a positive integer value. -<p><br>This option changes the default UDP port number (normally 137) that +<p><a name="minusp"></a> +<p></p><dt><strong><strong>-p UDP port number</strong></strong><dd> UDP port number is a positive integer value. +<p>This option changes the default UDP port number (normally 137) that <strong>nmbd</strong> responds to name queries on. Don't use this option unless you are an expert, in which case you won't need help! -<p><br><a name="minuss"></a> -<li><strong><strong>-s configuration file</strong></strong> The default configuration file name is +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s configuration file</strong></strong><dd> The default configuration file name is set at build time, typically as <em>/usr/local/samba/lib/smb.conf</em>, but this may be changed when Samba is autoconfigured. -<p><br>The file specified contains the configuration details required by the +<p>The file specified contains the configuration details required by the server. See <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> for more information. -<p><br><a name="minusi"></a> -<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that <strong>nmbd</strong> will use -to communicate with when generating NetBIOS names. For details on the -use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes -are <em>very</em> rarely used, only set this parameter if you are the -system administrator in charge of all the NetBIOS systems you -communicate with. -<p><br></ul> -<p><br><a name="FILES"></a> +<p></dl> +<p><a name="FILES"></a> <h2>FILES</h2> -<p><br><strong>/etc/inetd.conf</strong> -<p><br>If the server is to be run by the inetd meta-daemon, this file must +<p><strong>/etc/inetd.conf</strong> +<p>If the server is to be run by the inetd meta-daemon, this file must contain suitable startup information for the meta-daemon. -<p><br><strong>/etc/rc</strong> -<p><br>(or whatever initialization script your system uses). -<p><br>If running the server as a daemon at startup, this file will need to +<p><strong>/etc/rc</strong> +<p>(or whatever initialization script your system uses). +<p>If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. -<p><br><strong>/usr/local/samba/lib/smb.conf</strong> -<p><br>This is the default location of the +<p><strong>/usr/local/samba/lib/smb.conf</strong> +<p>This is the default location of the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> server configuration file. Other common places that systems install this file are <em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>. -<p><br>When run as a <strong>WINS</strong> server (see the <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a> +<p>When run as a <strong>WINS</strong> server (see the <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page), <strong>nmbd</strong> will store the WINS database in the file <code>wins.dat</code> in the <code>var/locks</code> directory configured under wherever Samba was configured to install itself. -<p><br>If <strong>nmbd</strong> is acting as a <strong>browse master</strong> (see the <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a> +<p>If <strong>nmbd</strong> is acting as a <strong>browse master</strong> (see the <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page), <strong>nmbd</strong> will store the browsing database in the file <code>browse.dat</code> in the <code>var/locks</code> directory configured under wherever Samba was configured to install itself. -<p><br><a name="SIGNALS"></a> +<p><a name="SIGNALS"></a> <h2>SIGNALS</h2> -<p><br>To shut down an <strong>nmbd</strong> process it is recommended that SIGKILL (-9) +<p>To shut down an <strong>nmbd</strong> process it is recommended that SIGKILL (-9) <em>NOT</em> be used, except as a last resort, as this may leave the name database in an inconsistent state. The correct way to terminate <strong>nmbd</strong> is to send it a SIGTERM (-15) signal and wait for it to die on its own. -<p><br><strong>nmbd</strong> will accept SIGHUP, which will cause it to dump out it's +<p><strong>nmbd</strong> will accept SIGHUP, which will cause it to dump out it's namelists into the file <code>namelist.debug</code> in the <em>/usr/local/samba/var/locks</em> directory (or the <em>var/locks</em> directory configured under wherever Samba was configured to install @@ -179,34 +172,34 @@ by sending it a SIGUSR1 (<code>kill -USR1 <nmbd-pid></code>) and lowered b SIGUSR2 (<code>kill -USR2 <nmbd-pid></code>). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>inetd (8)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf +<p><strong>inetd (8)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>, <a href="testprns.1.html"><strong>testprns (1)</strong></a>, and the Internet RFC's <strong>rfc1001.txt</strong>, <strong>rfc1002.txt</strong>. In addition the CIFS (formerly SMB) specification is available as a link from the Web page : <a href="http://samba.org/cifs/">http://samba.org/cifs/</a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 2c3e80c76e2..57effe149d3 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -3,9 +3,10 @@ + <html><head><title>nmblookup (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,139 +16,138 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> nmblookup - NetBIOS over TCP/IP client used to lookup NetBIOS names -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>nmblookup</strong> [<a href="nmblookup.1.html#minusM">-M</a>] [<a href="nmblookup.1.html#minusR">-R</a>] [<a href="nmblookup.1.html#minusS">-S</a>] [<a href="nmblookup.1.html#minusr">-r</a>] [<a href="nmblookup.1.html#minusA">-A</a>] [<a href="nmblookup.1.html#minush">-h</a>] [<a href="nmblookup.1.html#minusB">-B broadcast address</a>] [<a href="nmblookup.1.html#minusU">-U unicast address</a>] [<a href="nmblookup.1.html#minusd">-d debuglevel</a>] [<a href="nmblookup.1.html#minuss">-s smb config file</a>] [<a href="nmblookup.1.html#minusi">-i NetBIOS scope</a>] [<a href="nmblookup.1.html#minusT">-T</a>] <a href="nmblookup.1.html#name">name</a> -<p><br><a name="DESCRIPTION"></a> +<p><strong>nmblookup</strong> [<a href="nmblookup.1.html#minusM">-M</a>] [<a href="nmblookup.1.html#minusR">-R</a>] [<a href="nmblookup.1.html#minusS">-S</a>] [<a href="nmblookup.1.html#minusr">-r</a>] [<a href="nmblookup.1.html#minusA">-A</a>] [<a href="nmblookup.1.html#minush">-h</a>] [<a href="nmblookup.1.html#minusB">-B broadcast address</a>] [<a href="nmblookup.1.html#minusU">-U unicast address</a>] [<a href="nmblookup.1.html#minusd">-d debuglevel</a>] [<a href="nmblookup.1.html#minuss">-s smb config file</a>] [<a href="nmblookup.1.html#minusi">-i NetBIOS scope</a>] [<a href="nmblookup.1.html#minusT">-T</a>] <a href="nmblookup.1.html#name">name</a> +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>nmblookup</strong> is used to query NetBIOS names and map them to IP +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>nmblookup</strong> is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine. All queries are done over UDP. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minusM"></a> -<li><strong><strong>-M</strong></strong> Searches for a master browser by looking up the +<p><dl> +<p><a name="minusM"></a> +<p></p><dt><strong><strong>-M</strong></strong><dd> Searches for a master browser by looking up the NetBIOS name <a href="nmblookup.1.html#name"><strong>name</strong></a> with a type of 0x1d. If <a href="nmblookup.1.html#name"><strong>name</strong></a> is <code>"-"</code> then it does a lookup on the special name <code>__MSBROWSE__</code>. -<p><br><a name="minusR"></a> -<li><strong><strong>-R</strong></strong> Set the recursion desired bit in the packet to do a +<p><a name="minusR"></a> +<p></p><dt><strong><strong>-R</strong></strong><dd> Set the recursion desired bit in the packet to do a recursive lookup. This is used when sending a name query to a machine running a WINS server and the user wishes to query the names in the WINS server. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead. See rfc1001, rfc1002 for details. -<p><br><a name="minusS"></a> -<li><strong><strong>-S</strong></strong> Once the name query has returned an IP address then do a +<p><a name="minusS"></a> +<p></p><dt><strong><strong>-S</strong></strong><dd> Once the name query has returned an IP address then do a node status query as well. A node status query returns the NetBIOS names registered by a host. -<p><br><a name="minusr"></a> -<li><strong><strong>-r</strong></strong> Try and bind to UDP port 137 to send and receive UDP +<p><a name="minusr"></a> +<p></p><dt><strong><strong>-r</strong></strong><dd> Try and bind to UDP port 137 to send and receive UDP datagrams. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX systems root privilage is needed to bind to this port, and in addition, if the <a href="nmbd.8.html"><strong>nmbd</strong></a> daemon is running on this machine it also binds to this port. -<p><br><a name="minusA"></a> -<li><strong><strong>-A</strong></strong> Interpret <name> as an IP Address and do a node status +<p><a name="minusA"></a> +<p></p><dt><strong><strong>-A</strong></strong><dd> Interpret <name> as an IP Address and do a node status query on this address. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> Print a help (usage) message. -<p><br><a name="minusB"></a> -<li><strong><strong>-B broadcast address</strong></strong> Send the query to the given broadcast +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> Print a help (usage) message. +<p><a name="minusB"></a> +<p></p><dt><strong><strong>-B broadcast address</strong></strong><dd> Send the query to the given broadcast address. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as either auto-detected or defined in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter of the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. -<p><br><a name="minusU"></a> -<li><strong><strong>-U unicast address</strong></strong> Do a unicast query to the specified +<p><a name="minusU"></a> +<p></p><dt><strong><strong>-U unicast address</strong></strong><dd> Do a unicast query to the specified address or host <code>"unicast address"</code>. This option (along with the <a href="nmblookup.1.html#minusR"><strong>-R</strong></a> option) is needed to query a WINS server. -<p><br><a name="minusd"></a> -<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10. -<p><br>The default value if this parameter is not specified is zero. -<p><br>The higher this value, the more detail will be logged about the +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10. +<p>The default value if this parameter is not specified is zero. +<p>The higher this value, the more detail will be logged about the activities of <strong>nmblookup</strong>. At level 0, only critical errors and serious warnings will be logged. -<p><br>Levels above 1 will generate considerable amounts of log data, and +<p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of data, most of which is extremely cryptic. -<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log +<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. -<p><br><a name="minuss"></a> -<li><strong><strong>-s smb.conf</strong></strong> This parameter specifies the pathname to the +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s smb.conf</strong></strong><dd> This parameter specifies the pathname to the Samba configuration file, <a href="smb.conf.5.html"><strong>smb.conf</strong></a>. This file controls all aspects of the Samba setup on the machine. -<p><br><a name="minusi"></a> -<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that <strong>nmblookup</strong> will use +<p><a name="minusi"></a> +<p></p><dt><strong><strong>-i scope</strong></strong><dd> This specifies a NetBIOS scope that <strong>nmblookup</strong> will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are <em>very</em> rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with. -<p><br><a name="minusT"></a> -<li><strong><strong>-T</strong></strong> This causes any IP addresses found in the lookup to be +<p><a name="minusT"></a> +<p></p><dt><strong><strong>-T</strong></strong><dd> This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a DNS name, and printed out before each <code>"IP address NetBIOS name"</code> pair that is the normal output. -<p><br><a name="name"></a> -<li><strong><strong>name</strong></strong> This is the NetBIOS name being queried. Depending upon +<p><a name="name"></a> +<p></p><dt><strong><strong>name</strong></strong><dd> This is the NetBIOS name being queried. Depending upon the previous options this may be a NetBIOS name or IP address. If a NetBIOS name then the different name types may be specified by appending <code>#<type></code> to the name. This name may also be <code>"*"</code>, which will return all registered names within a broadcast area. -<p><br></ul> -<p><br><a name="EXAMPLES"></a> +<p></dl> +<p><a name="EXAMPLES"></a> <h2>EXAMPLES</h2> -<p><br><strong>nmblookup</strong> can be used to query a WINS server (in the same way +<p><strong>nmblookup</strong> can be used to query a WINS server (in the same way <strong>nslookup</strong> is used to query DNS servers). To query a WINS server, <strong>nmblookup</strong> must be called like this: -<p><br><code>nmblookup -U server -R 'name'</code> -<p><br>For example, running : -<p><br><code>nmblookup -U samba.org -R IRIX#1B'</code> -<p><br>would query the WINS server samba.org for the domain master +<p><code>nmblookup -U server -R 'name'</code> +<p>For example, running : +<p><code>nmblookup -U samba.org -R IRIX#1B'</code> +<p>would query the WINS server samba.org for the domain master browser (1B name type) for the IRIX workgroup. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="samba.7.html"><strong>samba (7)</strong></a>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, +<p><a href="samba.7.html"><strong>samba (7)</strong></a>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. -<p><br></body> +<p></body> </html> diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index f197ccfa32c..2e65ea42e2e 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -2,9 +2,10 @@ + <html><head><title>Samba (7)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -14,105 +15,104 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> Samba - A Windows SMB/CIFS fileserver for UNIX -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> <strong>Samba</strong> -<p><br><a name="DESCRIPTION"></a> +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>The Samba software suite is a collection of programs that implements +<p>The Samba software suite is a collection of programs that implements the Server Message Block(commonly abbreviated as SMB) protocol for UNIX systems. This protocol is sometimes also referred to as the Common Internet File System (CIFS), LanManager or NetBIOS protocol. -<p><br><a name="COMPONENTS"></a> +<p><a name="COMPONENTS"></a> <h2>COMPONENTS</h2> -<p><br>The Samba suite is made up of several components. Each component is +<p>The Samba suite is made up of several components. Each component is described in a separate manual page. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use. If the manual pages aren't clear enough then please send a patch or bug report -to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br><ul> -<p><br><li><strong><a href="smbd.8.html"><strong>smbd</strong></a></strong> <br> <br> The <a href="smbd.8.html"><strong>smbd</strong> +to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p><dl> +<p><p></p><dt><strong><a href="smbd.8.html"><strong>smbd</strong></a></strong><dd> <br> <br> The <a href="smbd.8.html"><strong>smbd</strong> (8)</a> daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file for this daemon is described in <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. -<p><br><li><strong><a href="nmbd.8.html"><strong>nmbd</strong></a></strong> <br> <br> The <a href="nmbd.8.html"><strong>nmbd</strong> +<p><p></p><dt><strong><a href="nmbd.8.html"><strong>nmbd</strong></a></strong><dd> <br> <br> The <a href="nmbd.8.html"><strong>nmbd</strong> (8)</a> daemon provides NetBIOS nameserving and browsing support. The configuration file for this daemon is described in <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. -<p><br><li><strong><a href="smbclient.1.html"><strong>smbclient</strong></a></strong> <br> <br> The <a href="smbclient.1.html"><strong>smbclient</strong> +<p><p></p><dt><strong><a href="smbclient.1.html"><strong>smbclient</strong></a></strong><dd> <br> <br> The <a href="smbclient.1.html"><strong>smbclient</strong> (1)</a> program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT). -<p><br><li><strong><a href="testparm.1.html"><strong>testparm</strong></a></strong> <br> <br> The <a href="testparm.1.html"><strong>testparm +<p><p></p><dt><strong><a href="testparm.1.html"><strong>testparm</strong></a></strong><dd> <br> <br> The <a href="testparm.1.html"><strong>testparm (1)</strong></a> utility allows you to test your <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> configuration file. -<p><br><li><strong><a href="testprns.1.html"><strong>testprns</strong></a></strong> <br> <br> the <a href="testprns.1.html"><strong>testprns +<p><p></p><dt><strong><a href="testprns.1.html"><strong>testprns</strong></a></strong><dd> <br> <br> the <a href="testprns.1.html"><strong>testprns (1)</strong></a> utility allows you to test the printers defined in your printcap file. -<p><br><li><strong><a href="smbstatus.1.html"><strong>smbstatus</strong></a></strong> <br> <br> The <a href="smbstatus.1.html"><strong>smbstatus</strong> +<p><p></p><dt><strong><a href="smbstatus.1.html"><strong>smbstatus</strong></a></strong><dd> <br> <br> The <a href="smbstatus.1.html"><strong>smbstatus</strong> (1)</a> utility allows you list current connections to the <a href="smbd.8.html"><strong>smbd (8)</strong></a> server. -<p><br><li><strong><a href="nmblookup.1.html"><strong>nmblookup</strong></a></strong> <br> <br> the +<p><p></p><dt><strong><a href="nmblookup.1.html"><strong>nmblookup</strong></a></strong><dd> <br> <br> the <a href="nmblookup.1.html"><strong>nmblookup (1)</strong></a> utility allows NetBIOS name queries to be made from the UNIX machine. -<p><br><li><strong><a href="make_smbcodepage.1.html"><strong>make_smbcodepage</strong></a></strong> <br> <br> The +<p><p></p><dt><strong><a href="make_smbcodepage.1.html"><strong>make_smbcodepage</strong></a></strong><dd> <br> <br> The <a href="make_smbcodepage.1.html"><strong>make_smbcodepage (1)</strong></a> utility allows you to create SMB code page definition files for your <a href="smbd.8.html"><strong>smbd (8)</strong></a> server. -<p><br><li><strong><a href="smbpasswd.8.html"><strong>smbpasswd</strong></a></strong> <br> <br> The <a href="smbpasswd.8.html"><strong>smbpasswd +<p><p></p><dt><strong><a href="smbpasswd.8.html"><strong>smbpasswd</strong></a></strong><dd> <br> <br> The <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a> utility allows you to change SMB encrypted passwords on Samba and Windows NT(tm) servers. -<p><br></ul> -<p><br><a name="AVAILABILITY"></a> +<p></dl> +<p><a name="AVAILABILITY"></a> <h2>AVAILABILITY</h2> -<p><br>The Samba software suite is licensed under the GNU Public License +<p>The Samba software suite is licensed under the GNU Public License (GPL). A copy of that license should have come with the package in the file COPYING. You are encouraged to distribute copies of the Samba suite, but please obey the terms of this license. -<p><br>The latest version of the Samba suite can be obtained via anonymous +<p>The latest version of the Samba suite can be obtained via anonymous ftp from samba.org in the directory pub/samba/. It is also available on several mirror sites worldwide. -<p><br>You may also find useful information about Samba on the newsgroup +<p>You may also find useful information about Samba on the newsgroup comp.protocols.smb and the Samba mailing list. Details on how to join the mailing list are given in the README file that comes with Samba. -<p><br>If you have access to a WWW viewer (such as Netscape or Mosaic) then +<p>If you have access to a WWW viewer (such as Netscape or Mosaic) then you will also find lots of useful information, including back issues of the Samba mailing list, at <a href="http://samba.org/samba/">http://samba.org/samba/</a>. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="CONTRIBUTIONS"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="CONTRIBUTIONS"></a> <h2>CONTRIBUTIONS</h2> -<p><br>If you wish to contribute to the Samba project, then I suggest you +<p>If you wish to contribute to the Samba project, then I suggest you join the Samba mailing list at <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. See the Web page at <a href="http://samba.org/listproc">http://samba.org/listproc</a> for details on how to do this. -<p><br>If you have patches to submit or bugs to report then you may mail them -directly to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Note, however, that due to +<p>If you have patches to submit or bugs to report then you may mail them +directly to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Note, however, that due to the enormous popularity of this package the Samba Team may take some time to respond to mail. We prefer patches in <em>diff -u</em> format. -<p><br><a name="CREDITS"></a> +<p><a name="CREDITS"></a> <h2>CREDITS</h2> -<p><br>Contributors to the project are now too numerous to mention here but +<p>Contributors to the project are now too numerous to mention here but all deserve the thanks of all Samba users. To see a full list, look at <a href="ftp://samba.org/pub/samba/alpha/change-log">ftp://samba.org/pub/samba/alpha/change-log</a> for the pre-CVS changes and at @@ -120,21 +120,21 @@ for the pre-CVS changes and at for the contributors to Samba post-CVS. CVS is the Open Source source code control system used by the Samba Team to develop Samba. The project would have been unmanageable without it. -<p><br>In addition, several commercial organizations now help fund the Samba +<p>In addition, several commercial organizations now help fund the Samba Team with money and equipment. For details see the Samba Web pages at <a href="http://samba.org/samba/samba-thanks.html">http://samba.org/samba/samba-thanks.html</a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. </body> </html> diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index adda876afdf..d01333bf048 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -3,6 +3,7 @@ + <html><head><title>smb.conf (5)</title> <link rev="made" href="mailto:samba@samba.org"> @@ -15,81 +16,80 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smb.conf - The configuration file for the Samba suite -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smb.conf</strong> The <strong>smb.conf</strong> file is a configuration file for the +<p><strong>smb.conf</strong> The <strong>smb.conf</strong> file is a configuration file for the Samba suite. <strong>smb.conf</strong> contains runtime configuration information for the Samba programs. The <strong>smb.conf</strong> file is designed to be configured and administered by the <a href="swat.8.html"><strong>swat (8)</strong></a> program. The complete description of the file format and possible parameters held within are here for reference purposes. -<p><br><a name="FILEFORMAT"></a> +<p><a name="FILEFORMAT"></a> <h2>FILE FORMAT</h2> -<p><br>The file consists of sections and parameters. A section begins with +<p>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 -<p><br><code>'name = value'</code> -<p><br>The file is line-based - that is, each newline-terminated line +<p><code>'name = value'</code> +<p>The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter. -<p><br>Section and parameter names are not case sensitive. -<p><br>Only the first equals sign in a parameter is significant. Whitespace +<p>Section and parameter names are not case sensitive. +<p>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. -<p><br>Any line beginning with a semicolon (';') or a hash ('#') character is +<p>Any line beginning with a semicolon (';') or a hash ('#') character is ignored, as are lines containing only whitespace. -<p><br>Any line ending in a <code>'\'</code> is "continued" on the next line in the +<p>Any line ending in a <code>'\'</code> is "continued" on the next line in the customary UNIX fashion. -<p><br>The values following the equals sign in parameters are all either a +<p>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. -<p><br><a name="SECTIONDESCRIPTIONS"></a> +<p><a name="SECTIONDESCRIPTIONS"></a> <h2>SECTION DESCRIPTIONS</h2> -<p><br>Each section in the configuration file (except for the -<a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section) describes a shared resource (known +<p>Each section in the configuration file (except for the +<a href="smb.conf.5.html#global"><strong>[global]</strong></a> section) describes a shared resource (known as a <em>"share"</em>). The section name is the name of the shared resource and the parameters within the section define the shares attributes. -<p><br>There are three special sections, <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a>, -<a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="../yodldocs/smb.conf.5.html#printers"><strong>[printers]</strong></a>, which are -described under <a href="../yodldocs/smb.conf.5.html#SPECIALSECTIONS"><strong>'special sections'</strong></a>. The +<p>There are three special sections, <a href="smb.conf.5.html#global"><strong>[global]</strong></a>, +<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a>, which are +described under <a href="smb.conf.5.html#SPECIALSECTIONS"><strong>'special sections'</strong></a>. The following notes apply to ordinary section descriptions. -<p><br>A share consists of a directory to which access is being given plus +<p>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. -<p><br>Sections are either filespace services (used by the client as an +<p>Sections are either filespace 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). -<p><br>Sections may be designated <a href="../yodldocs/smb.conf.5.html#guestok"><strong>guest</strong></a> services, in which +<p>Sections may be designated <a href="smb.conf.5.html#guestok"><strong>guest</strong></a> services, in which case no password is required to access them. A specified UNIX -<a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>guest account</strong></a> is used to define access +<a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a> is used to define access privileges in this case. -<p><br>Sections other than guest services will require a password to access +<p>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 <a href="../yodldocs/smb.conf.5.html#user"><strong>"user="</strong></a> option in +check against the password using the <a href="smb.conf.5.html#user"><strong>"user="</strong></a> option in the share definition. For modern clients such as Windows 95/98 and Windows NT, this should not be necessary. -<p><br>Note that the access rights granted by the server are masked by the +<p>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. -<p><br>The following sample section defines a file space share. The user has +<p>The following sample section defines a file space share. The user has write access to the path <code>/home/bar</code>. The share is accessed via the share name "foo": -<p><br><pre> +<p><pre> [foo] @@ -99,12 +99,12 @@ the share name "foo": </pre> -<p><br>The following sample section defines a printable share. The share +<p>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 -<a href="../yodldocs/smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> parameter means access will be permitted +<a href="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> parameter means access will be permitted as the default guest user (specified elsewhere): -<p><br><pre> +<p><pre> [aprinter] path = /usr/spool/public @@ -114,93 +114,93 @@ as the default guest user (specified elsewhere): </pre> -<p><br><a name="SPECIALSECTIONS"></a> +<p><a name="SPECIALSECTIONS"></a> <h2>SPECIAL SECTIONS</h2> -<p><br><ul> -<p><br><a name="global"></a> -<li><strong><strong>The [global] section</strong></strong> -<p><br>Parameters in this section apply to the server as a whole, or are +<p><dl> +<p><a name="global"></a> +<p></p><dt><strong><strong>The [global] section</strong></strong><dd> +<p>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 <a href="../yodldocs/smb.conf.5.html#PARAMETERS"><strong>'PARAMETERS'</strong></a> for more +items. See the notes under <a href="smb.conf.5.html#PARAMETERS"><strong>'PARAMETERS'</strong></a> for more information. -<p><br><a name="homes"></a> -<li><strong><strong>The [homes] section</strong></strong> -<p><br>If a section called <code>'homes'</code> is included in the configuration file, +<p><a name="homes"></a> +<p></p><dt><strong><strong>The [homes] section</strong></strong><dd> +<p>If a section called <code>'homes'</code> is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server. -<p><br>When the connection request is made, the existing sections are +<p>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. -<p><br>Some modifications are then made to the newly created share: -<p><br><ul> -<p><br><li > The share name is changed from <code>'homes'</code> to the located +<p>Some modifications are then made to the newly created share: +<p><dl> +<p><li > The share name is changed from <code>'homes'</code> to the located username -<p><br><li > If no path was given, the path is set to the user's home +<p><li > If no path was given, the path is set to the user's home directory. -<p><br></ul> -<p><br>If you decide to use a <a href="../yodldocs/smb.conf.5.html#path"><strong>path=</strong></a> line in your [homes] -section then you may find it useful to use the <a href="../yodldocs/smb.conf.5.html#percentS"><strong>%S</strong></a> +<p></dl> +<p>If you decide to use a <a href="smb.conf.5.html#path"><strong>path=</strong></a> line in your [homes] +section then you may find it useful to use the <a href="smb.conf.5.html#percentS"><strong>%S</strong></a> macro. For example : -<p><br><code>path=/data/pchome/%S</code> -<p><br>would be useful if you have different home directories for your PCs +<p><code>path=/data/pchome/%S</code> +<p>would be useful if you have different home directories for your PCs than for UNIX access. -<p><br>This is a fast and simple way to give a large number of clients access +<p>This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss. -<p><br>A similar process occurs if the requested section name is <code>"homes"</code>, +<p>A similar process occurs if the requested section name is <code>"homes"</code>, 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. -<p><br>The [homes] section can specify all the parameters a normal service +<p>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: -<p><br><pre> +<p><pre> [homes] writeable = yes </pre> -<p><br>An important point is that if guest access is specified in the [homes] +<p>An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients <strong>without a password</strong>. In the very unlikely event that this is -actually desirable, it would be wise to also specify <a href="../yodldocs/smb.conf.5.html#readonly"><strong>read only +actually desirable, it would be wise to also specify <a href="smb.conf.5.html#readonly"><strong>read only access</strong></a>. -<p><br>Note that the <a href="../yodldocs/smb.conf.5.html#browseable"><strong>browseable</strong></a> flag for auto home +<p>Note that the <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a> 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. -<p><br><a name="printers"></a> -<li><strong><strong>The [printers] section</strong></strong> -<p><br>This section works like <a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a>, but for printers. -<p><br>If a <strong>[printers]</strong> section occurs in the configuration file, users are +<p><a name="printers"></a> +<p></p><dt><strong><strong>The [printers] section</strong></strong><dd> +<p>This section works like <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a>, but for printers. +<p>If a <strong>[printers]</strong> section occurs in the configuration file, users are able to connect to any printer specified in the local host's printcap file. -<p><br>When a connection request is made, the existing sections are +<p>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 -<a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> section exists, it is used as described +<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> 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 <strong>[printers]</strong> section. -<p><br>A few modifications are then made to the newly created share: -<p><br><ul> -<p><br><li > The share name is set to the located printer name -<p><br><li > If no printer name was given, the printer name is set to the +<p>A few modifications are then made to the newly created share: +<p><dl> +<p><li > The share name is set to the located printer name +<p><li > If no printer name was given, the printer name is set to the located printer name -<p><br><li > If the share does not permit guest access and no username was +<p><li > If the share does not permit guest access and no username was given, the username is set to the located printer name. -<p><br></ul> -<p><br>Note that the <strong>[printers]</strong> service MUST be printable - if you specify +<p></dl> +<p>Note that the <strong>[printers]</strong> service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file. -<p><br>Typically the path specified would be that of a world-writeable spool +<p>Typically the path specified would be that of a world-writeable spool directory with the sticky bit set on it. A typical <strong>[printers]</strong> entry would look like this: -<p><br><pre> +<p><pre> [printers] path = /usr/spool/public @@ -209,499 +209,499 @@ would look like this: </pre> -<p><br>All aliases given for a printer in the printcap file are legitimate +<p>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: -<p><br><pre> +<p><pre> alias|alias|alias|alias... </pre> -<p><br>Each alias should be an acceptable printer name for your printing -subsystem. In the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section, specify the new +<p>Each alias should be an acceptable printer name for your printing +subsystem. In the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> 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. -<p><br>An alias, by the way, is defined as any component of the first entry +<p>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 ("|"). -<p><br>NOTE: On SYSV systems which use lpstat to determine what printers are -defined on the system you may be able to use <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>"printcap name = +<p>NOTE: On SYSV systems which use lpstat to determine what printers are +defined on the system you may be able to use <a href="smb.conf.5.html#printcapname"><strong>"printcap name = lpstat"</strong></a> to automatically obtain a list of -printers. See the <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>"printcap name"</strong></a> option for +printers. See the <a href="smb.conf.5.html#printcapname"><strong>"printcap name"</strong></a> option for more details. -<p><br></ul> -<p><br><a name="PARAMETERS"></a> +<p></dl> +<p><a name="PARAMETERS"></a> <h2>PARAMETERS</h2> -<p><br>Parameters define the specific attributes of sections. -<p><br>Some parameters are specific to the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section -(e.g., <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a>). Some parameters are usable in -all sections (e.g., <a href="../yodldocs/smb.conf.5.html#createmode"><strong>create mode</strong></a>). All others are +<p>Parameters define the specific attributes of sections. +<p>Some parameters are specific to the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section +(e.g., <a href="smb.conf.5.html#security"><strong>security</strong></a>). Some parameters are usable in +all sections (e.g., <a href="smb.conf.5.html#createmode"><strong>create mode</strong></a>). All others are permissible only in normal sections. For the purposes of the following -descriptions the <a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> and -<a href="../yodldocs/smb.conf.5.html#printers"><strong>[printers]</strong></a> sections will be considered normal. +descriptions the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and +<a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> sections will be considered normal. The letter <code>'G'</code> in parentheses indicates that a parameter is -specific to the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section. The letter <code>'S'</code> +specific to the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section. The letter <code>'S'</code> indicates that a parameter can be specified in a service specific section. Note that all <code>'S'</code> parameters can also be specified in the -<a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section - in which case they will define +<a href="smb.conf.5.html#global"><strong>[global]</strong></a> section - in which case they will define the default behavior for all services. -<p><br>Parameters are arranged here in alphabetical order - this may not +<p>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. -<p><br><a name="VARIABLESUBSTITUTIONS"></a> +<p><a name="VARIABLESUBSTITUTIONS"></a> <h2>VARIABLE SUBSTITUTIONS</h2> -<p><br>Many of the strings that are settable in the config file can take -substitutions. For example the option <a href="../yodldocs/smb.conf.5.html#path"><strong><code>"path = +<p>Many of the strings that are settable in the config file can take +substitutions. For example the option <a href="smb.conf.5.html#path"><strong><code>"path = /tmp/%u"</code></strong></a> would be interpreted as <code>"path = /tmp/john"</code> if the user connected with the username john. -<p><br>These substitutions are mostly noted in the descriptions below, but +<p>These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant. These are: -<p><br><ul> -<p><br><a name="percentS"></a> +<p><dl> +<p><a name="percentS"></a> <li > <strong>%S</strong> = the name of the current service, if any. -<p><br><a name="percentP"></a> +<p><a name="percentP"></a> <li > <strong>%P</strong> = the root directory of the current service, if any. -<p><br><a name="percentu"></a> +<p><a name="percentu"></a> <li > <strong>%u</strong> = user name of the current service, if any. -<p><br><a name="percentg"></a> -<li > <strong>%g</strong> = primary group name of <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a>. -<p><br><a name="percentU"></a> +<p><a name="percentg"></a> +<li > <strong>%g</strong> = primary group name of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>. +<p><a name="percentU"></a> <li > <strong>%U</strong> = session user name (the user name that the client wanted, not necessarily the same as the one they got). -<p><br><a name="percentG"></a> -<li > <strong>%G</strong> = primary group name of <a href="../yodldocs/smb.conf.5.html#percentU"><strong>%U</strong></a>. -<p><br><a name="percentH"></a> -<li > <strong>%H</strong> = the home directory of the user given by <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a>. -<p><br><a name="percentv"></a> +<p><a name="percentG"></a> +<li > <strong>%G</strong> = primary group name of <a href="smb.conf.5.html#percentU"><strong>%U</strong></a>. +<p><a name="percentH"></a> +<li > <strong>%H</strong> = the home directory of the user given by <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>. +<p><a name="percentv"></a> <li > <strong>%v</strong> = the Samba version. -<p><br><a name="percenth"></a> +<p><a name="percenth"></a> <li > <strong>%h</strong> = the internet hostname that Samba is running on. -<p><br><a name="percentm"></a> +<p><a name="percentm"></a> <li > <strong>%m</strong> = the NetBIOS name of the client machine (very useful). -<p><br><a name="percentL"></a> +<p><a name="percentL"></a> <li > <strong>%L</strong> = the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your server can have a "dual personality". -<p><br><a name="percentM"></a> +<p><a name="percentM"></a> <li > <strong>%M</strong> = the internet name of the client machine. -<p><br><a name="percentN"></a> +<p><a name="percentN"></a> <li > <strong>%N</strong> = the name of your NIS home directory server. This is obtained from your NIS auto.map entry. If you have not compiled Samba with the <strong>--with-automount</strong> option then this value will be the same -as <a href="../yodldocs/smb.conf.5.html#percentL"><strong>%L</strong></a>. -<p><br><a name="percentp"></a> +as <a href="smb.conf.5.html#percentL"><strong>%L</strong></a>. +<p><a name="percentp"></a> <li > <strong>%p</strong> = the path of the service's home directory, obtained from your NIS auto.map entry. The NIS auto.map entry is split up as "%N:%p". -<p><br><a name="percentR"></a> +<p><a name="percentR"></a> <li > <strong>%R</strong> = the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1. -<p><br><a name="percentd"></a> +<p><a name="percentd"></a> <li > <strong>%d</strong> = The process id of the current server process. -<p><br><a name="percenta"></a> +<p><a name="percenta"></a> <li > <strong>%a</strong> = the architecture of the remote machine. Only some are recognized, and those may not be 100% reliable. It currently recognizes Samba, WfWg, WinNT and Win95. Anything else will be known as "UNKNOWN". If it gets it wrong then sending a level 3 log to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a> should allow it to be fixed. -<p><br><a name="percentI"></a> +<p><a name="percentI"></a> <li > <strong>%I</strong> = The IP address of the client machine. -<p><br><a name="percentT"></a> +<p><a name="percentT"></a> <li > <strong>%T</strong> = the current date and time. -<p><br></ul> -<p><br>There are some quite creative things that can be done with these +<p></dl> +<p>There are some quite creative things that can be done with these substitutions and other smb.conf options. -<p><br><a name="NAMEMANGLING"></a> +<p><a name="NAMEMANGLING"></a> <h2>NAME MANGLING</h2> -<p><br>Samba supports <em>"name mangling"</em> so that DOS and Windows clients can +<p>Samba supports <em>"name mangling"</em> 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. -<p><br>There are several options that control the way mangling is performed, +<p>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. -<p><br>All of these options can be set separately for each service (or +<p>All of these options can be set separately for each service (or globally, of course). -<p><br>The options are: -<p><br><a name="manglecaseoption"></a> +<p>The options are: +<p><a name="manglecaseoption"></a> <strong>"mangle case = yes/no"</strong> controls if names that have characters that aren't of the "default" case are mangled. For example, if this is yes then a name like <code>"Mail"</code> would be mangled. Default <em>no</em>. -<p><br><a name="casesensitiveoption"></a> +<p><a name="casesensitiveoption"></a> <strong>"case sensitive = yes/no"</strong> controls whether filenames are case sensitive. If they aren't then Samba must do a filename search and match on passed names. Default <em>no</em>. -<p><br><a name="defaultcaseoption"></a> +<p><a name="defaultcaseoption"></a> <strong>"default case = upper/lower"</strong> controls what the default case is for new filenames. Default <em>lower</em>. -<p><br><a name="preservecaseoption"></a> +<p><a name="preservecaseoption"></a> <strong>"preserve case = yes/no"</strong> controls if new files are created with the case that the client passes, or if they are forced to be the <code>"default"</code> case. Default <em>Yes</em>. -<p><br><a name="shortpreservecaseoption"></a> -<p><br><strong>"short preserve case = yes/no"</strong> controls if new files which conform +<p><a name="shortpreservecaseoption"></a> +<p><strong>"short preserve case = yes/no"</strong> controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the <code>"default"</code> -case. This option can be use with <a href="../yodldocs/smb.conf.5.html#preservecaseoption"><strong>"preserve case = +case. This option can be use with <a href="smb.conf.5.html#preservecaseoption"><strong>"preserve case = yes"</strong></a> to permit long filenames to retain their case, while short names are lowered. Default <em>Yes</em>. -<p><br>By default, Samba 2.0 has the same semantics as a Windows NT +<p>By default, Samba 2.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving. -<p><br><a name="NOTEABOUTUSERNAMEPASSWORDVALIDATION"></a> +<p><a name="NOTEABOUTUSERNAMEPASSWORDVALIDATION"></a> <h2>NOTE ABOUT USERNAME/PASSWORD VALIDATION</h2> -<p><br>There are a number of ways in which a user can connect to a +<p>There are a number of ways in which a user can connect to a service. The server follows 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. If one of the steps pass then the following steps are not checked. -<p><br>If the service is marked <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only = yes"</strong></a> then +<p>If the service is marked <a href="smb.conf.5.html#guestonly"><strong>"guest only = yes"</strong></a> then steps 1 to 5 are skipped. -<p><br><ol> -<p><br><li> Step 1: If the client has passed a username/password pair and +<p><ol> +<p><li> 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 <code>\\server\service%username</code> method of passing a username. -<p><br><li> Step 2: If the client has previously registered a username with +<p><li> Step 2: If the client has previously registered a username with the system and now supplies a correct password for that username then the connection is allowed. -<p><br><li> Step 3: The client's netbios name and any previously used user +<p><li> Step 3: The client's netbios name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user. -<p><br><li> Step 4: If the client has previously validated a +<p><li> Step 4: If the client has previously validated a username/password pair with the server and the client has passed the validation token then that username is used. This step is skipped if -<a href="../yodldocs/smb.conf.5.html#revalidate"><strong>"revalidate = yes"</strong></a> for this service. -<p><br><li> Step 5: If a <a href="../yodldocs/smb.conf.5.html#user"><strong>"user = "</strong></a> field is given in the +<a href="smb.conf.5.html#revalidate"><strong>"revalidate = yes"</strong></a> for this service. +<p><li> Step 5: If a <a href="smb.conf.5.html#user"><strong>"user = "</strong></a> field is given in the smb.conf file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password -checking) with one of the usernames from the <a href="../yodldocs/smb.conf.5.html#user"><strong>user=</strong></a> +checking) with one of the usernames from the <a href="smb.conf.5.html#user"><strong>user=</strong></a> field then the connection is made as the username in the -<a href="../yodldocs/smb.conf.5.html#user"><strong>"user="</strong></a> line. If one of the username in the -<a href="../yodldocs/smb.conf.5.html#user"><strong>user=</strong></a> list begins with a <code>'@'</code> then that name +<a href="smb.conf.5.html#user"><strong>"user="</strong></a> line. If one of the username in the +<a href="smb.conf.5.html#user"><strong>user=</strong></a> list begins with a <code>'@'</code> then that name expands to a list of names in the group of the same name. -<p><br><li> Step 6: If the service is a guest service then a connection is -made as the username given in the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account +<p><li> Step 6: If the service is a guest service then a connection is +made as the username given in the <a href="smb.conf.5.html#guestaccount"><strong>"guest account ="</strong></a> for the service, irrespective of the supplied password. -<p><br></ol> -<p><br><a name="COMPLETELISTOFGLOBALPARAMETERS"></a> +<p></ol> +<p><a name="COMPLETELISTOFGLOBALPARAMETERS"></a> <h2>COMPLETE LIST OF GLOBAL PARAMETERS</h2> -<p><br>Here is a list of all global parameters. See the section of each +<p>Here is a list of all global parameters. See the section of each parameter for details. Note that some are synonyms. -<p><br><ul> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#adduserscript"><strong>add user script</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#allowtrusteddomains"><strong>allow trusted domains</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#announceas"><strong>announce as</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#announceversion"><strong>announce version</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#autoservices"><strong>auto services</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#bindinterfacesonly"><strong>bind interfaces only</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#browselist"><strong>browse list</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#changenotifytimeout"><strong>change notify timeout</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#characterset"><strong>character set</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#codingsystem"><strong>coding system</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#configfile"><strong>config file</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#deadtime"><strong>deadtime</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#debughirestimestamp"><strong>debug hires timestamp</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#debugpid"><strong>debug pid</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#debuguid"><strong>debug uid</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#debuglevel"><strong>debug level</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#default"><strong>default</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#defaultservice"><strong>default service</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#deleteuserscript"><strong>delete user script</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#dfreecommand"><strong>dfree command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#dnsproxy"><strong>dns proxy</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainadmingroup"><strong>domain admin group</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainadminusers"><strong>domain admin users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domaingroups"><strong>domain groups</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainguestgroup"><strong>domain guest group</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainguestusers"><strong>domain guest users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>domain logons</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#domainmaster"><strong>domain master</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>encrypt passwords</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#getwdcache"><strong>getwd cache</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#homedirmap"><strong>homedir map</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#hostsequiv"><strong>hosts equiv</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#interfaces"><strong>interfaces</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#keepalive"><strong>keepalive</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldapfilter"><strong>ldap filter</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldapport"><strong>ldap port</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldaproot"><strong>ldap root</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldapserver"><strong>ldap server</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ldapsuffix"><strong>ldap suffix</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>lm announce</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lminterval"><strong>lm interval</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#loadprinters"><strong>load printers</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#localmaster"><strong>local master</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lockdir"><strong>lock dir</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lockdirectory"><strong>lock directory</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#logfile"><strong>log file</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#loglevel"><strong>log level</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#logondrive"><strong>logon drive</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#logonhome"><strong>logon home</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#logonpath"><strong>logon path</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#logonscript"><strong>logon script</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lpqcachetime"><strong>lpq cache time</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#machinepasswordtimeout"><strong>machine password timeout</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#mangledstack"><strong>mangled stack</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maptoguest"><strong>map to guest</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxdisksize"><strong>max disk size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxlogsize"><strong>max log size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxmux"><strong>max mux</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxopenfiles"><strong>max open files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxpacket"><strong>max packet</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxttl"><strong>max ttl</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxwinsttl"><strong>max wins ttl</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxxmit"><strong>max xmit</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#messagecommand"><strong>message command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#minpasswdlength"><strong>min passwd length</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#minpasswordlength"><strong>min password length</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#minwinsttl"><strong>min wins ttl</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#netbiosaliases"><strong>netbios aliases</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#netbiosname"><strong>netbios name</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#netbiosscope"><strong>netbios scope</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#nishomedir"><strong>nis homedir</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ntaclsupport"><strong>nt acl support</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ntpipesupport"><strong>nt pipe support</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ntsmbsupport"><strong>nt smb support</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#olelockingcompatibility"><strong>ole locking compatibility</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#oplockbreakwaittime"><strong>oplock break wait time</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#oslevel"><strong>os level</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#packetsize"><strong>packet size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#panicaction"><strong>panic action</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#passwdchat"><strong>passwd chat</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#passwdchatdebug"><strong>passwd chat debug</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>passwd program</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#passwordlevel"><strong>password level</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>password server</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preferedmaster"><strong>prefered master</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preferredmaster"><strong>preferred master</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preload"><strong>preload</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printcap"><strong>printcap</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>printcap name</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printerdriverfile"><strong>printer driver file</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#protocol"><strong>protocol</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readbmpx"><strong>read bmpx</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readprediction"><strong>read prediction</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readraw"><strong>read raw</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readsize"><strong>read size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#remoteannounce"><strong>remote announce</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#remotebrowsesync"><strong>remote browse sync</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#restrictanonymous"><strong>restrict anonymous</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#root"><strong>root</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#rootdir"><strong>root dir</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#rootdirectory"><strong>root directory</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#serverstring"><strong>server string</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sharedmemsize"><strong>shared mem size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#smbpasswdfile"><strong>smb passwd file</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#smbrun"><strong>smbrun</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#socketaddress"><strong>socket address</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#socketoptions"><strong>socket options</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sourceenvironment"><strong>source environment</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#ssl"><strong>ssl</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslCAcertDir"><strong>ssl CA certDir</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslCAcertFile"><strong>ssl CA certFile</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslciphers"><strong>ssl ciphers</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslclientcert"><strong>ssl client cert</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslclientkey"><strong>ssl client key</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslcompatibility"><strong>ssl compatibility</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslhosts"><strong>ssl hosts</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslhostsresign"><strong>ssl hosts resign</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslrequireclientcert"><strong>ssl require clientcert</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslrequireservercert"><strong>ssl require servercert</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslservercert"><strong>ssl server cert</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslserverkey"><strong>ssl server key</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sslversion"><strong>ssl version</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#statcache"><strong>stat cache</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#statcachesize"><strong>stat cache size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#stripdot"><strong>strip dot</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#syslog"><strong>syslog</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#syslogonly"><strong>syslog only</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#templatehomedir"><strong>template homedir</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#templateshell"><strong>template shell</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#timeoffset"><strong>time offset</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#timeserver"><strong>time server</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#timestamplogs"><strong>timestamp logs</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>unix password sync</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#unixrealname"><strong>unix realname</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#updateencrypted"><strong>update encrypted</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#userhosts"><strong>use rhosts</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#usernamelevel"><strong>username level</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#usernamemap"><strong>username map</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#utmpdirectory"><strong>utmp directory</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#validchars"><strong>valid chars</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winbindcachetime"><strong>winbind cache time</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winbindgid"><strong>winbind gid</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winbinduid"><strong>winbind uid</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winshook"><strong>wins hook</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winsproxy"><strong>wins proxy</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winsserver"><strong>wins server</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#winssupport"><strong>wins support</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writeraw"><strong>write raw</strong></a> -<p><br></ul> -<p><br><a name="COMPLETELISTOFSERVICEPARAMETERS"></a> +<p><dl> +<p><li > <a href="smb.conf.5.html#adduserscript"><strong>add user script</strong></a> +<p><li > <a href="smb.conf.5.html#allowtrusteddomains"><strong>allow trusted domains</strong></a> +<p><li > <a href="smb.conf.5.html#announceas"><strong>announce as</strong></a> +<p><li > <a href="smb.conf.5.html#announceversion"><strong>announce version</strong></a> +<p><li > <a href="smb.conf.5.html#autoservices"><strong>auto services</strong></a> +<p><li > <a href="smb.conf.5.html#bindinterfacesonly"><strong>bind interfaces only</strong></a> +<p><li > <a href="smb.conf.5.html#browselist"><strong>browse list</strong></a> +<p><li > <a href="smb.conf.5.html#changenotifytimeout"><strong>change notify timeout</strong></a> +<p><li > <a href="smb.conf.5.html#characterset"><strong>character set</strong></a> +<p><li > <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> +<p><li > <a href="smb.conf.5.html#codingsystem"><strong>coding system</strong></a> +<p><li > <a href="smb.conf.5.html#configfile"><strong>config file</strong></a> +<p><li > <a href="smb.conf.5.html#deadtime"><strong>deadtime</strong></a> +<p><li > <a href="smb.conf.5.html#debughirestimestamp"><strong>debug hires timestamp</strong></a> +<p><li > <a href="smb.conf.5.html#debugpid"><strong>debug pid</strong></a> +<p><li > <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> +<p><li > <a href="smb.conf.5.html#debuguid"><strong>debug uid</strong></a> +<p><li > <a href="smb.conf.5.html#debuglevel"><strong>debug level</strong></a> +<p><li > <a href="smb.conf.5.html#default"><strong>default</strong></a> +<p><li > <a href="smb.conf.5.html#defaultservice"><strong>default service</strong></a> +<p><li > <a href="smb.conf.5.html#deleteuserscript"><strong>delete user script</strong></a> +<p><li > <a href="smb.conf.5.html#dfreecommand"><strong>dfree command</strong></a> +<p><li > <a href="smb.conf.5.html#dnsproxy"><strong>dns proxy</strong></a> +<p><li > <a href="smb.conf.5.html#domainadmingroup"><strong>domain admin group</strong></a> +<p><li > <a href="smb.conf.5.html#domainadminusers"><strong>domain admin users</strong></a> +<p><li > <a href="smb.conf.5.html#domaingroups"><strong>domain groups</strong></a> +<p><li > <a href="smb.conf.5.html#domainguestgroup"><strong>domain guest group</strong></a> +<p><li > <a href="smb.conf.5.html#domainguestusers"><strong>domain guest users</strong></a> +<p><li > <a href="smb.conf.5.html#domainlogons"><strong>domain logons</strong></a> +<p><li > <a href="smb.conf.5.html#domainmaster"><strong>domain master</strong></a> +<p><li > <a href="smb.conf.5.html#encryptpasswords"><strong>encrypt passwords</strong></a> +<p><li > <a href="smb.conf.5.html#getwdcache"><strong>getwd cache</strong></a> +<p><li > <a href="smb.conf.5.html#homedirmap"><strong>homedir map</strong></a> +<p><li > <a href="smb.conf.5.html#hostsequiv"><strong>hosts equiv</strong></a> +<p><li > <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> +<p><li > <a href="smb.conf.5.html#keepalive"><strong>keepalive</strong></a> +<p><li > <a href="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> +<p><li > <a href="smb.conf.5.html#ldapfilter"><strong>ldap filter</strong></a> +<p><li > <a href="smb.conf.5.html#ldapport"><strong>ldap port</strong></a> +<p><li > <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a> +<p><li > <a href="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a> +<p><li > <a href="smb.conf.5.html#ldapserver"><strong>ldap server</strong></a> +<p><li > <a href="smb.conf.5.html#ldapsuffix"><strong>ldap suffix</strong></a> +<p><li > <a href="smb.conf.5.html#lmannounce"><strong>lm announce</strong></a> +<p><li > <a href="smb.conf.5.html#lminterval"><strong>lm interval</strong></a> +<p><li > <a href="smb.conf.5.html#loadprinters"><strong>load printers</strong></a> +<p><li > <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a> +<p><li > <a href="smb.conf.5.html#lockdir"><strong>lock dir</strong></a> +<p><li > <a href="smb.conf.5.html#lockdirectory"><strong>lock directory</strong></a> +<p><li > <a href="smb.conf.5.html#logfile"><strong>log file</strong></a> +<p><li > <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a> +<p><li > <a href="smb.conf.5.html#logondrive"><strong>logon drive</strong></a> +<p><li > <a href="smb.conf.5.html#logonhome"><strong>logon home</strong></a> +<p><li > <a href="smb.conf.5.html#logonpath"><strong>logon path</strong></a> +<p><li > <a href="smb.conf.5.html#logonscript"><strong>logon script</strong></a> +<p><li > <a href="smb.conf.5.html#lpqcachetime"><strong>lpq cache time</strong></a> +<p><li > <a href="smb.conf.5.html#machinepasswordtimeout"><strong>machine password timeout</strong></a> +<p><li > <a href="smb.conf.5.html#mangledstack"><strong>mangled stack</strong></a> +<p><li > <a href="smb.conf.5.html#maptoguest"><strong>map to guest</strong></a> +<p><li > <a href="smb.conf.5.html#maxdisksize"><strong>max disk size</strong></a> +<p><li > <a href="smb.conf.5.html#maxlogsize"><strong>max log size</strong></a> +<p><li > <a href="smb.conf.5.html#maxmux"><strong>max mux</strong></a> +<p><li > <a href="smb.conf.5.html#maxopenfiles"><strong>max open files</strong></a> +<p><li > <a href="smb.conf.5.html#maxpacket"><strong>max packet</strong></a> +<p><li > <a href="smb.conf.5.html#maxttl"><strong>max ttl</strong></a> +<p><li > <a href="smb.conf.5.html#maxwinsttl"><strong>max wins ttl</strong></a> +<p><li > <a href="smb.conf.5.html#maxxmit"><strong>max xmit</strong></a> +<p><li > <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a> +<p><li > <a href="smb.conf.5.html#minpasswdlength"><strong>min passwd length</strong></a> +<p><li > <a href="smb.conf.5.html#minpasswordlength"><strong>min password length</strong></a> +<p><li > <a href="smb.conf.5.html#minwinsttl"><strong>min wins ttl</strong></a> +<p><li > <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> +<p><li > <a href="smb.conf.5.html#netbiosaliases"><strong>netbios aliases</strong></a> +<p><li > <a href="smb.conf.5.html#netbiosname"><strong>netbios name</strong></a> +<p><li > <a href="smb.conf.5.html#netbiosscope"><strong>netbios scope</strong></a> +<p><li > <a href="smb.conf.5.html#nishomedir"><strong>nis homedir</strong></a> +<p><li > <a href="smb.conf.5.html#ntaclsupport"><strong>nt acl support</strong></a> +<p><li > <a href="smb.conf.5.html#ntpipesupport"><strong>nt pipe support</strong></a> +<p><li > <a href="smb.conf.5.html#ntsmbsupport"><strong>nt smb support</strong></a> +<p><li > <a href="smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a> +<p><li > <a href="smb.conf.5.html#olelockingcompatibility"><strong>ole locking compatibility</strong></a> +<p><li > <a href="smb.conf.5.html#oplockbreakwaittime"><strong>oplock break wait time</strong></a> +<p><li > <a href="smb.conf.5.html#oslevel"><strong>os level</strong></a> +<p><li > <a href="smb.conf.5.html#packetsize"><strong>packet size</strong></a> +<p><li > <a href="smb.conf.5.html#panicaction"><strong>panic action</strong></a> +<p><li > <a href="smb.conf.5.html#passwdchat"><strong>passwd chat</strong></a> +<p><li > <a href="smb.conf.5.html#passwdchatdebug"><strong>passwd chat debug</strong></a> +<p><li > <a href="smb.conf.5.html#passwdprogram"><strong>passwd program</strong></a> +<p><li > <a href="smb.conf.5.html#passwordlevel"><strong>password level</strong></a> +<p><li > <a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a> +<p><li > <a href="smb.conf.5.html#preferedmaster"><strong>prefered master</strong></a> +<p><li > <a href="smb.conf.5.html#preferredmaster"><strong>preferred master</strong></a> +<p><li > <a href="smb.conf.5.html#preload"><strong>preload</strong></a> +<p><li > <a href="smb.conf.5.html#printcap"><strong>printcap</strong></a> +<p><li > <a href="smb.conf.5.html#printcapname"><strong>printcap name</strong></a> +<p><li > <a href="smb.conf.5.html#printerdriverfile"><strong>printer driver file</strong></a> +<p><li > <a href="smb.conf.5.html#protocol"><strong>protocol</strong></a> +<p><li > <a href="smb.conf.5.html#readbmpx"><strong>read bmpx</strong></a> +<p><li > <a href="smb.conf.5.html#readprediction"><strong>read prediction</strong></a> +<p><li > <a href="smb.conf.5.html#readraw"><strong>read raw</strong></a> +<p><li > <a href="smb.conf.5.html#readsize"><strong>read size</strong></a> +<p><li > <a href="smb.conf.5.html#remoteannounce"><strong>remote announce</strong></a> +<p><li > <a href="smb.conf.5.html#remotebrowsesync"><strong>remote browse sync</strong></a> +<p><li > <a href="smb.conf.5.html#restrictanonymous"><strong>restrict anonymous</strong></a> +<p><li > <a href="smb.conf.5.html#root"><strong>root</strong></a> +<p><li > <a href="smb.conf.5.html#rootdir"><strong>root dir</strong></a> +<p><li > <a href="smb.conf.5.html#rootdirectory"><strong>root directory</strong></a> +<p><li > <a href="smb.conf.5.html#security"><strong>security</strong></a> +<p><li > <a href="smb.conf.5.html#serverstring"><strong>server string</strong></a> +<p><li > <a href="smb.conf.5.html#sharedmemsize"><strong>shared mem size</strong></a> +<p><li > <a href="smb.conf.5.html#smbpasswdfile"><strong>smb passwd file</strong></a> +<p><li > <a href="smb.conf.5.html#smbrun"><strong>smbrun</strong></a> +<p><li > <a href="smb.conf.5.html#socketaddress"><strong>socket address</strong></a> +<p><li > <a href="smb.conf.5.html#socketoptions"><strong>socket options</strong></a> +<p><li > <a href="smb.conf.5.html#sourceenvironment"><strong>source environment</strong></a> +<p><li > <a href="smb.conf.5.html#ssl"><strong>ssl</strong></a> +<p><li > <a href="smb.conf.5.html#sslCAcertDir"><strong>ssl CA certDir</strong></a> +<p><li > <a href="smb.conf.5.html#sslCAcertFile"><strong>ssl CA certFile</strong></a> +<p><li > <a href="smb.conf.5.html#sslciphers"><strong>ssl ciphers</strong></a> +<p><li > <a href="smb.conf.5.html#sslclientcert"><strong>ssl client cert</strong></a> +<p><li > <a href="smb.conf.5.html#sslclientkey"><strong>ssl client key</strong></a> +<p><li > <a href="smb.conf.5.html#sslcompatibility"><strong>ssl compatibility</strong></a> +<p><li > <a href="smb.conf.5.html#sslhosts"><strong>ssl hosts</strong></a> +<p><li > <a href="smb.conf.5.html#sslhostsresign"><strong>ssl hosts resign</strong></a> +<p><li > <a href="smb.conf.5.html#sslrequireclientcert"><strong>ssl require clientcert</strong></a> +<p><li > <a href="smb.conf.5.html#sslrequireservercert"><strong>ssl require servercert</strong></a> +<p><li > <a href="smb.conf.5.html#sslservercert"><strong>ssl server cert</strong></a> +<p><li > <a href="smb.conf.5.html#sslserverkey"><strong>ssl server key</strong></a> +<p><li > <a href="smb.conf.5.html#sslversion"><strong>ssl version</strong></a> +<p><li > <a href="smb.conf.5.html#statcache"><strong>stat cache</strong></a> +<p><li > <a href="smb.conf.5.html#statcachesize"><strong>stat cache size</strong></a> +<p><li > <a href="smb.conf.5.html#stripdot"><strong>strip dot</strong></a> +<p><li > <a href="smb.conf.5.html#syslog"><strong>syslog</strong></a> +<p><li > <a href="smb.conf.5.html#syslogonly"><strong>syslog only</strong></a> +<p><li > <a href="smb.conf.5.html#templatehomedir"><strong>template homedir</strong></a> +<p><li > <a href="smb.conf.5.html#templateshell"><strong>template shell</strong></a> +<p><li > <a href="smb.conf.5.html#timeoffset"><strong>time offset</strong></a> +<p><li > <a href="smb.conf.5.html#timeserver"><strong>time server</strong></a> +<p><li > <a href="smb.conf.5.html#timestamplogs"><strong>timestamp logs</strong></a> +<p><li > <a href="smb.conf.5.html#unixpasswordsync"><strong>unix password sync</strong></a> +<p><li > <a href="smb.conf.5.html#unixrealname"><strong>unix realname</strong></a> +<p><li > <a href="smb.conf.5.html#updateencrypted"><strong>update encrypted</strong></a> +<p><li > <a href="smb.conf.5.html#userhosts"><strong>use rhosts</strong></a> +<p><li > <a href="smb.conf.5.html#usernamelevel"><strong>username level</strong></a> +<p><li > <a href="smb.conf.5.html#usernamemap"><strong>username map</strong></a> +<p><li > <a href="smb.conf.5.html#utmpdirectory"><strong>utmp directory</strong></a> +<p><li > <a href="smb.conf.5.html#validchars"><strong>valid chars</strong></a> +<p><li > <a href="smb.conf.5.html#winbindcachetime"><strong>winbind cache time</strong></a> +<p><li > <a href="smb.conf.5.html#winbindgid"><strong>winbind gid</strong></a> +<p><li > <a href="smb.conf.5.html#winbinduid"><strong>winbind uid</strong></a> +<p><li > <a href="smb.conf.5.html#winshook"><strong>wins hook</strong></a> +<p><li > <a href="smb.conf.5.html#winsproxy"><strong>wins proxy</strong></a> +<p><li > <a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> +<p><li > <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a> +<p><li > <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> +<p><li > <a href="smb.conf.5.html#writeraw"><strong>write raw</strong></a> +<p></dl> +<p><a name="COMPLETELISTOFSERVICEPARAMETERS"></a> <h2>COMPLETE LIST OF SERVICE PARAMETERS</h2> -<p><br>Here is a list of all service parameters. See the section of each +<p>Here is a list of all service parameters. See the section of each parameter for details. Note that some are synonyms. -<p><br><ul> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#adminusers"><strong>admin users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#allowhosts"><strong>allow hosts</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#alternatepermissions"><strong>alternate permissions</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#available"><strong>available</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#blockinglocks"><strong>blocking locks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#browsable"><strong>browsable</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#browseable"><strong>browseable</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#casesensitive"><strong>case sensitive</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#casesignames"><strong>casesignames</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#comment"><strong>comment</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#copy"><strong>copy</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#createmask"><strong>create mask</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#createmode"><strong>create mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#defaultcase"><strong>default case</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#deletereadonly"><strong>delete readonly</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#deletevetofiles"><strong>delete veto files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#denyhosts"><strong>deny hosts</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#directory"><strong>directory</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#directorymask"><strong>directory mask</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#directorymode"><strong>directory mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#dontdescend"><strong>dont descend</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#dosfiletimeresolution"><strong>dos filetime resolution</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#dosfiletimes"><strong>dos filetimes</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#exec"><strong>exec</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#fakedirectorycreatetimes"><strong>fake directory create times</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#fakeoplocks"><strong>fake oplocks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#followsymlinks"><strong>follow symlinks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forcegroup"><strong>force group</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#forceuser"><strong>force user</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#fstype"><strong>fstype</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#group"><strong>group</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>guest account</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#guestok"><strong>guest ok</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>guest only</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#hidedotfiles"><strong>hide dot files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#hidefiles"><strong>hide files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#include"><strong>include</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#inheritpermissions"><strong>inherit permissions</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>invalid users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#level2oplocks"><strong>level2 oplocks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#locking"><strong>locking</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lppausecommand"><strong>lppause command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lpqcommand"><strong>lpq command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lpresumecommand"><strong>lpresume command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#lprmcommand"><strong>lprm command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#magicoutput"><strong>magic output</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#magicscript"><strong>magic script</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#manglecase"><strong>mangle case</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#manglelocks"><strong>mangle locks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#mangledmap"><strong>mangled map</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#manglednames"><strong>mangled names</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#manglingchar"><strong>mangling char</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maparchive"><strong>map archive</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maphidden"><strong>map hidden</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#mapsystem"><strong>map system</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#maxconnections"><strong>max connections</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#minprintspace"><strong>min print space</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#onlyguest"><strong>only guest</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#onlyuser"><strong>only user</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#oplockcontentionlimit"><strong>oplock contention limit</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>oplocks</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#path"><strong>path</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#postexec"><strong>postexec</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#postscript"><strong>postscript</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preexec"><strong>preexec</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preexecclose"><strong>preexec close</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#preservecase"><strong>preserve case</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printcommand"><strong>print command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printok"><strong>print ok</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printable"><strong>printable</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printer"><strong>printer</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printerdriver"><strong>printer driver</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printerdriverlocation"><strong>printer driver location</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printername"><strong>printer name</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#printing"><strong>printing</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#public"><strong>public</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#queuepausecommand"><strong>queuepause command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#queueresumecommand"><strong>queueresume command</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readlist"><strong>read list</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#readonly"><strong>read only</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#revalidate"><strong>revalidate</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#rootpostexec"><strong>root postexec</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#rootpreexec"><strong>root preexec</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#rootpreexecclose"><strong>root preexec close</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#securitymask"><strong>security mask</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#setdirectory"><strong>set directory</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#sharemodes"><strong>share modes</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#shortpreservecase"><strong>short preserve case</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#status"><strong>status</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#strictlocking"><strong>strict locking</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#strictsync"><strong>strict sync</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#syncalways"><strong>sync always</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#user"><strong>user</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#username"><strong>username</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#users"><strong>users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#utmp"><strong>utmp</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#validusers"><strong>valid users</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>veto files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#vetooplockfiles"><strong>veto oplock files</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#volume"><strong>volume</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#widelinks"><strong>wide links</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writable"><strong>writable</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writecachesize"><strong>write cache size</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writelist"><strong>write list</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writeok"><strong>write ok</strong></a> -<p><br><li > <a href="../yodldocs/smb.conf.5.html#writeable"><strong>writeable</strong></a> -<p><br></ul> -<p><br><a name="EXPLANATIONOFEACHPARAMETER"></a> +<p><dl> +<p><li > <a href="smb.conf.5.html#adminusers"><strong>admin users</strong></a> +<p><li > <a href="smb.conf.5.html#allowhosts"><strong>allow hosts</strong></a> +<p><li > <a href="smb.conf.5.html#alternatepermissions"><strong>alternate permissions</strong></a> +<p><li > <a href="smb.conf.5.html#available"><strong>available</strong></a> +<p><li > <a href="smb.conf.5.html#blockinglocks"><strong>blocking locks</strong></a> +<p><li > <a href="smb.conf.5.html#browsable"><strong>browsable</strong></a> +<p><li > <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a> +<p><li > <a href="smb.conf.5.html#casesensitive"><strong>case sensitive</strong></a> +<p><li > <a href="smb.conf.5.html#casesignames"><strong>casesignames</strong></a> +<p><li > <a href="smb.conf.5.html#comment"><strong>comment</strong></a> +<p><li > <a href="smb.conf.5.html#copy"><strong>copy</strong></a> +<p><li > <a href="smb.conf.5.html#createmask"><strong>create mask</strong></a> +<p><li > <a href="smb.conf.5.html#createmode"><strong>create mode</strong></a> +<p><li > <a href="smb.conf.5.html#defaultcase"><strong>default case</strong></a> +<p><li > <a href="smb.conf.5.html#deletereadonly"><strong>delete readonly</strong></a> +<p><li > <a href="smb.conf.5.html#deletevetofiles"><strong>delete veto files</strong></a> +<p><li > <a href="smb.conf.5.html#denyhosts"><strong>deny hosts</strong></a> +<p><li > <a href="smb.conf.5.html#directory"><strong>directory</strong></a> +<p><li > <a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a> +<p><li > <a href="smb.conf.5.html#directorymode"><strong>directory mode</strong></a> +<p><li > <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a> +<p><li > <a href="smb.conf.5.html#dontdescend"><strong>dont descend</strong></a> +<p><li > <a href="smb.conf.5.html#dosfiletimeresolution"><strong>dos filetime resolution</strong></a> +<p><li > <a href="smb.conf.5.html#dosfiletimes"><strong>dos filetimes</strong></a> +<p><li > <a href="smb.conf.5.html#exec"><strong>exec</strong></a> +<p><li > <a href="smb.conf.5.html#fakedirectorycreatetimes"><strong>fake directory create times</strong></a> +<p><li > <a href="smb.conf.5.html#fakeoplocks"><strong>fake oplocks</strong></a> +<p><li > <a href="smb.conf.5.html#followsymlinks"><strong>follow symlinks</strong></a> +<p><li > <a href="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> +<p><li > <a href="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> +<p><li > <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security mode</strong></a> +<p><li > <a href="smb.conf.5.html#forcegroup"><strong>force group</strong></a> +<p><li > <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> +<p><li > <a href="smb.conf.5.html#forceuser"><strong>force user</strong></a> +<p><li > <a href="smb.conf.5.html#fstype"><strong>fstype</strong></a> +<p><li > <a href="smb.conf.5.html#group"><strong>group</strong></a> +<p><li > <a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a> +<p><li > <a href="smb.conf.5.html#guestok"><strong>guest ok</strong></a> +<p><li > <a href="smb.conf.5.html#guestonly"><strong>guest only</strong></a> +<p><li > <a href="smb.conf.5.html#hidedotfiles"><strong>hide dot files</strong></a> +<p><li > <a href="smb.conf.5.html#hidefiles"><strong>hide files</strong></a> +<p><li > <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> +<p><li > <a href="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a> +<p><li > <a href="smb.conf.5.html#include"><strong>include</strong></a> +<p><li > <a href="smb.conf.5.html#inheritpermissions"><strong>inherit permissions</strong></a> +<p><li > <a href="smb.conf.5.html#invalidusers"><strong>invalid users</strong></a> +<p><li > <a href="smb.conf.5.html#level2oplocks"><strong>level2 oplocks</strong></a> +<p><li > <a href="smb.conf.5.html#locking"><strong>locking</strong></a> +<p><li > <a href="smb.conf.5.html#lppausecommand"><strong>lppause command</strong></a> +<p><li > <a href="smb.conf.5.html#lpqcommand"><strong>lpq command</strong></a> +<p><li > <a href="smb.conf.5.html#lpresumecommand"><strong>lpresume command</strong></a> +<p><li > <a href="smb.conf.5.html#lprmcommand"><strong>lprm command</strong></a> +<p><li > <a href="smb.conf.5.html#magicoutput"><strong>magic output</strong></a> +<p><li > <a href="smb.conf.5.html#magicscript"><strong>magic script</strong></a> +<p><li > <a href="smb.conf.5.html#manglecase"><strong>mangle case</strong></a> +<p><li > <a href="smb.conf.5.html#manglelocks"><strong>mangle locks</strong></a> +<p><li > <a href="smb.conf.5.html#mangledmap"><strong>mangled map</strong></a> +<p><li > <a href="smb.conf.5.html#manglednames"><strong>mangled names</strong></a> +<p><li > <a href="smb.conf.5.html#manglingchar"><strong>mangling char</strong></a> +<p><li > <a href="smb.conf.5.html#maparchive"><strong>map archive</strong></a> +<p><li > <a href="smb.conf.5.html#maphidden"><strong>map hidden</strong></a> +<p><li > <a href="smb.conf.5.html#mapsystem"><strong>map system</strong></a> +<p><li > <a href="smb.conf.5.html#maxconnections"><strong>max connections</strong></a> +<p><li > <a href="smb.conf.5.html#minprintspace"><strong>min print space</strong></a> +<p><li > <a href="smb.conf.5.html#onlyguest"><strong>only guest</strong></a> +<p><li > <a href="smb.conf.5.html#onlyuser"><strong>only user</strong></a> +<p><li > <a href="smb.conf.5.html#oplockcontentionlimit"><strong>oplock contention limit</strong></a> +<p><li > <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> +<p><li > <a href="smb.conf.5.html#path"><strong>path</strong></a> +<p><li > <a href="smb.conf.5.html#postexec"><strong>postexec</strong></a> +<p><li > <a href="smb.conf.5.html#postscript"><strong>postscript</strong></a> +<p><li > <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a> +<p><li > <a href="smb.conf.5.html#preexecclose"><strong>preexec close</strong></a> +<p><li > <a href="smb.conf.5.html#preservecase"><strong>preserve case</strong></a> +<p><li > <a href="smb.conf.5.html#printcommand"><strong>print command</strong></a> +<p><li > <a href="smb.conf.5.html#printok"><strong>print ok</strong></a> +<p><li > <a href="smb.conf.5.html#printable"><strong>printable</strong></a> +<p><li > <a href="smb.conf.5.html#printer"><strong>printer</strong></a> +<p><li > <a href="smb.conf.5.html#printerdriver"><strong>printer driver</strong></a> +<p><li > <a href="smb.conf.5.html#printerdriverlocation"><strong>printer driver location</strong></a> +<p><li > <a href="smb.conf.5.html#printername"><strong>printer name</strong></a> +<p><li > <a href="smb.conf.5.html#printing"><strong>printing</strong></a> +<p><li > <a href="smb.conf.5.html#public"><strong>public</strong></a> +<p><li > <a href="smb.conf.5.html#queuepausecommand"><strong>queuepause command</strong></a> +<p><li > <a href="smb.conf.5.html#queueresumecommand"><strong>queueresume command</strong></a> +<p><li > <a href="smb.conf.5.html#readlist"><strong>read list</strong></a> +<p><li > <a href="smb.conf.5.html#readonly"><strong>read only</strong></a> +<p><li > <a href="smb.conf.5.html#revalidate"><strong>revalidate</strong></a> +<p><li > <a href="smb.conf.5.html#rootpostexec"><strong>root postexec</strong></a> +<p><li > <a href="smb.conf.5.html#rootpreexec"><strong>root preexec</strong></a> +<p><li > <a href="smb.conf.5.html#rootpreexecclose"><strong>root preexec close</strong></a> +<p><li > <a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a> +<p><li > <a href="smb.conf.5.html#setdirectory"><strong>set directory</strong></a> +<p><li > <a href="smb.conf.5.html#sharemodes"><strong>share modes</strong></a> +<p><li > <a href="smb.conf.5.html#shortpreservecase"><strong>short preserve case</strong></a> +<p><li > <a href="smb.conf.5.html#status"><strong>status</strong></a> +<p><li > <a href="smb.conf.5.html#strictlocking"><strong>strict locking</strong></a> +<p><li > <a href="smb.conf.5.html#strictsync"><strong>strict sync</strong></a> +<p><li > <a href="smb.conf.5.html#syncalways"><strong>sync always</strong></a> +<p><li > <a href="smb.conf.5.html#user"><strong>user</strong></a> +<p><li > <a href="smb.conf.5.html#username"><strong>username</strong></a> +<p><li > <a href="smb.conf.5.html#users"><strong>users</strong></a> +<p><li > <a href="smb.conf.5.html#utmp"><strong>utmp</strong></a> +<p><li > <a href="smb.conf.5.html#validusers"><strong>valid users</strong></a> +<p><li > <a href="smb.conf.5.html#vetofiles"><strong>veto files</strong></a> +<p><li > <a href="smb.conf.5.html#vetooplockfiles"><strong>veto oplock files</strong></a> +<p><li > <a href="smb.conf.5.html#volume"><strong>volume</strong></a> +<p><li > <a href="smb.conf.5.html#widelinks"><strong>wide links</strong></a> +<p><li > <a href="smb.conf.5.html#writable"><strong>writable</strong></a> +<p><li > <a href="smb.conf.5.html#writecachesize"><strong>write cache size</strong></a> +<p><li > <a href="smb.conf.5.html#writelist"><strong>write list</strong></a> +<p><li > <a href="smb.conf.5.html#writeok"><strong>write ok</strong></a> +<p><li > <a href="smb.conf.5.html#writeable"><strong>writeable</strong></a> +<p></dl> +<p><a name="EXPLANATIONOFEACHPARAMETER"></a> <h2>EXPLANATION OF EACH PARAMETER</h2> -<p><br><ul> -<p><br><a name="adduserscript"></a> -<li><strong><strong>add user script (G)</strong></strong> -<p><br>This is the full pathname to a script that will be run <em>AS ROOT</em> by +<p><dl> +<p><a name="adduserscript"></a> +<p></p><dt><strong><strong>add user script (G)</strong></strong><dd> +<p>This is the full pathname to a script that will be run <em>AS ROOT</em> by <a href="smbd.8.html"><strong>smbd (8)</strong></a> under special circumstances decribed below. -<p><br>Normally, a Samba server requires that UNIX users are created for all +<p>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 <a href="smbd.8.html"><strong>smbd</strong></a> to create the required UNIX users <em>ON DEMAND</em> when a user accesses the Samba server. -<p><br>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> or -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"add user script"</strong> +<p>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to +<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> or +<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"add user script"</strong> must be set to a full pathname for a script that will create a UNIX user given one argument of <strong>%u</strong>, which expands into the UNIX user name to create. -<p><br>When the Windows user attempts to access the Samba server, at +<p>When the Windows user attempts to access the Samba server, at <em>"login"</em>(session setup in the SMB protocol) time, -<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>password +<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a> and attempts to authenticate the given user with the given password. If the authentication succeeds then <a href="smbd.8.html"><strong>smbd</strong></a> attempts to find a UNIX user in the UNIX @@ -709,61 +709,61 @@ password database to map the Windows user into. If this lookup fails, and <strong>"add user script"</strong> is set then <a href="smbd.8.html"><strong>smbd</strong></a> will call the specified script <em>AS ROOT</em>, expanding any <strong>%u</strong> argument to be the user name to create. -<p><br>If this script successfully creates the user then +<p>If this script successfully creates the user then <a href="smbd.8.html"><strong>smbd</strong></a> will continue on as though the UNIX user already existed. In this way, UNIX users are dynamically created to match existing Windows NT accounts. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>security=server</strong></a>, -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>, <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>password -server</strong></a>, <a href="../yodldocs/smb.conf.5.html#deleteuserscript"><strong>delete user +<p>See also <a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a>, +<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>, <a href="smb.conf.5.html#passwordserver"><strong>password +server</strong></a>, <a href="smb.conf.5.html#deleteuserscript"><strong>delete user script</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> add user script = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> add user script = /usr/local/samba/bin/add_user %u</code> -<p><br><a name="adminusers"></a> -<li><strong><strong>admin users (S)</strong></strong> -<p><br>This is a list of users who will be granted administrative privileges +<p><a name="adminusers"></a> +<p></p><dt><strong><strong>admin users (S)</strong></strong><dd> +<p>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). -<p><br>You should use this option very carefully, as any user in this list +<p>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. -<p><br><strong>Default:</strong> <br> +<p><strong>Default:</strong> <br> <code> no admin users</code> -<p><br><strong>Example:</strong> <br> +<p><strong>Example:</strong> <br> <code> admin users = jason</code> -<p><br><a name="allowhosts"></a> -<li><strong><strong>allow hosts (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>. -<p><br><a name="allowtrusteddomains"></a> -<li><strong><strong>allow trusted domains (G)</strong></strong> -<p><br>This option only takes effect when the <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> +<p><a name="allowhosts"></a> +<p></p><dt><strong><strong>allow hosts (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>. +<p><a name="allowtrusteddomains"></a> +<p></p><dt><strong><strong>allow trusted domains (G)</strong></strong><dd> +<p>This option only takes effect when the <a href="smb.conf.5.html#security"><strong>security</strong></a> option is set to <strong>server</strong> or <strong>domain</strong>. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication. -<p><br>This is useful if you only want your Samba server to serve resources +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> allow trusted domains = Yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> allow trusted domains = No</code> -<p><br><a name="alternatepermissions"></a> -<li><strong><strong>alternate permissions (S)</strong></strong> -<p><br>This is a deprecated parameter. It no longer has any effect in Samba2.0. +<p><a name="alternatepermissions"></a> +<p></p><dt><strong><strong>alternate permissions (S)</strong></strong><dd> +<p>This is a deprecated parameter. It no longer has any effect in Samba2.0. In previous versions of Samba it affected the way the DOS "read only" attribute was mapped for a file. In Samba2.0 a file is marked "read only" if the UNIX file does not have the 'w' bit set for the owner of the file, regardless if the owner of the file is the currently logged on user or not. -<p><br><a name="announceas"></a> -<li><strong><strong>announce as (G)</strong></strong> -<p><br>This specifies what type of server <a href="nmbd.8.html"><strong>nmbd</strong></a> will +<p><a name="announceas"></a> +<p></p><dt><strong><strong>announce as (G)</strong></strong><dd> +<p>This specifies what type of server <a href="nmbd.8.html"><strong>nmbd</strong></a> will announce itself as, to a network neighborhood browse list. By default this is set to Windows NT. The valid options are : "NT", which is a synonym for "NT Server", "NT Server", "NT Workstation", "Win95" or @@ -771,49 +771,49 @@ synonym for "NT Server", "NT Server", "NT Workstation", "Win95" or and Windows for Workgroups respectively. Do not change this parameter unless you have a specific need to stop Samba appearing as an NT server as this may prevent Samba servers from participating as browser servers correctly. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> announce as = NT Server</code> -<p><br><strong>Example</strong> +<p><strong>Example</strong> <code> announce as = Win95</code> -<p><br><a name="announceversion"></a> -<li><strong><strong>announce version (G)</strong></strong> -<p><br>This specifies the major and minor version numbers that nmbd will use +<p><a name="announceversion"></a> +<p></p><dt><strong><strong>announce version (G)</strong></strong><dd> +<p>This specifies the major and minor version numbers that nmbd will use when announcing itself as a server. The default is 4.2. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> announce version = 4.2</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> announce version = 2.0</code> -<p><br><a name="autoservices"></a> -<li><strong><strong>auto services (G)</strong></strong> -<p><br>This is a list of services that you want to be automatically added to +<p><a name="autoservices"></a> +<p></p><dt><strong><strong>auto services (G)</strong></strong><dd> +<p>This is a list of services that you want to be automatically added to the browse lists. This is most useful for homes and printers services that would otherwise not be visible. -<p><br>Note that if you just want all printers in your printcap file loaded -then the <a href="../yodldocs/smb.conf.5.html#loadprinters"><strong>"load printers"</strong></a> option is easier. -<p><br><strong>Default:</strong> +<p>Note that if you just want all printers in your printcap file loaded +then the <a href="smb.conf.5.html#loadprinters"><strong>"load printers"</strong></a> option is easier. +<p><strong>Default:</strong> <code> no auto services</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> auto services = fred lp colorlp</code> -<p><br><a name="available"></a> -<li><strong><strong>available (S)</strong></strong> -<p><br>This parameter lets you <em>'turn off'</em> a service. If <code>'available = no'</code>, +<p><a name="available"></a> +<p></p><dt><strong><strong>available (S)</strong></strong><dd> +<p>This parameter lets you <em>'turn off'</em> a service. If <code>'available = no'</code>, then <em>ALL</em> attempts to connect to the service will fail. Such failures are logged. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> available = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> available = no</code> -<p><br><a name="bindinterfacesonly"></a> -<li><strong><strong>bind interfaces only (G)</strong></strong> -<p><br>This global parameter allows the Samba admin to limit what interfaces +<p><a name="bindinterfacesonly"></a> +<p></p><dt><strong><strong>bind interfaces only (G)</strong></strong><dd> +<p>This global parameter allows the Samba admin to limit what interfaces on a machine will serve smb requests. If affects file service <a href="smbd.8.html"><strong>smbd</strong></a> and name service <a href="nmbd.8.html"><strong>nmbd</strong></a> in slightly different ways. -<p><br>For name service it causes <a href="nmbd.8.html"><strong>nmbd</strong></a> to bind to ports +<p>For name service it causes <a href="nmbd.8.html"><strong>nmbd</strong></a> to bind to ports 137 and 138 on the interfaces listed in the -<a href="../yodldocs/smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> +<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter. <a href="nmbd.8.html"><strong>nmbd</strong></a> 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 @@ -822,376 +822,376 @@ sockets. If <strong>"bind interfaces only"</strong> is set then <a href="nmbd.8.html"><strong>nmbd</strong></a> 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 -<a href="../yodldocs/smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list. As unicast packets +<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list. As unicast packets are received on the other sockets it allows <a href="nmbd.8.html"><strong>nmbd</strong></a> to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the -<a href="../yodldocs/smb.conf.5.html#interfaces"><strong>"interfaces"</strong></a> list. IP Source address spoofing +<a href="smb.conf.5.html#interfaces"><strong>"interfaces"</strong></a> list. IP Source address spoofing does defeat this simple check, however so it must not be used seriously as a security feature for <a href="nmbd.8.html"><strong>nmbd</strong></a>. -<p><br>For file service it causes <a href="smbd.8.html"><strong>smbd</strong></a> to bind only to -the interface list given in the <a href="../yodldocs/smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> +<p>For file service it causes <a href="smbd.8.html"><strong>smbd</strong></a> to bind only to +the interface list given in the <a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter. This restricts the networks that <a href="smbd.8.html"><strong>smbd</strong></a> 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. -<p><br>If <strong>"bind interfaces only"</strong> is set then unless the network address -<em>127.0.0.1</em> is added to the <a href="../yodldocs/smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter +<p>If <strong>"bind interfaces only"</strong> is set then unless the network address +<em>127.0.0.1</em> is added to the <a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> and <a href="swat.8.html"><strong>swat</strong></a> may not work as expected due to the reasons covered below. -<p><br>To change a users SMB password, the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> +<p>To change a users SMB password, the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> by default connects to the <em>"localhost" - 127.0.0.1</em> address as an SMB client to issue the password change request. If <strong>"bind interfaces only"</strong> is set then unless the network address <em>127.0.0.1</em> is added to the -<a href="../yodldocs/smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list then +<a href="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list then <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> will fail to connect in it's default mode. <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> can be forced to use the primary IP interface of the local host by using its <a href="smbpasswd.8.html#minusr"><strong>"-r remote machine"</strong></a> parameter, with <strong>"remote machine"</strong> set to the IP name of the primary interface of the local host. -<p><br>The <a href="swat.8.html"><strong>swat</strong></a> status page tries to connect with +<p>The <a href="swat.8.html"><strong>swat</strong></a> status page tries to connect with <a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a> at the address <em>127.0.0.1</em> to determine if they are running. Not adding <em>127.0.0.1</em> will cause <a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a> to always show "not running" even if they really are. This can prevent <a href="swat.8.html"><strong>swat</strong></a> from starting/stopping/restarting <a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> bind interfaces only = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> bind interfaces only = True</code> -<p><br><a name="blockinglocks"></a> -<li><strong><strong>blocking locks (S)</strong></strong> -<p><br>This parameter controls the behavior of <a href="smbd.8.html"><strong>smbd</strong></a> when +<p><a name="blockinglocks"></a> +<p></p><dt><strong><strong>blocking locks (S)</strong></strong><dd> +<p>This parameter controls the behavior of <a href="smbd.8.html"><strong>smbd</strong></a> when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it. -<p><br>If this parameter is set and the lock range requested cannot be +<p>If this parameter is set and the lock range requested cannot be immediately satisfied, Samba 2.0 will internally queue the lock request, and periodically attempt to obtain the lock until the timeout period expires. -<p><br>If this parameter is set to "False", then Samba 2.0 will behave +<p>If this parameter is set to "False", then Samba 2.0 will behave as previous versions of Samba would and will fail the lock request immediately if the lock range cannot be obtained. -<p><br>This parameter can be set per share. -<p><br><strong>Default:</strong> +<p>This parameter can be set per share. +<p><strong>Default:</strong> <code> blocking locks = True</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> blocking locks = False</code> -<p><br><a name="browsable"></a> -<li><strong><strong>browsable (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#browseable"><strong>browseable</strong></a>. -<p><br><a name="browselist"></a> -<li><strong><strong>browse list(G)</strong></strong> -<p><br>This controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will serve a browse +<p><a name="browsable"></a> +<p></p><dt><strong><strong>browsable (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a>. +<p><a name="browselist"></a> +<p></p><dt><strong><strong>browse list(G)</strong></strong><dd> +<p>This controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will serve a browse list to a client doing a NetServerEnum call. Normally set to true. You should never need to change this. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> browse list = Yes</code> -<p><br><a name="browseable"></a> -<li><strong><strong>browseable</strong></strong> -<p><br>This controls whether this share is seen in the list of available +<p><a name="browseable"></a> +<p></p><dt><strong><strong>browseable</strong></strong><dd> +<p>This controls whether this share is seen in the list of available shares in a net view and in the browse list. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> browseable = Yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> browseable = No</code> -<p><br><a name="casesensitive"></a> -<li><strong><strong>case sensitive (S)</strong></strong> -<p><br>See the discussion in the section <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>. -<p><br><a name="casesignames"></a> -<li><strong><strong>casesignames (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. -<p><br><a name="changenotifytimeout"></a> -<li><strong><strong>change notify timeout (G)</strong></strong> -<p><br>One of the new NT SMB requests that Samba 2.0 supports is the +<p><a name="casesensitive"></a> +<p></p><dt><strong><strong>case sensitive (S)</strong></strong><dd> +<p>See the discussion in the section <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>. +<p><a name="casesignames"></a> +<p></p><dt><strong><strong>casesignames (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. +<p><a name="changenotifytimeout"></a> +<p></p><dt><strong><strong>change notify timeout (G)</strong></strong><dd> +<p>One of the new NT SMB requests that Samba 2.0 supports is the "ChangeNotify" requests. This SMB allows a client to tell a server to <em>"watch"</em> a particular directory for any changes and only reply to the SMB request when a change has occurred. Such constant scanning of a directory is expensive under UNIX, hence an <a href="smbd.8.html"><strong>smbd</strong></a> daemon only performs such a scan on each requested directory once every <strong>change notify timeout</strong> seconds. -<p><br><strong>change notify timeout</strong> is specified in units of seconds. -<p><br><strong>Default:</strong> +<p><strong>change notify timeout</strong> is specified in units of seconds. +<p><strong>Default:</strong> <code> change notify timeout = 60</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> change notify timeout = 300</code> -<p><br>Would change the scan time to every 5 minutes. -<p><br><a name="characterset"></a> -<li><strong><strong>character set (G)</strong></strong> -<p><br>This allows a smbd to map incoming filenames from a DOS Code page (see -the <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> parameter) to several +<p>Would change the scan time to every 5 minutes. +<p><a name="characterset"></a> +<p></p><dt><strong><strong>character set (G)</strong></strong><dd> +<p>This allows a smbd to map incoming filenames from a DOS Code page (see +the <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> parameter) to several built in UNIX character sets. The built in code page translations are: -<p><br><ul> -<p><br><li > <strong>ISO8859-1</strong> Western European UNIX character set. The parameter -<a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code +<p><dl> +<p><li > <strong>ISO8859-1</strong> Western European UNIX character set. The parameter +<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code page 850 if the <strong>character set</strong> parameter is set to iso8859-1 in order for the conversion to the UNIX character set to be done correctly. -<p><br><li > <strong>ISO8859-2</strong> Eastern European UNIX character set. The parameter -<a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code +<p><li > <strong>ISO8859-2</strong> Eastern European UNIX character set. The parameter +<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code page 852 if the <strong>character set</strong> parameter is set to ISO8859-2 in order for the conversion to the UNIX character set to be done correctly. -<p><br><li > <strong>ISO8859-5</strong> Russian Cyrillic UNIX character set. The parameter -<a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code +<p><li > <strong>ISO8859-5</strong> Russian Cyrillic UNIX character set. The parameter +<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code page 866 if the <strong>character set</strong> parameter is set to ISO8859-5 in order for the conversion to the UNIX character set to be done correctly. -<p><br><li > <strong>ISO8859-7</strong> Greek UNIX character set. The parameter -<a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code +<p><li > <strong>ISO8859-7</strong> Greek UNIX character set. The parameter +<a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code page 737 if the <strong>character set</strong> parameter is set to ISO8859-7 in order for the conversion to the UNIX character set to be done correctly. -<p><br><li > <strong>KOI8-R</strong> Alternate mapping for Russian Cyrillic UNIX -character set. The parameter <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code +<p><li > <strong>KOI8-R</strong> Alternate mapping for Russian Cyrillic UNIX +character set. The parameter <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code page 866 if the <strong>character set</strong> parameter is set to KOI8-R in order for the conversion to the UNIX character set to be done correctly. -<p><br></ul> -<p><br><em>BUG</em>. These MSDOS code page to UNIX character set mappings should +<p></dl> +<p><em>BUG</em>. These MSDOS code page to UNIX character set mappings should be dynamic, like the loading of MS DOS code pages, not static. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>. Normally this +<p>See also <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>. Normally this parameter is not set, meaning no filename translation is done. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> character set = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> character set = ISO8859-1</code> -<p><br><a name="clientcodepage"></a> -<li><strong><strong>client code page (G)</strong></strong> -<p><br>This parameter specifies the DOS code page that the clients accessing +<p><a name="clientcodepage"></a> +<p></p><dt><strong><strong>client code page (G)</strong></strong><dd> +<p>This parameter specifies the DOS code page that the clients accessing Samba are using. To determine what code page a Windows or DOS client is using, open a DOS command prompt and type the command "chcp". This will output the code page. The default for USA MS-DOS, Windows 95, and Windows NT releases is code page 437. The default for western european releases of the above operating systems is code page 850. -<p><br>This parameter tells <a href="smbd.8.html"><strong>smbd</strong></a> which of the +<p>This parameter tells <a href="smbd.8.html"><strong>smbd</strong></a> which of the <code>codepage.XXX</code> files to dynamically load on startup. These files, described more fully in the manual page <a href="make_smbcodepage.1.html"><strong>make_smbcodepage (1)</strong></a>, tell <a href="smbd.8.html"><strong>smbd</strong></a> how to map lower to upper case characters to provide the case insensitivity of filenames that Windows clients expect. -<p><br>Samba currently ships with the following code page files : -<p><br><ul> -<p><br><li > <strong>Code Page 437 - MS-DOS Latin US</strong> -<p><br><li > <strong>Code Page 737 - Windows '95 Greek</strong> -<p><br><li > <strong>Code Page 850 - MS-DOS Latin 1</strong> -<p><br><li > <strong>Code Page 852 - MS-DOS Latin 2</strong> -<p><br><li > <strong>Code Page 861 - MS-DOS Icelandic</strong> -<p><br><li > <strong>Code Page 866 - MS-DOS Cyrillic</strong> -<p><br><li > <strong>Code Page 932 - MS-DOS Japanese SJIS</strong> -<p><br><li > <strong>Code Page 936 - MS-DOS Simplified Chinese</strong> -<p><br><li > <strong>Code Page 949 - MS-DOS Korean Hangul</strong> -<p><br><li > <strong>Code Page 950 - MS-DOS Traditional Chinese</strong> -<p><br></ul> -<p><br>Thus this parameter may have any of the values 437, 737, 850, 852, +<p>Samba currently ships with the following code page files : +<p><dl> +<p><li > <strong>Code Page 437 - MS-DOS Latin US</strong> +<p><li > <strong>Code Page 737 - Windows '95 Greek</strong> +<p><li > <strong>Code Page 850 - MS-DOS Latin 1</strong> +<p><li > <strong>Code Page 852 - MS-DOS Latin 2</strong> +<p><li > <strong>Code Page 861 - MS-DOS Icelandic</strong> +<p><li > <strong>Code Page 866 - MS-DOS Cyrillic</strong> +<p><li > <strong>Code Page 932 - MS-DOS Japanese SJIS</strong> +<p><li > <strong>Code Page 936 - MS-DOS Simplified Chinese</strong> +<p><li > <strong>Code Page 949 - MS-DOS Korean Hangul</strong> +<p><li > <strong>Code Page 950 - MS-DOS Traditional Chinese</strong> +<p></dl> +<p>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 <a href="make_smbcodepage.1.html"><strong>make_smbcodepage (1)</strong></a> man page and write one. Please remember to donate it back to the Samba user community. -<p><br>This parameter co-operates with the <a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid +<p>This parameter co-operates with the <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter in determining what characters are valid in filenames and how capitalization is done. If you set both -this parameter and the <a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter +this parameter and the <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter the <strong>"client code page"</strong> parameter <em>MUST</em> be set before the -<a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter in the <strong>smb.conf</strong> -file. The <a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> string will then augment +<a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter in the <strong>smb.conf</strong> +file. The <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> string will then augment the character settings in the "client code page" parameter. -<p><br>If not set, <strong>"client code page"</strong> defaults to 850. -<p><br>See also : <a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> -<p><br><strong>Default:</strong> +<p>If not set, <strong>"client code page"</strong> defaults to 850. +<p>See also : <a href="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> +<p><strong>Default:</strong> <code> client code page = 850</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> client code page = 936</code> -<p><br><a name="codingsystem"></a> -<li><strong><strong>codingsystem (G)</strong></strong> -<p><br>This parameter is used to determine how incoming Shift-JIS Japanese -characters are mapped from the incoming <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client code +<p><a name="codingsystem"></a> +<p></p><dt><strong><strong>codingsystem (G)</strong></strong><dd> +<p>This parameter is used to determine how incoming Shift-JIS Japanese +characters are mapped from the incoming <a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> used by the client, into file names in the -UNIX filesystem. Only useful if <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client code +UNIX filesystem. Only useful if <a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> is set to 932 (Japanese Shift-JIS). -<p><br>The options are : -<p><br><ul> -<p><br><li > <strong>SJIS</strong> Shift-JIS. Does no conversion of the incoming filename. -<p><br><li > <strong>JIS8, J8BB, J8BH, J8@B, J8@J, J8@H </strong> Convert from incoming +<p>The options are : +<p><dl> +<p><li > <strong>SJIS</strong> Shift-JIS. Does no conversion of the incoming filename. +<p><li > <strong>JIS8, J8BB, J8BH, J8@B, J8@J, J8@H </strong> Convert from incoming Shift-JIS to eight bit JIS code with different shift-in, shift out codes. -<p><br><li > <strong>JIS7, J7BB, J7BH, J7@B, J7@J, J7@H </strong> Convert from incoming +<p><li > <strong>JIS7, J7BB, J7BH, J7@B, J7@J, J7@H </strong> Convert from incoming Shift-JIS to seven bit JIS code with different shift-in, shift out codes. -<p><br><li > <strong>JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </strong> Convert from incoming +<p><li > <strong>JUNET, JUBB, JUBH, JU@B, JU@J, JU@H </strong> Convert from incoming Shift-JIS to JUNET code with different shift-in, shift out codes. -<p><br><li > <strong>EUC</strong> Convert an incoming Shift-JIS character to EUC code. -<p><br><li > <strong>HEX</strong> Convert an incoming Shift-JIS character to a 3 byte hex +<p><li > <strong>EUC</strong> Convert an incoming Shift-JIS character to EUC code. +<p><li > <strong>HEX</strong> Convert an incoming Shift-JIS character to a 3 byte hex representation, i.e. <code>:AB</code>. -<p><br><li > <strong>CAP</strong> Convert an incoming Shift-JIS character to the 3 byte hex +<p><li > <strong>CAP</strong> Convert an incoming Shift-JIS character to the 3 byte hex representation used by the Columbia AppleTalk Program (CAP), i.e. <code>:AB</code>. This is used for compatibility between Samba and CAP. -<p><br></ul> -<p><br><a name="comment"></a> -<li><strong><strong>comment (S)</strong></strong> -<p><br>This is a text field that is seen next to a share when a client does a +<p></dl> +<p><a name="comment"></a> +<p></p><dt><strong><strong>comment (S)</strong></strong><dd> +<p>This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via "net view" to list what shares are available. -<p><br>If you want to set the string that is displayed next to the machine +<p>If you want to set the string that is displayed next to the machine name then see the server string command. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> No comment string</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> comment = Fred's Files</code> -<p><br><a name="configfile"></a> -<li><strong><strong>config file (G)</strong></strong> -<p><br>This allows you to override the config file to use, instead of the +<p><a name="configfile"></a> +<p></p><dt><strong><strong>config file (G)</strong></strong><dd> +<p>This allows you to override the config file to use, instead of the default (usually <strong>smb.conf</strong>). There is a chicken and egg problem here as this option is set in the config file! -<p><br>For this reason, if the name of the config file has changed when the +<p>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. -<p><br>This option takes the usual substitutions, which can be very useful. -<p><br>If the config file doesn't exist then it won't be loaded (allowing you +<p>This option takes the usual substitutions, which can be very useful. +<p>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). -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> config file = /usr/local/samba/lib/smb.conf.%m</code> -<p><br><a name="copy"></a> -<li><strong><strong>copy (S)</strong></strong> -<p><br>This parameter allows you to <em>'clone'</em> service entries. The specified +<p><a name="copy"></a> +<p></p><dt><strong><strong>copy (S)</strong></strong><dd> +<p>This parameter allows you to <em>'clone'</em> 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. -<p><br>This feature lets you set up a 'template' service and create similar +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> none</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> copy = otherservice</code> -<p><br><a name="createmask"></a> -<li><strong><strong>create mask (S)</strong></strong> -<p><br>A synonym for this parameter is <a href="../yodldocs/smb.conf.5.html#createmode"><strong>'create mode'</strong></a>. -<p><br>When a file is created, the necessary permissions are calculated +<p><a name="createmask"></a> +<p></p><dt><strong><strong>create mask (S)</strong></strong><dd> +<p>A synonym for this parameter is <a href="smb.conf.5.html#createmode"><strong>'create mode'</strong></a>. +<p>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 <em>*not*</em> set here will be removed from the modes set on a file when it is created. -<p><br>The default value of this parameter removes the 'group' and 'other' +<p>The default value of this parameter removes the 'group' and 'other' write and execute bits from the UNIX modes. -<p><br>Following this Samba will bit-wise 'OR' the UNIX mode created from +<p>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. -<p><br>This parameter does not affect directory modes. See the parameter -<a href="../yodldocs/smb.conf.5.html#directorymode"><strong>'directory mode'</strong></a> for details. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> parameter +<p>This parameter does not affect directory modes. See the parameter +<a href="smb.conf.5.html#directorymode"><strong>'directory mode'</strong></a> for details. +<p>See also the <a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> parameter for forcing particular mode bits to be set on created files. See also -the <a href="../yodldocs/smb.conf.5.html#directorymode"><strong>"directory mode"</strong></a> parameter for masking +the <a href="smb.conf.5.html#directorymode"><strong>"directory mode"</strong></a> parameter for masking mode bits on created directories. -See also the <a href="../yodldocs/smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. -<p><br><strong>Default:</strong> +See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. +<p><strong>Default:</strong> <code> create mask = 0744</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> create mask = 0775</code> -<p><br><a name="createmode"></a> -<li><strong><strong>create mode (S)</strong></strong> -<p><br>This is a synonym for <a href="../yodldocs/smb.conf.5.html#createmask"><strong>create mask</strong></a>. -<p><br><a name="deadtime"></a> -<li><strong><strong>deadtime (G)</strong></strong> -<p><br>The value of the parameter (a decimal integer) represents the number +<p><a name="createmode"></a> +<p></p><dt><strong><strong>create mode (S)</strong></strong><dd> +<p>This is a synonym for <a href="smb.conf.5.html#createmask"><strong>create mask</strong></a>. +<p><a name="deadtime"></a> +<p></p><dt><strong><strong>deadtime (G)</strong></strong><dd> +<p>The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected. The deadtime only takes effect if the number of open files is zero. -<p><br>This is useful to stop a server's resources being exhausted by a large +<p>This is useful to stop a server's resources being exhausted by a large number of inactive connections. -<p><br>Most clients have an auto-reconnect feature when a connection is +<p>Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users. -<p><br>Using this parameter with a timeout of a few minutes is recommended +<p>Using this parameter with a timeout of a few minutes is recommended for most systems. -<p><br>A deadtime of zero indicates that no auto-disconnection should be +<p>A deadtime of zero indicates that no auto-disconnection should be performed. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> deadtime = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> deadtime = 15</code> -<p><br><a name="debughirestimestamp"></a> -<li><strong><strong>debug hires timestamp (G)</strong></strong> -<p><br>Sometimes the timestamps in the log messages are needed with a +<p><a name="debughirestimestamp"></a> +<p></p><dt><strong><strong>debug hires timestamp (G)</strong></strong><dd> +<p>Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp message header when turned on. -<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> +<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> must be on for this to have an effect. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> debug hires timestamp = No</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> debug hires timestamp = Yes</code> -<p><br><a name="debugtimestamp"></a> -<li><strong><strong>debug timestamp (G)</strong></strong> -<p><br>Samba2.0 debug log messages are timestamped by default. If you are -running at a high <a href="../yodldocs/smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> these timestamps +<p><a name="debugtimestamp"></a> +<p></p><dt><strong><strong>debug timestamp (G)</strong></strong><dd> +<p>Samba2.0 debug log messages are timestamped by default. If you are +running at a high <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> these timestamps can be distracting. This boolean parameter allows timestamping to be turned off. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> debug timestamp = Yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> debug timestamp = No</code> -<p><br><a name="debugpid"></a> -<li><strong><strong>debug pid (G)</strong></strong> -<p><br>When using only one log file for more then one forked smbd-process +<p><a name="debugpid"></a> +<p></p><dt><strong><strong>debug pid (G)</strong></strong><dd> +<p>When using only one log file for more then one forked smbd-process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on. -<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> +<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> must be on for this to have an effect. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> debug pid = No</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> debug pid = Yes</code> -<p><br><a name="debuguid"></a> -<li><strong><strong>debug uid (G)</strong></strong> -<p><br>Samba is sometimes run as root and sometime run as the connected +<p><a name="debuguid"></a> +<p></p><dt><strong><strong>debug uid (G)</strong></strong><dd> +<p>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. -<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> +<p>Note that the parameter <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a> must be on for this to have an effect. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> debug uid = No</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> debug uid = Yes</code> -<p><br><a name="debuglevel"></a> -<li><strong><strong>debug level (G)</strong></strong> -<p><br>The value of the parameter (an integer) allows the debug level +<p><a name="debuglevel"></a> +<p></p><dt><strong><strong>debug level (G)</strong></strong><dd> +<p>The value of the parameter (an integer) allows the debug level (logging level) to be specified in the <strong>smb.conf</strong> file. This is to give greater flexibility in the configuration of the system. -<p><br>The default will be the debug level specified on the command line +<p>The default will be the debug level specified on the command line or level zero if none was specified. -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> debug level = 3</code> -<p><br><a name="default"></a> -<li><strong><strong>default (G)</strong></strong> -<p><br>A synonym for <a href="../yodldocs/smb.conf.5.html#defaultservice"><strong>default service</strong></a>. -<p><br><a name="defaultcase"></a> -<li><strong><strong>default case (S)</strong></strong> -<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>. Also note -the <a href="../yodldocs/smb.conf.5.html#shortpreservecase"><strong>"short preserve case"</strong></a> parameter. -<p><br><a name="defaultservice"></a> -<li><strong><strong>default service (G)</strong></strong> -<p><br>This parameter specifies the name of a service which will be connected +<p><a name="default"></a> +<p></p><dt><strong><strong>default (G)</strong></strong><dd> +<p>A synonym for <a href="smb.conf.5.html#defaultservice"><strong>default service</strong></a>. +<p><a name="defaultcase"></a> +<p></p><dt><strong><strong>default case (S)</strong></strong><dd> +<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>. Also note +the <a href="smb.conf.5.html#shortpreservecase"><strong>"short preserve case"</strong></a> parameter. +<p><a name="defaultservice"></a> +<p></p><dt><strong><strong>default service (G)</strong></strong><dd> +<p>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 <em>NOT</em> given in the parameter value (see example below). -<p><br>There is no default value for this parameter. If this parameter is not +<p>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. -<p><br>Typically the default service would be a <a href="../yodldocs/smb.conf.5.html#guestok"><strong>guest ok</strong></a>, -<a href="../yodldocs/smb.conf.5.html#readonly"><strong>read-only</strong></a> service. -<p><br>Also note that the apparent service name will be changed to equal that +<p>Typically the default service would be a <a href="smb.conf.5.html#guestok"><strong>guest ok</strong></a>, +<a href="smb.conf.5.html#readonly"><strong>read-only</strong></a> service. +<p>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 <a href="../yodldocs/smb.conf.5.html#percentS"><strong>%S</strong></a> to make a wildcard service. -<p><br>Note also that any <code>'_'</code> characters in the name of the service used +macros like <a href="smb.conf.5.html#percentS"><strong>%S</strong></a> to make a wildcard service. +<p>Note also that any <code>'_'</code> characters in the name of the service used in the default service will get mapped to a <code>'/'</code>. This allows for interesting things. -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <pre> default service = pub @@ -1201,34 +1201,34 @@ interesting things. </pre> -<p><br><a name="deleteuserscript"></a> -<li><strong><strong>delete user script (G)</strong></strong> -<p><br>This is the full pathname to a script that will be run <em>AS ROOT</em> by +<p><a name="deleteuserscript"></a> +<p></p><dt><strong><strong>delete user script (G)</strong></strong><dd> +<p>This is the full pathname to a script that will be run <em>AS ROOT</em> by <a href="smbd.8.html"><strong>smbd (8)</strong></a> under special circumstances decribed below. -<p><br>Normally, a Samba server requires that UNIX users are created for all +<p>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 <a href="smbd.8.html"><strong>smbd</strong></a> to delete the required UNIX users <em>ON DEMAND</em> when a user accesses the Samba server and the Windows NT user no longer exists. -<p><br>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"delete user +<p>In order to use this option, <a href="smbd.8.html"><strong>smbd</strong></a> must be set to +<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"delete user script"</strong> must be set to a full pathname for a script that will delete a UNIX user given one argument of <strong>%u</strong>, which expands into the UNIX user name to delete. <em>NOTE</em> that this is different to the -<a href="../yodldocs/smb.conf.5.html#adduserscript"><strong>add user script</strong></a> which will work with the -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> option as well as -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>. The reason for this +<a href="smb.conf.5.html#adduserscript"><strong>add user script</strong></a> which will work with the +<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> option as well as +<a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>. The reason for this is only when Samba is a domain member does it get the information on an attempted user logon that a user no longer exists. In the -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> mode a missing user +<a href="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> mode a missing user is treated the same as an invalid password logon attempt. Deleting the user in this circumstance would not be a good idea. -<p><br>When the Windows user attempts to access the Samba server, at +<p>When the Windows user attempts to access the Samba server, at <em>"login"</em>(session setup in the SMB protocol) time, -<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>password +<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a> 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 @@ -1237,265 +1237,265 @@ password database that matches the Windows user account. If this lookup succeeds and <strong>"delete user script"</strong> is set then <a href="smbd.8.html"><strong>smbd</strong></a> will call the specified script <em>AS ROOT</em>, expanding any <strong>%u</strong> argument to be the user name to delete. -<p><br>This script should delete the given UNIX username. In this way, UNIX +<p>This script should delete the given UNIX username. In this way, UNIX users are dynamically deleted to match existing Windows NT accounts. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>, -<a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>password server</strong></a>, <a href="../yodldocs/smb.conf.5.html#adduserscript"><strong>add user +<p>See also <a href="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a>, +<a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a>, <a href="smb.conf.5.html#adduserscript"><strong>add user script</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> delete user script = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> delete user script = /usr/local/samba/bin/del_user %u</code> -<p><br><a name="deletereadonly"></a> -<li><strong><strong>delete readonly (S)</strong></strong> -<p><br>This parameter allows readonly files to be deleted. This is not +<p><a name="deletereadonly"></a> +<p></p><dt><strong><strong>delete readonly (S)</strong></strong><dd> +<p>This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX. -<p><br>This option may be useful for running applications such as rcs, where +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> delete readonly = No</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> delete readonly = Yes</code> -<p><br><a name="deletevetofiles"></a> -<li><strong><strong>delete veto files (S)</strong></strong> -<p><br>This option is used when Samba is attempting to delete a directory -that contains one or more vetoed directories (see the <a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>'veto +<p><a name="deletevetofiles"></a> +<p></p><dt><strong><strong>delete veto files (S)</strong></strong><dd> +<p>This option is used when Samba is attempting to delete a directory +that contains one or more vetoed directories (see the <a href="smb.conf.5.html#vetofiles"><strong>'veto files'</strong></a> option). If this option is set to False (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. -<p><br>If this option is set to True, then Samba will attempt to recursively +<p>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 <strong>NetAtalk</strong>, which create meta-files within directories you might normally veto DOS/Windows users from seeing (e.g. <code>.AppleDouble</code>) -<p><br>Setting <code>'delete veto files = True'</code> allows these directories to be +<p>Setting <code>'delete veto files = True'</code> allows these directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so). -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>veto files</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#vetofiles"><strong>veto files</strong></a> parameter. +<p><strong>Default:</strong> <code> delete veto files = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> delete veto files = True</code> -<p><br><a name="denyhosts"></a> -<li><strong><strong>deny hosts (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>. -<p><br><a name="dfreecommand"></a> -<li><strong><strong>dfree command (G)</strong></strong> -<p><br>The dfree command setting should only be used on systems where a +<p><a name="denyhosts"></a> +<p></p><dt><strong><strong>deny hosts (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>. +<p><a name="dfreecommand"></a> +<p></p><dt><strong><strong>dfree command (G)</strong></strong><dd> +<p>The dfree command 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. -<p><br>This setting allows the replacement of the internal routines to +<p>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. -<p><br>The external program will be passed a single parameter indicating a +<p>The external program will be passed a single parameter indicating a directory in the filesystem being queried. This will typically consist of the string <code>"./"</code>. 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. -<p><br>Note: Your script should <em>NOT</em> be setuid or setgid and should be +<p>Note: Your script should <em>NOT</em> be setuid or setgid and should be owned by (and writeable only by) root! -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> By default internal routines for determining the disk capacity and remaining space will be used.</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> dfree command = /usr/local/samba/bin/dfree</code> -<p><br>Where the script dfree (which must be made executable) could be: -<p><br><pre> +<p>Where the script dfree (which must be made executable) could be: +<p><pre> #!/bin/sh df $1 | tail -1 | awk '{print $2" "$4}' </pre> -<p><br>or perhaps (on Sys V based systems): -<p><br><pre> +<p>or perhaps (on Sys V based systems): +<p><pre> #!/bin/sh /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' </pre> -<p><br>Note that you may have to replace the command names with full +<p>Note that you may have to replace the command names with full path names on some systems. -<p><br><a name="directory"></a> -<li><strong><strong>directory (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#path"><strong>path</strong></a>. -<p><br><a name="directorymask"></a> -<li><strong><strong>directory mask (S)</strong></strong> -<p><br>This parameter is the octal modes which are used when converting DOS +<p><a name="directory"></a> +<p></p><dt><strong><strong>directory (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#path"><strong>path</strong></a>. +<p><a name="directorymask"></a> +<p></p><dt><strong><strong>directory mask (S)</strong></strong><dd> +<p>This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories. -<p><br>When a directory is created, the necessary permissions are calculated +<p>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 <em>*not*</em> set here will be removed from the modes set on a directory when it is created. -<p><br>The default value of this parameter removes the 'group' and 'other' +<p>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. -<p><br>Following this Samba will bit-wise 'OR' the UNIX mode created from +<p>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). -<p><br>See the <a href="../yodldocs/smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> parameter +<p>See the <a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> parameter to cause particular mode bits to always be set on created directories. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#createmode"><strong>"create mode"</strong></a> parameter for masking -mode bits on created files, and the <a href="../yodldocs/smb.conf.5.html#directorysecuritymask"><strong>"directory security mask"</strong></a> +<p>See also the <a href="smb.conf.5.html#createmode"><strong>"create mode"</strong></a> parameter for masking +mode bits on created files, and the <a href="smb.conf.5.html#directorysecuritymask"><strong>"directory security mask"</strong></a> parameter. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. +<p><strong>Default:</strong> <code> directory mask = 0755</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> directory mask = 0775</code> -<p><br><a name="directorymode"></a> -<li><strong><strong>directory mode (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#directorymask"><strong>directory mask</strong></a>. -<p><br><a name="directorysecuritymask"></a> -<li><strong><strong>directory security mask (S)</strong></strong> -<p><br>This parameter controls what UNIX permission bits can be modified +<p><a name="directorymode"></a> +<p></p><dt><strong><strong>directory mode (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a>. +<p><a name="directorysecuritymask"></a> +<p></p><dt><strong><strong>directory security mask (S)</strong></strong><dd> +<p>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. -<p><br>This parameter is applied as a mask (AND'ed with) to the changed +<p>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. -<p><br>If not set explicitly this parameter is set to the same value as the -<a href="../yodldocs/smb.conf.5.html#directorymask"><strong>directory mask</strong></a> parameter. To allow a user to +<p>If not set explicitly this parameter is set to the same value as the +<a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a> parameter. To allow a user to modify all the user/group/world permissions on a directory, set this parameter to 0777. -<p><br><em>Note</em> that users who can access the Samba server through other +<p><em>Note</em> 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 set it to 0777. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security -mode</strong></a>, <a href="../yodldocs/smb.conf.5.html#securitymask"><strong>security -mask</strong></a>, <a href="../yodldocs/smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> +<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security +mode</strong></a>, <a href="smb.conf.5.html#securitymask"><strong>security +mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> parameters. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> directory security mask = <same as directory mask></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> directory security mask = 0777</code> -<p><br><a name="dnsproxy"></a> -<li><strong><strong>dns proxy (G)</strong></strong> -<p><br>Specifies that <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS +<p><a name="dnsproxy"></a> +<p></p><dt><strong><strong>dns proxy (G)</strong></strong><dd> +<p>Specifies that <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client. -<p><br>Note that the maximum length for a NetBIOS name is 15 characters, so +<p>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. -<p><br><a href="nmbd.8.html"><strong>nmbd</strong></a> spawns a second copy of itself to do the +<p><a href="nmbd.8.html"><strong>nmbd</strong></a> spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action. -<p><br>See also the parameter <a href="../yodldocs/smb.conf.5.html#winssupport"><strong>wins support</strong></a>. -<p><br><strong>Default:</strong> +<p>See also the parameter <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>. +<p><strong>Default:</strong> <code> dns proxy = yes</code> -<p><br><a name="domainadmingroup"></a> +<p><a name="domainadmingroup"></a> <strong>domain admin group (G)</strong> -<p><br>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished +<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished Samba NT Domain Controller Code. It may be removed in a later release. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list <strong>Samba-ntdom</strong> available by sending email to <a href="mailto:listproc@samba.org"><em>listproc@samba.org</em></a> -<p><br><a name="domainadminusers"></a> -<li><strong><strong>domain admin users (G)</strong></strong> -<p><br>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished +<p><a name="domainadminusers"></a> +<p></p><dt><strong><strong>domain admin users (G)</strong></strong><dd> +<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished Samba NT Domain Controller Code. It may be removed in a later release. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list <strong>Samba-ntdom</strong> available by sending email to <a href="mailto:listproc@samba.org"><em>listproc@samba.org</em></a> -<p><br><a name="domaingroups"></a> -<li><strong><strong>domain groups (G)</strong></strong> -<p><br>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished +<p><a name="domaingroups"></a> +<p></p><dt><strong><strong>domain groups (G)</strong></strong><dd> +<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished Samba NT Domain Controller Code. It may be removed in a later release. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list <strong>Samba-ntdom</strong> available by sending email to <a href="mailto:listproc@samba.org"><em>listproc@samba.org</em></a> -<p><br><a name="domainguestgroup"></a> -<li><strong><strong>domain guest group (G)</strong></strong> -<p><br>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished +<p><a name="domainguestgroup"></a> +<p></p><dt><strong><strong>domain guest group (G)</strong></strong><dd> +<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished Samba NT Domain Controller Code. It may be removed in a later release. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list <strong>Samba-ntdom</strong> available by sending email to <a href="mailto:listproc@samba.org"><em>listproc@samba.org</em></a> -<p><br><a name="domainguestusers"></a> -<li><strong><strong>domain guest users (G)</strong></strong> -<p><br>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished +<p><a name="domainguestusers"></a> +<p></p><dt><strong><strong>domain guest users (G)</strong></strong><dd> +<p>This is an <strong>EXPERIMENTAL</strong> parameter that is part of the unfinished Samba NT Domain Controller Code. It may be removed in a later release. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list <strong>Samba-ntdom</strong> available by sending email to <a href="mailto:listproc@samba.org"><em>listproc@samba.org</em></a> -<p><br><a name="domainlogons"></a> -<li><strong><strong>domain logons (G)</strong></strong> -<p><br>If set to true, the Samba server will serve Windows 95/98 Domain -logons for the <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> it is in. For more +<p><a name="domainlogons"></a> +<p></p><dt><strong><strong>domain logons (G)</strong></strong><dd> +<p>If set to true, the Samba server will serve Windows 95/98 Domain +logons for the <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> it is in. For more details on setting up this feature see the file DOMAINS.txt in the Samba documentation directory <code>docs/</code> shipped with the source code. -<p><br>Note that Win95/98 Domain logons are <em>NOT</em> the same as Windows +<p>Note that Win95/98 Domain logons are <em>NOT</em> the same as Windows NT Domain logons. NT Domain logons require a Primary Domain Controller (PDC) for the Domain. It is intended that in a future release Samba will be able to provide this functionality for Windows NT clients also. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> domain logons = no</code> -<p><br><a name="domainmaster"></a> -<li><strong><strong>domain master (G)</strong></strong> -<p><br>Tell <a href="nmbd.8.html"><strong>nmbd</strong></a> to enable WAN-wide browse list +<p><a name="domainmaster"></a> +<p></p><dt><strong><strong>domain master (G)</strong></strong><dd> +<p>Tell <a href="nmbd.8.html"><strong>nmbd</strong></a> to enable WAN-wide browse list collation. Setting this option causes <a href="nmbd.8.html"><strong>nmbd</strong></a> to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given -<a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a>. Local master browsers in the same -<a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> on broadcast-isolated subnets will give +<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a>. Local master browsers in the same +<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> on broadcast-isolated subnets will give this <a href="nmbd.8.html"><strong>nmbd</strong></a> their local browse lists, and then ask <a href="smbd.8.html"><strong>smbd</strong></a> for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet. -<p><br>Note that Windows NT Primary Domain Controllers expect to be able to -claim this <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> specific special NetBIOS +<p>Note that Windows NT Primary Domain Controllers expect to be able to +claim this <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> specific special NetBIOS name that identifies them as domain master browsers for that -<a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> by default (i.e. there is no way to +<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> 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 <a href="nmbd.8.html"><strong>nmbd</strong></a> claims the -special name for a <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> before a Windows NT +special name for a <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> domain master = no</code> -<p><br><a name="dontdescend"></a> -<li><strong><strong>dont descend (S)</strong></strong> -<p><br>There are certain directories on some systems (e.g., the <code>/proc</code> tree +<p><a name="dontdescend"></a> +<p></p><dt><strong><strong>dont descend (S)</strong></strong><dd> +<p>There are certain directories on some systems (e.g., the <code>/proc</code> tree under Linux) that are either not of interest to clients or are infinitely deep (recursive). This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty. -<p><br>Note that Samba can be very fussy about the exact format of the "dont +<p>Note that Samba can be very fussy about the exact format of the "dont descend" entries. For example you may need <code>"./proc"</code> instead of just <code>"/proc"</code>. Experimentation is the best policy :-) -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> none (i.e., all directories are OK to descend)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> dont descend = /proc,/dev</code> -<p><br><a name="dosfiletimeresolution"></a> -<li><strong><strong>dos filetime resolution (S)</strong></strong> -<p><br>Under the DOS and Windows FAT filesystem, the finest granularity on +<p><a name="dosfiletimeresolution"></a> +<p></p><dt><strong><strong>dos filetime resolution (S)</strong></strong><dd> +<p>Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to <a href="smbd.8.html"><strong>smbd</strong></a>. -<p><br>This option is mainly used as a compatibility option for Visual C++ +<p>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 @@ -1505,52 +1505,52 @@ 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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> dos filetime resolution = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> dos filetime resolution = True</code> -<p><br><a name="dosfiletimes"></a> -<li><strong><strong>dos filetimes (S)</strong></strong> -<p><br>Under DOS and Windows, if a user can write to a file they can change +<p><a name="dosfiletimes"></a> +<p></p><dt><strong><strong>dos filetimes (S)</strong></strong><dd> +<p>Under DOS and Windows, if a user can write to a file they can change the timestamp on it. Under POSIX semantics, only the owner of the file or root may change the timestamp. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user smbd is acting on behalf of is not the file owner. Setting this option to True allows DOS semantics and smbd will change the file timestamp as DOS requires. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> dos filetimes = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> dos filetimes = True</code> -<p><br><a name="encryptpasswords"></a> -<li><strong><strong>encrypt passwords (G)</strong></strong> -<p><br>This boolean controls whether encrypted passwords will be negotiated +<p><a name="encryptpasswords"></a> +<p></p><dt><strong><strong>encrypt passwords (G)</strong></strong><dd> +<p>This boolean controls whether encrypted passwords will be negotiated with the client. Note that Windows NT 4.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed. To use encrypted passwords in Samba see the file ENCRYPTION.txt in the Samba documentation directory <code>docs/</code> shipped with the source code. -<p><br>In order for encrypted passwords to work correctly +<p>In order for encrypted passwords to work correctly <a href="smbd.8.html"><strong>smbd</strong></a> must either have access to a local <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> file (see the <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a> program for information on how to set up and maintain this file), or set the -<a href="../yodldocs/smb.conf.5.html#security"><strong>security=</strong></a> parameter to either -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>"server"</strong></a> or -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"domain"</strong></a> which causes +<a href="smb.conf.5.html#security"><strong>security=</strong></a> parameter to either +<a href="smb.conf.5.html#securityequalserver"><strong>"server"</strong></a> or +<a href="smb.conf.5.html#securityequaldomain"><strong>"domain"</strong></a> which causes <a href="smbd.8.html"><strong>smbd</strong></a> to authenticate against another server. -<p><br><a name="exec"></a> -<li><strong><strong>exec (S)</strong></strong> -<p><br>This is a synonym for <a href="../yodldocs/smb.conf.5.html#preexec"><strong>preexec</strong></a>. -<p><br><a name="fakedirectorycreatetimes"></a> -<li><strong><strong>fake directory create times (S)</strong></strong> -<p><br>NTFS and Windows VFAT file systems keep a create time for all files +<p><a name="exec"></a> +<p></p><dt><strong><strong>exec (S)</strong></strong><dd> +<p>This is a synonym for <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>. +<p><a name="fakedirectorycreatetimes"></a> +<p></p><dt><strong><strong>fake directory create times (S)</strong></strong><dd> +<p>NTFS and Windows VFAT file systems keep a create time for all files and directories. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep. Setting this parameter for a share causes Samba to always report midnight 1-1-1980 as the create time for directories. -<p><br>This option is mainly used as a compatibility option for Visual C++ +<p>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 @@ -1558,121 +1558,121 @@ 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. -<p><br>However, Unix time semantics mean that the create time reported by +<p>However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or deleted in the directory. NMAKE therefore finds all object files in the object directory bar the last one built are out of date compared to the directory and rebuilds them. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> fake directory create times = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> fake directory create times = True</code> -<p><br><a name="fakeoplocks"></a> -<li><strong><strong>fake oplocks (S)</strong></strong> -<p><br>Oplocks are the way that SMB clients get permission from a server to +<p><a name="fakeoplocks"></a> +<p></p><dt><strong><strong>fake oplocks (S)</strong></strong><dd> +<p>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 aggressively cache file data. With some oplock types the client may even cache file open/close operations. This can give enormous performance benefits. -<p><br>When you set <code>"fake oplocks = yes"</code> <a href="smbd.8.html"><strong>smbd</strong></a> will +<p>When you set <code>"fake oplocks = yes"</code> <a href="smbd.8.html"><strong>smbd</strong></a> will always grant oplock requests no matter how many clients are using the file. -<p><br>It is generally much better to use the real <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>oplocks</strong></a> +<p>It is generally much better to use the real <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> support rather than this parameter. -<p><br>If you enable this option on all read-only shares or shares that you +<p>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! -<p><br>This option is disabled by default. -<p><br><a name="followsymlinks"></a> -<li><strong><strong>follow symlinks (S)</strong></strong> -<p><br>This parameter allows the Samba administrator to stop +<p>This option is disabled by default. +<p><a name="followsymlinks"></a> +<p></p><dt><strong><strong>follow symlinks (S)</strong></strong><dd> +<p>This parameter allows the Samba administrator to stop <a href="smbd.8.html"><strong>smbd</strong></a> from following symbolic links in a particular share. Setting this parameter to <em>"No"</em> prevents any file or directory that is a symbolic link from being followed (the user will get an error). This option is very useful to stop users from adding a symbolic link to <code>/etc/passwd</code> in their home directory for instance. However it will slow filename lookups down slightly. -<p><br>This option is enabled (i.e. <a href="smbd.8.html"><strong>smbd</strong></a> will follow +<p>This option is enabled (i.e. <a href="smbd.8.html"><strong>smbd</strong></a> will follow symbolic links) by default. -<p><br><a name="forcecreatemode"></a> -<li><strong><strong>force create mode (S)</strong></strong> -<p><br>This parameter specifies a set of UNIX mode bit permissions that will +<p><a name="forcecreatemode"></a> +<p></p><dt><strong><strong>force create mode (S)</strong></strong><dd> +<p>This parameter specifies a set of UNIX mode bit permissions that will <em>*always*</em> be set on a file by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its permissions changed. The default for this parameter is (in octal) 000. The modes in this parameter are bitwise 'OR'ed onto -the file mode after the mask set in the <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create +the file mode after the mask set in the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> parameter is applied. -<p><br>See also the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details +<p>See also the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details on masking mode bits on files. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. +<p><strong>Default:</strong> <code> force create mode = 000</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force create mode = 0755</code> -<p><br>would force all created files to have read and execute permissions set +<p>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'. -<p><br><a name="forcedirectorymode"></a> -<li><strong><strong>force directory mode (S)</strong></strong> -<p><br>This parameter specifies a set of UNIX mode bit permissions that will +<p><a name="forcedirectorymode"></a> +<p></p><dt><strong><strong>force directory mode (S)</strong></strong><dd> +<p>This parameter specifies a set of UNIX mode bit permissions that will <em>*always*</em> be set on a directory created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory. This operation is done after the mode mask in the parameter -<a href="../yodldocs/smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> is applied. -<p><br>See also the parameter <a href="../yodldocs/smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> for +<a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> is applied. +<p>See also the parameter <a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> for details on masking mode bits on created directories. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#inheritpermissions"><strong>"inherit permissions"</strong></a> parameter. +<p><strong>Default:</strong> <code> force directory mode = 000</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force directory mode = 0755</code> -<p><br>would force all created directories to have read and execute +<p>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'. -<p><br><a name="forcedirectorysecuritymode"></a> -<li><strong><strong>force directory security mode (S)</strong></strong> -<p><br>This parameter controls what UNIX permission bits can be modified when +<p><a name="forcedirectorysecuritymode"></a> +<p></p><dt><strong><strong>force directory security mode (S)</strong></strong><dd> +<p>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. -<p><br>This parameter is applied as a mask (OR'ed with) to the changed +<p>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'. -<p><br>If not set explicitly this parameter is set to the same value as the -<a href="../yodldocs/smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> parameter. To allow +<p>If not set explicitly this parameter is set to the same value as the +<a href="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> parameter. To allow a user to modify all the user/group/world permissions on a directory, with restrictions set this parameter to 000. -<p><br><em>Note</em> that users who can access the Samba server through other +<p><em>Note</em> 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 set it to 0000. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a>, -<a href="../yodldocs/smb.conf.5.html#securitymask"><strong>security mask</strong></a>, <a href="../yodldocs/smb.conf.5.html#forcesecuritymode"><strong>force security +<p>See also the <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a>, +<a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> parameters. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> force directory security mode = <same as force directory mode></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force directory security mode = 0</code> -<p><br><a name="forcegroup"></a> -<li><strong><strong>force group (S)</strong></strong> -<p><br>This specifies a UNIX group name that will be assigned as the default +<p><a name="forcegroup"></a> +<p></p><dt><strong><strong>force group (S)</strong></strong><dd> +<p>This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files. -<p><br>In Samba 2.0.5 and above this parameter has extended functionality in the following +<p>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 @@ -1683,151 +1683,151 @@ assignment. For example, the setting <code>force group = +sys</code> 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. -<p><br>If the <a href="../yodldocs/smb.conf.5.html#forceuser"><strong>"force user"</strong></a> parameter is also set the +<p>If the <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a> parameter is also set the group specified in <strong>force group</strong> will override the primary group -set in <a href="../yodldocs/smb.conf.5.html#forceuser"><strong>"force user"</strong></a>. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#forceuser"><strong>"force user"</strong></a> -<p><br><strong>Default:</strong> +set in <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a>. +<p>See also <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a> +<p><strong>Default:</strong> <code> no forced group</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force group = agroup</code> -<p><br><a name="forcesecuritymode"></a> -<li><strong><strong>force security mode (S)</strong></strong> -<p><br>This parameter controls what UNIX permission bits can be modified when +<p><a name="forcesecuritymode"></a> +<p></p><dt><strong><strong>force security mode (S)</strong></strong><dd> +<p>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box. -<p><br>This parameter is applied as a mask (OR'ed with) to the changed +<p>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'. -<p><br>If not set explicitly this parameter is set to the same value as the -<a href="../yodldocs/smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> parameter. To allow +<p>If not set explicitly this parameter is set to the same value as the +<a href="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> parameter. To allow a user to modify all the user/group/world permissions on a file, with no restrictions set this parameter to 000. -<p><br><em>Note</em> that users who can access the Samba server through other +<p><em>Note</em> 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 set it to 0000. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security -mode</strong></a>, <a href="../yodldocs/smb.conf.5.html#directorysecuritymask"><strong>directory security -mask</strong></a>, <a href="../yodldocs/smb.conf.5.html#securitymask"><strong>security mask</strong></a> +<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security +mode</strong></a>, <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security +mask</strong></a>, <a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a> parameters. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> force security mode = <same as force create mode></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force security mode = 0</code> -<p><br><a name="forceuser"></a> -<li><strong><strong>force user (S)</strong></strong> -<p><br>This specifies a UNIX user name that will be assigned as the default +<p><a name="forceuser"></a> +<p></p><dt><strong><strong>force user (S)</strong></strong><dd> +<p>This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. You should also use it carefully as using it incorrectly can cause security problems. -<p><br>This user name only gets used once a connection is established. Thus +<p>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 <code>"forced user"</code>, no matter what username the client connected as. -<p><br>This can be very useful. -<p><br>In Samba 2.0.5 and above this parameter also causes the primary +<p>This can be very useful. +<p>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). -<p><br>See also <a href="../yodldocs/smb.conf.5.html#forcegroup"><strong>"force group"</strong></a> -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a> +<p><strong>Default:</strong> <code> no forced user</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> force user = auser</code> -<p><br><a name="fstype"></a> -<li><strong><strong>fstype (S)</strong></strong> -<p><br>This parameter allows the administrator to configure the string that +<p><a name="fstype"></a> +<p></p><dt><strong><strong>fstype (S)</strong></strong><dd> +<p>This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by <a href="smbd.8.html"><strong>smbd</strong></a> when a client queries the filesystem type for a share. The default type is <strong>"NTFS"</strong> for compatibility with Windows NT but this can be changed to other strings such as "Samba" or "FAT" if required. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> fstype = NTFS</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> fstype = Samba</code> -<p><br><a name="getwdcache"></a> -<li><strong><strong>getwd cache (G)</strong></strong> -<p><br>This is a tuning option. When this is enabled a caching algorithm +<p><a name="getwdcache"></a> +<p></p><dt><strong><strong>getwd cache (G)</strong></strong><dd> +<p>This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls. This can have a significant impact on performance, especially when the -<a href="../yodldocs/smb.conf.5.html#widelinks"><strong>widelinks</strong></a> parameter is set to False. -<p><br><strong>Default:</strong> +<a href="smb.conf.5.html#widelinks"><strong>widelinks</strong></a> parameter is set to False. +<p><strong>Default:</strong> <code> getwd cache = No</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> getwd cache = Yes</code> -<p><br><a name="group"></a> -<li><strong><strong>group (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>. -<p><br><a name="guestaccount"></a> -<li><strong><strong>guest account (S)</strong></strong> -<p><br>This is a username which will be used for access to services which are -specified as <a href="../yodldocs/smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> (see below). Whatever +<p><a name="group"></a> +<p></p><dt><strong><strong>group (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>. +<p><a name="guestaccount"></a> +<p></p><dt><strong><strong>guest account (S)</strong></strong><dd> +<p>This is a username which will be used for access to services which are +specified as <a href="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> (see below). Whatever privileges this user has will be available to any client connecting to the guest service. Typically this user will exist in the password file, but will not have a valid login. The user account <strong>"ftp"</strong> is often a good choice for this parameter. If a username is specified in a given service, the specified username overrides this one. -<p><br>One some systems the default guest account "nobody" may not be able to +<p>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 <code>"su -"</code> command) and trying to print using the system print command such as <strong>lpr (1)</strong> or <strong>lp (1)</strong>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> specified at compile time, usually "nobody"</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> guest account = ftp</code> -<p><br><a name="guestok"></a> -<li><strong><strong>guest ok (S)</strong></strong> -<p><br>If this parameter is <em>'yes'</em> for a service, then no password is +<p><a name="guestok"></a> +<p></p><dt><strong><strong>guest ok (S)</strong></strong><dd> +<p>If this parameter is <em>'yes'</em> for a service, then no password is required to connect to the service. Privileges will be those of the -<a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>guest account</strong></a>. -<p><br>See the section below on <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> for more +<a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a>. +<p>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more information about this option. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> guest ok = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> guest ok = yes</code> -<p><br><a name="guestonly"></a> -<li><strong><strong>guest only (S)</strong></strong> -<p><br>If this parameter is <em>'yes'</em> for a service, then only guest +<p><a name="guestonly"></a> +<p></p><dt><strong><strong>guest only (S)</strong></strong><dd> +<p>If this parameter is <em>'yes'</em> for a service, then only guest connections to the service are permitted. This parameter will have no -affect if <a href="../yodldocs/smb.conf.5.html#guestok"><strong>"guest ok"</strong></a> or <a href="../yodldocs/smb.conf.5.html#public"><strong>"public"</strong></a> +affect if <a href="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a> or <a href="smb.conf.5.html#public"><strong>"public"</strong></a> is not set for the service. -<p><br>See the section below on <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> for more +<p>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more information about this option. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> guest only = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> guest only = yes</code> -<p><br><a name="hidedotfiles"></a> -<li><strong><strong>hide dot files (S)</strong></strong> -<p><br>This is a boolean parameter that controls whether files starting with +<p><a name="hidedotfiles"></a> +<p></p><dt><strong><strong>hide dot files (S)</strong></strong><dd> +<p>This is a boolean parameter that controls whether files starting with a dot appear as hidden files. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> hide dot files = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> hide dot files = no</code> -<p><br><a name="hidefiles"></a> -<li><strong><strong>hide files(S)</strong></strong> -<p><br>This is a list of files or directories that are not visible but are +<p><a name="hidefiles"></a> +<p></p><dt><strong><strong>hide files(S)</strong></strong><dd> +<p>This is a list of files or directories that are not visible but are accessible. The DOS 'hidden' attribute is applied to any files or directories that match. -<p><br>Each entry in the list must be separated by a <code>'/'</code>, which allows +<p>Each entry in the list must be separated by a <code>'/'</code>, which allows spaces to be included in the entry. <code>'*'</code> and <code>'?'</code> can be used to specify multiple files or directories as in DOS wildcards. -<p><br>Each entry must be a Unix path, not a DOS path and must not include the +<p>Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator <code>'/'</code>. -<p><br>Note that the case sensitivity option is applicable in hiding files. -<p><br>Setting this parameter will affect the performance of Samba, as it +<p>Note that the case sensitivity option is applicable in hiding files. +<p>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. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#hidedotfiles"><strong>"hide dot files"</strong></a>, <a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>"veto -files"</strong></a> and <a href="../yodldocs/smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. -<p><br><strong>Default</strong> +<p>See also <a href="smb.conf.5.html#hidedotfiles"><strong>"hide dot files"</strong></a>, <a href="smb.conf.5.html#vetofiles"><strong>"veto +files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. +<p><strong>Default</strong> <pre> No files or directories are hidden by this option (dot files are @@ -1835,139 +1835,139 @@ files"</strong></a> and <a href="../yodldocs/smb.conf.5.html#casesensitive"><str </pre> -<p><br><strong>Example</strong> +<p><strong>Example</strong> <code> hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/</code> -<p><br>The above example is based on files that the Macintosh SMB client +<p>The above example is based on files that the Macintosh SMB client (DAVE) available from <a href="http://www.thursby.com"><strong>Thursby</strong></a> creates for internal use, and also still hides all files beginning with a dot. -<p><br><a name="homedirmap"></a> -<li><strong><strong>homedir map (G)</strong></strong> -<p><br>If <a href="../yodldocs/smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a> is true, and -<a href="smbd.8.html"><strong>smbd</strong></a> is also acting as a Win95/98 <a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon +<p><a name="homedirmap"></a> +<p></p><dt><strong><strong>homedir map (G)</strong></strong><dd> +<p>If <a href="smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a> is true, and +<a href="smbd.8.html"><strong>smbd</strong></a> is also acting as a Win95/98 <a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a> then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted. At present, only the Sun auto.home map format is understood. The form of the map is: -<p><br><code>username server:/some/file/system</code> -<p><br>and the program will extract the servername from before the first +<p><code>username server:/some/file/system</code> +<p>and the program will extract the servername from before the first <code>':'</code>. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps. -<p><br>NB: A working NIS is required on the system for this option to work. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a>, <a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>domain +<p>NB: A working NIS is required on the system for this option to work. +<p>See also <a href="smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a>, <a href="smb.conf.5.html#domainlogons"><strong>domain logons</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> homedir map = auto.home</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> homedir map = amd.homedir</code> -<p><br><a name="hostsallow"></a> -<li><strong><strong>hosts allow (S)</strong></strong> -<p><br>A synonym for this parameter is <a href="../yodldocs/smb.conf.5.html#allowhosts"><strong>'allow hosts'</strong></a> -<p><br>This parameter is a comma, space, or tab delimited set of hosts which +<p><a name="hostsallow"></a> +<p></p><dt><strong><strong>hosts allow (S)</strong></strong><dd> +<p>A synonym for this parameter is <a href="smb.conf.5.html#allowhosts"><strong>'allow hosts'</strong></a> +<p>This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service. -<p><br>If specified in the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section then it will +<p>If specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section then it will apply to all services, regardless of whether the individual service has a different setting. -<p><br>You can specify the hosts by name or IP number. For example, you could +<p>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 <code>"allow hosts = 150.203.5."</code>. The full syntax of the list is described in the man page <strong>hosts_access (5)</strong>. Note that this man page may not be present on your system, so a brief description will be given here also. -<p><br>Note that the localhost address 127.0.0.1 will always be allowed +<p>Note that the localhost address 127.0.0.1 will always be allowed access unless specifically denied by a "hosts deny" option. -<p><br>You can also specify hosts by network/netmask pairs and by netgroup +<p>You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The <em>EXCEPT</em> keyword can also be used to limit a wildcard list. The following examples may provide some help: -<p><br><strong>Example 1</strong>: allow all IPs in 150.203.*.* except one -<p><br><code> hosts allow = 150.203. EXCEPT 150.203.6.66</code> -<p><br><strong>Example 2</strong>: allow hosts that match the given network/netmask -<p><br><code> hosts allow = 150.203.15.0/255.255.255.0</code> -<p><br><strong>Example 3</strong>: allow a couple of hosts -<p><br><code> hosts allow = lapland, arvidsjaur</code> -<p><br><strong>Example 4</strong>: allow only hosts in NIS netgroup "foonet", but +<p><strong>Example 1</strong>: allow all IPs in 150.203.*.* except one +<p><code> hosts allow = 150.203. EXCEPT 150.203.6.66</code> +<p><strong>Example 2</strong>: allow hosts that match the given network/netmask +<p><code> hosts allow = 150.203.15.0/255.255.255.0</code> +<p><strong>Example 3</strong>: allow a couple of hosts +<p><code> hosts allow = lapland, arvidsjaur</code> +<p><strong>Example 4</strong>: allow only hosts in NIS netgroup "foonet", but deny access from one particular host -<p><br><code> hosts allow = @foonet</code> -<p><br><code> hosts deny = pirate</code> -<p><br>Note that access still requires suitable user-level passwords. -<p><br>See <a href="testparm.1.html"><strong>testparm (1)</strong></a> for a way of testing your +<p><code> hosts allow = @foonet</code> +<p><code> hosts deny = pirate</code> +<p>Note that access still requires suitable user-level passwords. +<p>See <a href="testparm.1.html"><strong>testparm (1)</strong></a> for a way of testing your host access to see if it does what you expect. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> none (i.e., all hosts permitted access)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> allow hosts = 150.203.5. myhost.mynet.edu.au</code> -<p><br><a name="hostsdeny"></a> -<li><strong><strong>hosts deny (S)</strong></strong> -<p><br>The opposite of <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>'hosts allow'</strong></a> - hosts listed +<p><a name="hostsdeny"></a> +<p></p><dt><strong><strong>hosts deny (S)</strong></strong><dd> +<p>The opposite of <a href="smb.conf.5.html#hostsallow"><strong>'hosts allow'</strong></a> - hosts listed here are <em>NOT</em> permitted access to services unless the specific services have their own lists to override this one. Where the lists -conflict, the <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>'allow'</strong></a> list takes precedence. -<p><br><strong>Default:</strong> +conflict, the <a href="smb.conf.5.html#hostsallow"><strong>'allow'</strong></a> list takes precedence. +<p><strong>Default:</strong> <code> none (i.e., no hosts specifically excluded)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> hosts deny = 150.203.4. badhost.mynet.edu.au</code> -<p><br><a name="hostsequiv"></a> -<li><strong><strong>hosts equiv (G)</strong></strong> -<p><br>If this global parameter is a non-null string, it specifies the name +<p><a name="hostsequiv"></a> +<p></p><dt><strong><strong>hosts equiv (G)</strong></strong><dd> +<p>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. -<p><br>This is not be confused with <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> which +<p>This is not be confused with <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> which is about hosts access to services and is more useful for guest services. <strong>hosts equiv</strong> may be useful for NT clients which will not supply passwords to samba. -<p><br>NOTE: The use of <strong>hosts equiv</strong> can be a major security hole. This is +<p>NOTE: The use of <strong>hosts equiv</strong> 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 <strong>hosts equiv</strong> 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 <em>really</em> trust them :-). -<p><br><strong>Default</strong> +<p><strong>Default</strong> <code> No host equivalences</code> -<p><br><strong>Example</strong> +<p><strong>Example</strong> <code> hosts equiv = /etc/hosts.equiv</code> -<p><br><a name="include"></a> -<li><strong><strong>include (G)</strong></strong> -<p><br>This allows you to include one config file inside another. The file +<p><a name="include"></a> +<p></p><dt><strong><strong>include (G)</strong></strong><dd> +<p>This allows you to include one config file inside another. The file is included literally, as though typed in place. -<p><br>It takes the standard substitutions, except <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a>, -<a href="../yodldocs/smb.conf.5.html#percentP"><strong>%P</strong></a> and <a href="../yodldocs/smb.conf.5.html#percentS"><strong>%S</strong></a>. -<p><br><a name="inheritpermissions"></a> -<li><strong><strong>inherit permissions (S)</strong></strong> -<p><br>The permissions on new files and directories are normally governed by -<a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and -<a href="../yodldocs/smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> +<p>It takes the standard substitutions, except <a href="smb.conf.5.html#percentu"><strong>%u</strong></a>, +<a href="smb.conf.5.html#percentP"><strong>%P</strong></a> and <a href="smb.conf.5.html#percentS"><strong>%S</strong></a>. +<p><a name="inheritpermissions"></a> +<p></p><dt><strong><strong>inherit permissions (S)</strong></strong><dd> +<p>The permissions on new files and directories are normally governed by +<a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>, +<a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>, +<a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and +<a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> but the boolean inherit permissions parameter overrides this. -<p><br>New directories inherit the mode of the parent directory, +<p>New directories inherit the mode of the parent directory, including bits such as setgid. -<p><br>New files inherit their read/write bits from the parent directory. +<p>New files inherit their read/write bits from the parent directory. Their execute bits continue to be determined by -<a href="../yodldocs/smb.conf.5.html#maparchive"><strong>"map archive"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#maphidden"><strong>"map hidden"</strong></a> and -<a href="../yodldocs/smb.conf.5.html#mapsystem"><strong>"map system"</strong></a> as usual. -<p><br>Note that the setuid bit is *never* set via inheritance +<a href="smb.conf.5.html#maparchive"><strong>"map archive"</strong></a>, +<a href="smb.conf.5.html#maphidden"><strong>"map hidden"</strong></a> and +<a href="smb.conf.5.html#mapsystem"><strong>"map system"</strong></a> as usual. +<p>Note that the setuid bit is *never* set via inheritance (the code explicitly prohibits this). -<p><br>This can be particularly useful on large systems with many users, +<p>This can be particularly useful on large systems with many users, perhaps several thousand, to allow a single <strong>[homes]</strong> share to be used flexibly by each user. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a>, <a href="../yodldocs/smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and -<a href="../yodldocs/smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a>. -<p><br><strong>Default</strong> +<p>See also <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>, <a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a>, +<a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> and +<a href="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a>. +<p><strong>Default</strong> <code> inherit permissions = no</code> -<p><br><strong>Example</strong> +<p><strong>Example</strong> <code> inherit permissions = yes</code> -<p><br><a name="interfaces"></a> -<li><strong><strong>interfaces (G)</strong></strong> -<p><br>This option allows you to override the default network interfaces list +<p><a name="interfaces"></a> +<p></p><dt><strong><strong>interfaces (G)</strong></strong><dd> +<p>This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable. -<p><br>The option takes a list of interface strings. Each string can be in +<p>The option takes a list of interface strings. Each string can be in any of the following forms: -<p><br><ul> +<p><dl> <li > a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth" @@ -1975,27 +1975,27 @@ any of the following forms: from the list of interfaces obtained from the kernel <li > an IP/mask pair. <li > a broadcast/mask pair. -</ul> -<p><br>The "mask" parameters can either be a bit length (such as 24 for a C +</dl> +<p>The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decmal form. -<p><br>The "IP" parameters above can either be a full dotted decimal IP +<p>The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OSes normal hostname resolution mechanisms. -<p><br>For example, the following line: -<p><br><code>interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</code> -<p><br>would configure three network interfaces corresponding to the eth0 +<p>For example, the following line: +<p><code>interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</code> +<p>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. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#bindinterfacesonly"><strong>"bind interfaces only"</strong></a>. -<p><br><a name="invalidusers"></a> -<li><strong><strong>invalid users (S)</strong></strong> -<p><br>This is a list of users that should not be allowed to login to this +<p>See also <a href="smb.conf.5.html#bindinterfacesonly"><strong>"bind interfaces only"</strong></a>. +<p><a name="invalidusers"></a> +<p></p><dt><strong><strong>invalid users (S)</strong></strong><dd> +<p>This is a list of users that should not be allowed to login to this service. This is really a <em>"paranoid"</em> check to absolutely ensure an improper setting does not breach your security. -<p><br>A name starting with a <code>'@'</code> is interpreted as an NIS netgroup first +<p>A name starting with a <code>'@'</code> 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. -<p><br>A name starting with <code>'+'</code> is interpreted only by looking in the +<p>A name starting with <code>'+'</code> is interpreted only by looking in the UNIX group database. A name starting with <code>'&'</code> is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters <code>'+'</code> and <code>'&'</code> may be @@ -2004,120 +2004,120 @@ used at the start of the name in either order so the value netgroup database, and the value <code>"&+group"</code> means check the NIS netgroup database, followed by the UNIX group database (the same as the <code>'@'</code> prefix). -<p><br>The current servicename is substituted for -<a href="../yodldocs/smb.conf.5.html#percentS"><strong>%S</strong></a>. This is useful in the <a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> +<p>The current servicename is substituted for +<a href="smb.conf.5.html#percentS"><strong>%S</strong></a>. This is useful in the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> section. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#validusers"><strong>"valid users"</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#validusers"><strong>"valid users"</strong></a>. +<p><strong>Default:</strong> <code> No invalid users</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> invalid users = root fred admin @wheel</code> -<p><br><a name="keepalive"></a> -<li><strong><strong>keepalive (G)</strong></strong> -<p><br>The value of the parameter (an integer) represents the number of +<p><a name="keepalive"></a> +<p></p><dt><strong><strong>keepalive (G)</strong></strong><dd> +<p>The value of the parameter (an integer) represents the number of seconds between <strong>'keepalive'</strong> 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. -<p><br>Keepalives should, in general, not be needed if the socket being used -has the SO_KEEPALIVE attribute set on it (see <a href="../yodldocs/smb.conf.5.html#socketoptions"><strong>"socket +<p>Keepalives should, in general, not be needed if the socket being used +has the SO_KEEPALIVE attribute set on it (see <a href="smb.conf.5.html#socketoptions"><strong>"socket options"</strong></a>). Basically you should only use this option if you strike difficulties. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> keepalive = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> keepalive = 60</code> -<p><br><a name="kerneloplocks"></a> -<li><strong><strong>kernel oplocks (G)</strong></strong> -<p><br>For UNIXs that support kernel based <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>oplocks</strong></a> +<p><a name="kerneloplocks"></a> +<p></p><dt><strong><strong>kernel oplocks (G)</strong></strong><dd> +<p>For UNIXs that support kernel based <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> (currently only IRIX but hopefully also Linux and FreeBSD soon) this parameter allows the use of them to be turned on or off. -<p><br>Kernel oplocks support allows Samba <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>oplocks</strong></a> to be +<p>Kernel oplocks support allows Samba <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> to be broken whenever a local UNIX process or NFS operation accesses a file that <a href="smbd.8.html"><strong>smbd</strong></a> has oplocked. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a <em>very</em> cool feature :-). -<p><br>This parameter defaults to <em>"On"</em> on systems that have the support, +<p>This parameter defaults to <em>"On"</em> on systems that have the support, and <em>"off"</em> on systems that don't. You should never need to touch this parameter. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="../yodldocs/smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a> +<p>See also the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a> parameters. -<p><br><a name="ldapfilter"></a> -<li><strong><strong>ldap filter (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldapfilter"></a> +<p></p><dt><strong><strong>ldap filter (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies an LDAP search filter used to search for a +<p>This parameter specifies an LDAP search filter used to search for a user name in the LDAP database. It must contain the string -<a href="../yodldocs/smb.conf.5.html#percentU"><strong>%u</strong></a> which will be replaced with the user being +<a href="smb.conf.5.html#percentU"><strong>%u</strong></a> which will be replaced with the user being searched for. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> empty string.</code> -<p><br><a name="ldapport"></a> -<li><strong><strong>ldap port (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldapport"></a> +<p></p><dt><strong><strong>ldap port (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies the TCP port number to use to contact +<p>This parameter specifies the TCP port number to use to contact the LDAP server on. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ldap port = 389.</code> -<p><br><a name="ldaproot"></a> -<li><strong><strong>ldap root (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldaproot"></a> +<p></p><dt><strong><strong>ldap root (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies the entity to bind to the LDAP server +<p>This parameter specifies the entity to bind to the LDAP server as (essentially the LDAP username) in order to be able to perform queries and modifications on the LDAP database. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>. +<p><strong>Default:</strong> <code> empty string (no user defined)</code> -<p><br><a name="ldaprootpasswd"></a> -<li><strong><strong>ldap root passwd (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldaprootpasswd"></a> +<p></p><dt><strong><strong>ldap root passwd (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies the password for the entity to bind to the +<p>This parameter specifies the password for the entity to bind to the LDAP server as (the password for this LDAP username) in order to be able to perform queries and modifications on the LDAP database. -<p><br><em>BUGS:</em> This parameter should <em>NOT</em> be a readable parameter +<p><em>BUGS:</em> This parameter should <em>NOT</em> be a readable parameter in the <strong>smb.conf</strong> file and will be removed once a correct storage place is found. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>. +<p><strong>Default:</strong> <code> empty string.</code> -<p><br><a name="ldapserver"></a> -<li><strong><strong>ldap server (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldapserver"></a> +<p></p><dt><strong><strong>ldap server (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies the DNS name of the LDAP server to use +<p>This parameter specifies the DNS name of the LDAP server to use for SMB/CIFS authentication purposes. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ldap server = localhost</code> -<p><br><a name="ldapsuffix"></a> -<li><strong><strong>ldap suffix (G)</strong></strong> -<p><br>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a +<p><a name="ldapsuffix"></a> +<p></p><dt><strong><strong>ldap suffix (G)</strong></strong><dd> +<p>This parameter is part of the <em>EXPERIMENTAL</em> Samba support for a password database stored on an LDAP server back-end. These options are only available if your version of Samba was configured with the <strong>--with-ldap</strong> option. -<p><br>This parameter specifies the <code>"dn"</code> or LDAP <em>"distinguished name"</em> +<p>This parameter specifies the <code>"dn"</code> or LDAP <em>"distinguished name"</em> that tells <a href="smbd.8.html"><strong>smbd</strong></a> to start from when searching for an entry in the LDAP password database. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> empty string.</code> -<p><br><a name="level2oplocks"></a> -<li><strong><strong>level2 oplocks (S)</strong></strong> -<p><br>This parameter (new in Samba 2.0.5) controls whether Samba supports +<p><a name="level2oplocks"></a> +<p></p><dt><strong><strong>level2 oplocks (S)</strong></strong><dd> +<p>This parameter (new in Samba 2.0.5) controls whether Samba supports level2 (read-only) oplocks on a share. In Samba 2.0.5 this parameter defaults to "False" as the code is new, but will default to "True" in a later release. -<p><br>Level2, or read-only oplocks allow Windows NT clients that have an +<p>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 @@ -2125,66 +2125,66 @@ 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 acesses of files that are not commonly written (such as application .EXE files). -<p><br>Once one of the clients which have a read-only oplock writes to +<p>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. -<p><br>It is recommended that this parameter be turned on to speed access +<p>It is recommended that this parameter be turned on to speed access to shared executables (and also to test the code :-). -<p><br>For more discussions on level2 oplocks see the CIFS spec. -<p><br>Currently, if <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> are supported +<p>For more discussions on level2 oplocks see the CIFS spec. +<p>Currently, if <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> are supported then level2 oplocks are not granted (even if this parameter is set -to <code>"true"</code>). Note also, the <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> parameter must +to <code>"true"</code>). Note also, the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> parameter must be set to "true" on this share in order for this parameter to have any effect. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> parameters. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> parameters. +<p><strong>Default:</strong> <code> level2 oplocks = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> level2 oplocks = True</code> -<p><br><a name="lmannounce"></a> -<li><strong><strong>lm announce (G)</strong></strong> -<p><br>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> will produce +<p><a name="lmannounce"></a> +<p></p><dt><strong><strong>lm announce (G)</strong></strong><dd> +<p>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> will produce Lanman announce broadcasts that are needed by <strong>OS/2</strong> clients in order for them to see the Samba server in their browse list. This parameter can have three values, <code>"true"</code>, <code>"false"</code>, or <code>"auto"</code>. The default is <code>"auto"</code>. If set to <code>"false"</code> Samba will never produce these broadcasts. If set to <code>"true"</code> Samba will produce Lanman -announce broadcasts at a frequency set by the parameter <a href="../yodldocs/smb.conf.5.html#lminterval"><strong>"lm +announce broadcasts at a frequency set by the parameter <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>. If set to <code>"auto"</code> Samba will not send Lanman announce broadcasts by default but will listen for them. If it hears such a broadcast on the wire it will then start sending them at a -frequency set by the parameter <a href="../yodldocs/smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>. -<p><br><strong>Default:</strong> +frequency set by the parameter <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>. +<p>See also <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>. +<p><strong>Default:</strong> <code> lm announce = auto</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> lm announce = true</code> -<p><br><a name="lminterval"></a> -<li><strong><strong>lm interval (G)</strong></strong> -<p><br>If Samba is set to produce Lanman announce broadcasts needed by -<strong>OS/2</strong> clients (see the <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a> +<p><a name="lminterval"></a> +<p></p><dt><strong><strong>lm interval (G)</strong></strong><dd> +<p>If Samba is set to produce Lanman announce broadcasts needed by +<strong>OS/2</strong> clients (see the <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a> parameter) then this parameter defines the frequency in seconds with which they will be made. If this is set to zero then no Lanman -announcements will be made despite the setting of the <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>"lm +announcements will be made despite the setting of the <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a> parameter. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>. +<p><strong>Default:</strong> <code> lm interval = 60</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> lm interval = 120</code> -<p><br><a name="loadprinters"></a> -<li><strong><strong>load printers (G)</strong></strong> -<p><br>A boolean variable that controls whether all printers in the printcap +<p><a name="loadprinters"></a> +<p></p><dt><strong><strong>load printers (G)</strong></strong><dd> +<p>A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default. See the -<a href="../yodldocs/smb.conf.5.html#printers"><strong>"printers"</strong></a> section for more details. -<p><br><strong>Default:</strong> +<a href="smb.conf.5.html#printers"><strong>"printers"</strong></a> section for more details. +<p><strong>Default:</strong> <code> load printers = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> load printers = no</code> -<p><br><a name="localmaster"></a> -<li><strong><strong>local master (G)</strong></strong> -<p><br>This option allows <a href="nmbd.8.html"><strong>nmbd</strong></a> to try and become a +<p><a name="localmaster"></a> +<p></p><dt><strong><strong>local master (G)</strong></strong><dd> +<p>This option allows <a href="nmbd.8.html"><strong>nmbd</strong></a> to try and become a local master browser on a subnet. If set to False then <a href="nmbd.8.html"><strong>nmbd</strong></a> will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By @@ -2192,464 +2192,464 @@ default this value is set to true. Setting this value to true doesn't mean that Samba will <em>become</em> the local master browser on a subnet, just that <a href="nmbd.8.html"><strong>nmbd</strong></a> will <em>participate</em> in elections for local master browser. -<p><br>Setting this value to False will cause <a href="nmbd.8.html"><strong>nmbd</strong></a> +<p>Setting this value to False will cause <a href="nmbd.8.html"><strong>nmbd</strong></a> <em>never</em> to become a local master browser. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> local master = yes</code> -<p><br><a name="lockdir"></a> -<li><strong><strong>lock dir (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#lockdirectory"><strong>"lock directory"</strong></a>. -<p><br><a name="lockdirectory"></a> -<li><strong><strong>lock directory (G)</strong></strong> -<p><br>This option specifies the directory where lock files will be placed. -The lock files are used to implement the <a href="../yodldocs/smb.conf.5.html#maxconnections"><strong>"max +<p><a name="lockdir"></a> +<p></p><dt><strong><strong>lock dir (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#lockdirectory"><strong>"lock directory"</strong></a>. +<p><a name="lockdirectory"></a> +<p></p><dt><strong><strong>lock directory (G)</strong></strong><dd> +<p>This option specifies the directory where lock files will be placed. +The lock files are used to implement the <a href="smb.conf.5.html#maxconnections"><strong>"max connections"</strong></a> option. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> lock directory = /tmp/samba</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> lock directory = /usr/local/samba/var/locks</code> -<p><br><a name="locking"></a> -<li><strong><strong>locking (S)</strong></strong> -<p><br>This controls whether or not locking will be performed by the server +<p><a name="locking"></a> +<p></p><dt><strong><strong>locking (S)</strong></strong><dd> +<p>This controls whether or not locking will be performed by the server in response to lock requests from the client. -<p><br>If <code>"locking = no"</code>, all lock and unlock requests will appear to +<p>If <code>"locking = no"</code>, all lock and unlock requests will appear to succeed and all lock queries will indicate that the queried lock is clear. -<p><br>If <code>"locking = yes"</code>, real locking will be performed by the server. -<p><br>This option <em>may</em> be useful for read-only filesystems which <em>may</em> +<p>If <code>"locking = yes"</code>, real locking will be performed by the server. +<p>This option <em>may</em> be useful for read-only filesystems which <em>may</em> not need locking (such as cdrom drives), although setting this parameter of <code>"no"</code> is not really recommended even in this case. -<p><br>Be careful about disabling locking either globally or in a specific +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> locking = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> locking = no</code> -<p><br><a name="logfile"></a> -<li><strong><strong>log file (G)</strong></strong> -<p><br>This options allows you to override the name of the Samba log file +<p><a name="logfile"></a> +<p></p><dt><strong><strong>log file (G)</strong></strong><dd> +<p>This options allows you to override the name of the Samba log file (also known as the debug file). -<p><br>This option takes the standard substitutions, allowing you to have +<p>This option takes the standard substitutions, allowing you to have separate log files for each user or machine. -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> log file = /usr/local/samba/var/log.%m</code> -<p><br><a name="loglevel"></a> -<li><strong><strong>log level (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a>. -<p><br><a name="logondrive"></a> -<li><strong><strong>logon drive (G)</strong></strong> -<p><br>This parameter specifies the local path to which the home directory -will be connected (see <a href="../yodldocs/smb.conf.5.html#logonhome"><strong>"logon home"</strong></a>) and is only +<p><a name="loglevel"></a> +<p></p><dt><strong><strong>log level (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a>. +<p><a name="logondrive"></a> +<p></p><dt><strong><strong>logon drive (G)</strong></strong><dd> +<p>This parameter specifies the local path to which the home directory +will be connected (see <a href="smb.conf.5.html#logonhome"><strong>"logon home"</strong></a>) and is only used by NT Workstations. -<p><br>Note that this option is only useful if Samba is set up as a -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. -<p><br><strong>Example:</strong> +<p>Note that this option is only useful if Samba is set up as a +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. +<p><strong>Example:</strong> <code> logon drive = h:</code> -<p><br><a name="logonhome"></a> -<li><strong><strong>logon home (G)</strong></strong> -<p><br>This parameter specifies the home directory location when a Win95/98 or +<p><a name="logonhome"></a> +<p></p><dt><strong><strong>logon home (G)</strong></strong><dd> +<p>This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do -<p><br><code>"NET USE H: /HOME"</code> -<p><br>from a command prompt, for example. -<p><br>This option takes the standard substitutions, allowing you to have +<p><code>"NET USE H: /HOME"</code> +<p>from a command prompt, for example. +<p>This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. -<p><br>This parameter can be used with Win9X workstations to ensure that +<p>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: -<p><br><code>" logon home = \\%L\%U\profile"</code> -<p><br>This tells Samba to return the above string, with substitutions made +<p><code>" logon home = \\%L\%U\profile"</code> +<p>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 <code>"net use /home"</code>, but use the whole string when dealing with profiles. -<p><br>Note that in prior versions of Samba, the <code>"logon path"</code> was returned rather than +<p>Note that in prior versions of Samba, the <code>"logon path"</code> was returned rather than <code>"logon home"</code>. This broke <code>"net use /home"</code> but allowed profiles outside the home directory. The current implementation is correct, and can be used for profiles if you use the above trick. -<p><br>Note that this option is only useful if Samba is set up as a -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. -<p><br><strong>Example:</strong> +<p>Note that this option is only useful if Samba is set up as a +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. +<p><strong>Example:</strong> <code> logon home = "\\remote_smb_server\%U"</code> -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> logon home = "\\%N\%U"</code> -<p><br><a name="logonpath"></a> -<li><strong><strong>logon path (G)</strong></strong> -<p><br>This parameter specifies the home directory where roaming profiles +<p><a name="logonpath"></a> +<p></p><dt><strong><strong>logon path (G)</strong></strong><dd> +<p>This parameter specifies the home directory where roaming profiles (NTuser.dat etc files for Windows NT) are stored. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles. To find out how to handle roaming profiles for Win 9X system, see the <code>"logon home"</code> parameter. -<p><br>This option takes the standard substitutions, allowing you to have +<p>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 <code>"application data"</code>, (<code>"desktop"</code>, <code>"start menu"</code>, <code>"network neighborhood"</code>, <code>"programs"</code> and other folders, and their contents, are loaded and displayed on your Windows NT client. -<p><br>The share and the path must be readable by the user for the +<p>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 logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories. -<p><br>Thereafter, the directories and any of the contents can, if required, be +<p>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 <em>MAN</em>datory profile). -<p><br>Windows clients can sometimes maintain a connection to the [homes] +<p>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 <code>\\%N\HOMES\profile_path</code> will cause problems). -<p><br>This option takes the standard substitutions, allowing you to have +<p>This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. -<p><br>Note that this option is only useful if Samba is set up as a -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. -<p><br><strong>Default:</strong> +<p>Note that this option is only useful if Samba is set up as a +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. +<p><strong>Default:</strong> <code> logon path = \\%N\%U\profile</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> logon path = \\PROFILESERVER\HOME_DIR\%U\PROFILE</code> -<p><br><a name="logonscript"></a> -<li><strong><strong>logon script (G)</strong></strong> -<p><br>This parameter specifies the batch file (.bat) or NT command file +<p><a name="logonscript"></a> +<p></p><dt><strong><strong>logon script (G)</strong></strong><dd> +<p>This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS style cr/lf line endings. Using a DOS-style editor to create the file is recommended. -<p><br>The script must be a relative path to the <code>[netlogon]</code> service. If -the <code>[netlogon]</code> service specifies a <a href="../yodldocs/smb.conf.5.html#path"><strong>path</strong></a> of +<p>The script must be a relative path to the <code>[netlogon]</code> service. If +the <code>[netlogon]</code> service specifies a <a href="smb.conf.5.html#path"><strong>path</strong></a> of /usr/local/samba/netlogon, and logon script = STARTUP.BAT, then the file that will be downloaded is: -<p><br><code>/usr/local/samba/netlogon/STARTUP.BAT</code> -<p><br>The contents of the batch file is entirely your choice. A suggested +<p><code>/usr/local/samba/netlogon/STARTUP.BAT</code> +<p>The contents of the batch file is entirely your choice. A suggested command would be to add <code>NET TIME \\SERVER /SET /YES</code>, to force every machine to synchronize clocks with the same time server. Another use would be to add <code>NET USE U: \\SERVER\UTILS</code> for commonly used utilities, or <code>NET USE Q: \\SERVER\ISO9001_QA</code> for example. -<p><br>Note that it is particularly important not to allow write access to +<p>Note that it is particularly important not to allow write access to the <code>[netlogon]</code> 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. -<p><br>This option takes the standard substitutions, allowing you to have +<p>This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. -<p><br>Note that this option is only useful if Samba is set up as a -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. -<p><br><strong>Example:</strong> +<p>Note that this option is only useful if Samba is set up as a +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. +<p><strong>Example:</strong> <code> logon script = scripts\%U.bat</code> -<p><br><a name="lppausecommand"></a> -<li><strong><strong>lppause command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="lppausecommand"></a> +<p></p><dt><strong><strong>lppause command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job. -<p><br>This command should be a program or script which takes a printer name +<p>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. -<p><br>If a <code>"%p"</code> is given then the printername is put in its place. A +<p>If a <code>"%p"</code> is given then the printername is put in its place. A <code>"%j"</code> is replaced with the job number (an integer). On HPUX (see -<a href="../yodldocs/smb.conf.5.html#printing"><strong>printing=hpux</strong></a>), if the <code>"-p%p"</code> option is added +<a href="smb.conf.5.html#printing"><strong>printing=hpux</strong></a>), if the <code>"-p%p"</code> 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. -<p><br>Note that it is good practice to include the absolute path in the +<p>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. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. +<p><strong>Default:</strong> Currently no default value is given to this string, unless the -value of the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in +value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in which case the default is : -<p><br><code> lp -i %p-%j -H hold</code> -<p><br>or if the value of the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>, +<p><code> lp -i %p-%j -H hold</code> +<p>or if the value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>, then the default is: -<p><br><code> qstat -s -j%j -h</code> -<p><br><strong>Example for HPUX:</strong> +<p><code> qstat -s -j%j -h</code> +<p><strong>Example for HPUX:</strong> lppause command = /usr/bin/lpalt %p-%j -p0 -<p><br><a name="lpqcachetime"></a> -<li><strong><strong>lpq cache time (G)</strong></strong> -<p><br>This controls how long lpq info will be cached for to prevent the +<p><a name="lpqcachetime"></a> +<p></p><dt><strong><strong>lpq cache time (G)</strong></strong><dd> +<p>This controls how long lpq info will be cached for to prevent the <strong>lpq</strong> command being called too often. A separate cache is kept for each variation of the <strong>lpq</strong> command used by the system, so if you use different <strong>lpq</strong> commands for different users then they won't share cache information. -<p><br>The cache files are stored in <code>/tmp/lpq.xxxx</code> where xxxx is a hash of +<p>The cache files are stored in <code>/tmp/lpq.xxxx</code> where xxxx is a hash of the <strong>lpq</strong> command in use. -<p><br>The default is 10 seconds, meaning that the cached results of a +<p>The default is 10 seconds, meaning that the cached results of a previous identical <strong>lpq</strong> command will be used if the cached data is less than 10 seconds old. A large value may be advisable if your <strong>lpq</strong> command is very slow. -<p><br>A value of 0 will disable caching completely. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>A value of 0 will disable caching completely. +<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. +<p><strong>Default:</strong> <code> lpq cache time = 10</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> lpq cache time = 30</code> -<p><br><a name="lpqcommand"></a> -<li><strong><strong>lpq command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="lpqcommand"></a> +<p></p><dt><strong><strong>lpq command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to obtain <code>"lpq"</code>-style printer status information. -<p><br>This command should be a program or script which takes a printer name +<p>This command should be a program or script which takes a printer name as its only parameter and outputs printer status information. -<p><br>Currently eight styles of printer status information are supported; +<p>Currently eight styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX and SOFTQ. This covers most UNIX systems. You control which type is expected using the -<a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing ="</strong></a> option. -<p><br>Some clients (notably Windows for Workgroups) may not correctly send +<a href="smb.conf.5.html#printing"><strong>"printing ="</strong></a> option. +<p>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. -<p><br>If a <code>%p</code> is given then the printername is put in its place. Otherwise +<p>If a <code>%p</code> is given then the printername is put in its place. Otherwise it is placed at the end of the command. -<p><br>Note that it is good practice to include the absolute path in the <strong>lpq +<p>Note that it is good practice to include the absolute path in the <strong>lpq command</strong> as the PATH may not be available to the server. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. +<p><strong>Default:</strong> <code> depends on the setting of printing =</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> lpq command = /usr/bin/lpq %p</code> -<p><br><a name="lpresumecommand"></a> -<li><strong><strong>lpresume command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="lpresumecommand"></a> +<p></p><dt><strong><strong>lpresume command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job. -<p><br>This command should be a program or script which takes a printer name -and job number to resume the print job. See also the <a href="../yodldocs/smb.conf.5.html#lppausecommand"><strong>"lppause +<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 <a href="smb.conf.5.html#lppausecommand"><strong>"lppause command"</strong></a> parameter. -<p><br>If a <code>%p</code> is given then the printername is put in its place. A +<p>If a <code>%p</code> is given then the printername is put in its place. A <code>%j</code> is replaced with the job number (an integer). -<p><br>Note that it is good practice to include the absolute path in the <strong>lpresume +<p>Note that it is good practice to include the absolute path in the <strong>lpresume command</strong> as the PATH may not be available to the server. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. -<p><br><strong>Default:</strong> -<p><br>Currently no default value is given to this string, unless the -value of the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in +<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. +<p><strong>Default:</strong> +<p>Currently no default value is given to this string, unless the +value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in which case the default is : -<p><br><code> lp -i %p-%j -H resume</code> -<p><br>or if the value of the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>, +<p><code> lp -i %p-%j -H resume</code> +<p>or if the value of the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</code>, then the default is: -<p><br><code> qstat -s -j%j -r</code> -<p><br><strong>Example for HPUX:</strong> +<p><code> qstat -s -j%j -r</code> +<p><strong>Example for HPUX:</strong> <code> lpresume command = /usr/bin/lpalt %p-%j -p2</code> -<p><br><a name="lprmcommand"></a> -<li><strong><strong>lprm command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="lprmcommand"></a> +<p></p><dt><strong><strong>lprm command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to delete a print job. -<p><br>This command should be a program or script which takes a printer name +<p>This command should be a program or script which takes a printer name and job number, and deletes the print job. -<p><br>If a <code>%p</code> is given then the printername is put in its place. A +<p>If a <code>%p</code> is given then the printername is put in its place. A <code>%j</code> is replaced with the job number (an integer). -<p><br>Note that it is good practice to include the absolute path in the +<p>Note that it is good practice to include the absolute path in the <strong>lprm command</strong> as the PATH may not be available to the server. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter. +<p><strong>Default:</strong> <code> depends on the setting of "printing ="</code> -<p><br><strong>Example 1:</strong> +<p><strong>Example 1:</strong> <code> lprm command = /usr/bin/lprm -P%p %j</code> -<p><br><strong>Example 2:</strong> +<p><strong>Example 2:</strong> <code> lprm command = /usr/bin/cancel %p-%j</code> -<p><br><a name="machinepasswordtimeout"></a> -<li><strong><strong>machine password timeout (G)</strong></strong> -<p><br>If a Samba server is a member of an Windows NT Domain (see the -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter) then +<p><a name="machinepasswordtimeout"></a> +<p></p><dt><strong><strong>machine password timeout (G)</strong></strong><dd> +<p>If a Samba server is a member of an Windows NT Domain (see the +<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter) then periodically a running <a href="smbd.8.html"><strong>smbd</strong></a> process will try and change the <strong>MACHINE ACCOUNT PASWORD</strong> stored in the file called <code><Domain>.<Machine>.mac</code> where <code><Domain></code> is the name of the Domain we are a member of and <code><Machine></code> is the primary -<a href="../yodldocs/smb.conf.5.html#netbiosname"><strong>"NetBIOS name"</strong></a> of the machine +<a href="smb.conf.5.html#netbiosname"><strong>"NetBIOS name"</strong></a> of the machine <a href="smbd.8.html"><strong>smbd</strong></a> is running on. 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. -<p><br>See also <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, and the -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter. -<p><br><strong>Default:</strong> +<p>See also <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, and the +<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter. +<p><strong>Default:</strong> <code> machine password timeout = 604800</code> -<p><br><a name="magicoutput"></a> -<li><strong><strong>magic output (S)</strong></strong> -<p><br>This parameter specifies the name of a file which will contain output -created by a magic script (see the <a href="../yodldocs/smb.conf.5.html#magicscript"><strong>"magic +<p><a name="magicoutput"></a> +<p></p><dt><strong><strong>magic output (S)</strong></strong><dd> +<p>This parameter specifies the name of a file which will contain output +created by a magic script (see the <a href="smb.conf.5.html#magicscript"><strong>"magic script"</strong></a> parameter below). -<p><br>Warning: If two clients use the same <a href="../yodldocs/smb.conf.5.html#magicscript"><strong>"magic +<p>Warning: If two clients use the same <a href="smb.conf.5.html#magicscript"><strong>"magic script"</strong></a> in the same directory the output file content is undefined. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> magic output = <magic script name>.out</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> magic output = myfile.txt</code> -<p><br><a name="magicscript"></a> -<li><strong><strong>magic script (S)</strong></strong> -<p><br>This parameter specifies the name of a file which, if opened, will be +<p><a name="magicscript"></a> +<p></p><dt><strong><strong>magic script (S)</strong></strong><dd> +<p>This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user. -<p><br>Scripts executed in this way will be deleted upon completion, +<p>Scripts executed in this way will be deleted upon completion, permissions permitting. -<p><br>If the script generates output, output will be sent to the file -specified by the <a href="../yodldocs/smb.conf.5.html#magicoutput"><strong>"magic output"</strong></a> parameter (see +<p>If the script generates output, output will be sent to the file +specified by the <a href="smb.conf.5.html#magicoutput"><strong>"magic output"</strong></a> parameter (see above). -<p><br>Note that some shells are unable to interpret scripts containing +<p>Note that some shells are unable to interpret scripts containing carriage-return-linefeed instead of linefeed as the end-of-line marker. Magic scripts must be executable <em>"as is"</em> on the host, which for some hosts and some shells will require filtering at the DOS end. -<p><br>Magic scripts are <em>EXPERIMENTAL</em> and should <em>NOT</em> be relied upon. -<p><br><strong>Default:</strong> +<p>Magic scripts are <em>EXPERIMENTAL</em> and should <em>NOT</em> be relied upon. +<p><strong>Default:</strong> <code> None. Magic scripts disabled.</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> magic script = user.csh</code> -<p><br><a name="manglecase"></a> -<li><strong><strong>mangle case (S)</strong></strong> -<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>. -<p><br><a name="manglelocks"></a> -<li><strong><strong>mangle locks (S)</strong></strong> -<p><br>This option is was introduced with Samba 2.0.4 and above and has been +<p><a name="manglecase"></a> +<p></p><dt><strong><strong>mangle case (S)</strong></strong><dd> +<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>. +<p><a name="manglelocks"></a> +<p></p><dt><strong><strong>mangle locks (S)</strong></strong><dd> +<p>This option is was introduced with Samba 2.0.4 and above and has been removed in Samba 2.0.6 as Samba now dynamically configures such things on 32 bit systems. -<p><br><a name="mangledmap"></a> -<li><strong><strong>mangled map (S)</strong></strong> -<p><br>This is for those who want to directly map UNIX file names which can +<p><a name="mangledmap"></a> +<p></p><dt><strong><strong>mangled map (S)</strong></strong><dd> +<p>This is for those who want to directly map UNIX file names which can not be represented on Windows/DOS. The mangling of names is not always what is 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 <code>".html"</code> for HTML files, whereas under Windows/DOS <code>".htm"</code> is more commonly used. -<p><br>So to map <code>"html"</code> to <code>"htm"</code> you would use: -<p><br><code> mangled map = (*.html *.htm)</code> -<p><br>One very useful case is to remove the annoying <code>";1"</code> off the ends +<p>So to map <code>"html"</code> to <code>"htm"</code> you would use: +<p><code> mangled map = (*.html *.htm)</code> +<p>One very useful case is to remove the annoying <code>";1"</code> off the ends of filenames on some CDROMS (only visible under some UNIXs). To do this use a map of (*;1 *). -<p><br><strong>default:</strong> +<p><strong>default:</strong> <code> no mangled map</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> mangled map = (*;1 *)</code> -<p><br><a name="manglednames"></a> -<li><strong><strong>mangled names (S)</strong></strong> -<p><br>This controls whether non-DOS names under UNIX should be mapped to +<p><a name="manglednames"></a> +<p></p><dt><strong><strong>mangled names (S)</strong></strong><dd> +<p>This controls whether non-DOS names under UNIX should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored. -<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for details +<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for details on how to control the mangling process. -<p><br>If mangling is used then the mangling algorithm is as follows: -<p><br><ul> -<p><br><li > The first (up to) five alphanumeric characters before the +<p>If mangling is used then the mangling algorithm is as follows: +<p><dl> +<p><li > The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters of the mangled name. -<p><br><li > A tilde <code>"~"</code> is appended to the first part of the mangled +<p><li > A tilde <code>"~"</code> is appended to the first part of the mangled name, followed 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. -<p><br>Note that the character to use may be specified using the -<a href="../yodldocs/smb.conf.5.html#manglingchar"><strong>"mangling char"</strong></a> option, if you don't like +<p>Note that the character to use may be specified using the +<a href="smb.conf.5.html#manglingchar"><strong>"mangling char"</strong></a> option, if you don't like <code>'~'</code>. -<p><br><li > The first three alphanumeric characters of the final extension +<p><li > The first three alphanumeric characters of the final extension are preserved, forced to upper case and appear as the extension of the mangled name. The final extension is defined as that part of the original filename after the rightmost dot. If there are no dots in the filename, the mangled name will have no extension (except in the case -of <a href="../yodldocs/smb.conf.5.html#hidefiles"><strong>"hidden files"</strong></a> - see below). -<p><br><li > Files whose UNIX name begins with a dot will be presented as DOS +of <a href="smb.conf.5.html#hidefiles"><strong>"hidden files"</strong></a> - see below). +<p><li > Files whose UNIX name begins with a dot will be presented as DOS hidden files. The mangled name will be created as for other filenames, but with the leading dot removed and <code>"___"</code> as its extension regardless of actual original extension (that's three underscores). -<p><br></ul> -<p><br>The two-digit hash value consists of upper case alphanumeric +<p></dl> +<p>The two-digit hash value consists of upper case alphanumeric characters. -<p><br>This algorithm can cause name collisions only if files in a directory +<p>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. -<p><br>The name mangling (if enabled) allows a file to be copied between UNIX +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> mangled names = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> mangled names = no</code> -<p><br><a name="manglingchar"></a> -<li><strong><strong>mangling char (S)</strong></strong> -<p><br>This controls what character is used as the <em>"magic"</em> character in -<a href="../yodldocs/smb.conf.5.html#manglednames"><strong>name mangling</strong></a>. The default is a <code>'~'</code> but +<p><a name="manglingchar"></a> +<p></p><dt><strong><strong>mangling char (S)</strong></strong><dd> +<p>This controls what character is used as the <em>"magic"</em> character in +<a href="smb.conf.5.html#manglednames"><strong>name mangling</strong></a>. The default is a <code>'~'</code> but this may interfere with some software. Use this option to set it to whatever you prefer. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> mangling char = ~</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> mangling char = ^</code> -<p><br><a name="mangledstack"></a> -<li><strong><strong>mangled stack (G)</strong></strong> -<p><br>This parameter controls the number of mangled names that should be +<p><a name="mangledstack"></a> +<p></p><dt><strong><strong>mangled stack (G)</strong></strong><dd> +<p>This parameter controls the number of mangled names that should be cached in the Samba server <a href="smbd.8.html"><strong>smbd</strong></a>. -<p><br>This stack is a list of recently mangled base names (extensions are +<p>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). -<p><br>The larger this value, the more likely it is that mangled names can be +<p>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 access. Smaller stacks save memory in the server (each stack element costs 256 bytes). -<p><br>It is not possible to absolutely guarantee correct long file names, so +<p>It is not possible to absolutely guarantee correct long file names, so be prepared for some surprises! -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> mangled stack = 50</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> mangled stack = 100</code> -<p><br><a name="maparchive"></a> -<li><strong><strong>map archive (S)</strong></strong> -<p><br>This controls whether the DOS archive attribute should be mapped to +<p><a name="maparchive"></a> +<p></p><dt><strong><strong>map archive (S)</strong></strong><dd> +<p>This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit. The DOS archive bit is set when a file has been modified since its last backup. One motivation for this option it to keep Samba/your PC from making any file it touches from becoming executable under UNIX. This can be quite annoying for shared source code, documents, etc... -<p><br>Note that this requires the <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> +<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> parameter to be set such that owner execute bit is not masked out -(i.e. it must include 100). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create +(i.e. it must include 100). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> map archive = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> map archive = no</code> -<p><br><a name="maphidden"></a> -<li><strong><strong>map hidden (S)</strong></strong> -<p><br>This controls whether DOS style hidden files should be mapped to the +<p><a name="maphidden"></a> +<p></p><dt><strong><strong>map hidden (S)</strong></strong><dd> +<p>This controls whether DOS style hidden files should be mapped to the UNIX world execute bit. -<p><br>Note that this requires the <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be +<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be set such that the world execute bit is not masked out (i.e. it must -include 001). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> +include 001). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> map hidden = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> map hidden = yes</code> -<p><br><a name="mapsystem"></a> -<li><strong><strong>map system (S)</strong></strong> -<p><br>This controls whether DOS style system files should be mapped to the +<p><a name="mapsystem"></a> +<p></p><dt><strong><strong>map system (S)</strong></strong><dd> +<p>This controls whether DOS style system files should be mapped to the UNIX group execute bit. -<p><br>Note that this requires the <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be +<p>Note that this requires the <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be set such that the group execute bit is not masked out (i.e. it must -include 010). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a> +include 010). See the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> map system = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> map system = yes</code> -<p><br><a name="maptoguest"></a> -<li><strong><strong>map to guest (G)</strong></strong> -<p><br>This parameter is only useful in <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> modes -other than <a href="../yodldocs/smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> - i.e. user, +<p><a name="maptoguest"></a> +<p></p><dt><strong><strong>map to guest (G)</strong></strong><dd> +<p>This parameter is only useful in <a href="smb.conf.5.html#security"><strong>security</strong></a> modes +other than <a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> - i.e. user, server, and domain. -<p><br>This parameter can take three different values, which tell +<p>This parameter can take three different values, which tell <a href="smbd.8.html"><strong>smbd</strong></a> what to do with user login requests that don't match a valid UNIX user in some way. -<p><br>The three settings are : -<p><br><ul> -<p><br><li > <strong>"Never"</strong> - Means user login requests with an invalid password +<p>The three settings are : +<p><dl> +<p><li > <strong>"Never"</strong> - Means user login requests with an invalid password are rejected. This is the default. -<p><br><li > <strong>"Bad User"</strong> - Means user logins with an invalid password are +<p><li > <strong>"Bad User"</strong> - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is -treated as a guest login and mapped into the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest +treated as a guest login and mapped into the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. -<p><br><li > <strong>"Bad Password"</strong> - Means user logins with an invalid +<p><li > <strong>"Bad Password"</strong> - Means user logins with an invalid password are treated as a guest login and mapped into the -<a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. Note that this can +<a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on a <strong>"guest"</strong> - and will not know the reason they cannot access files they think @@ -2657,291 +2657,291 @@ they should - there will have been no message given to them that they got their password wrong. Helpdesk services will <em>*hate*</em> you if you set the <strong>"map to guest"</strong> parameter this way :-). -<p><br></ul> -<p><br>Note that this parameter is needed to set up <strong>"Guest"</strong> share -services when using <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> modes other than +<p></dl> +<p>Note that this parameter is needed to set up <strong>"Guest"</strong> share +services when using <a href="smb.conf.5.html#security"><strong>security</strong></a> modes other than share. This is because in these modes the name of the resource being requested is <em>*not*</em> 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 <strong>"Guest"</strong> shares. -<p><br>For people familiar with the older Samba releases, this parameter +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> map to guest = Never</code> <strong>Example</strong>: <code> map to guest = Bad User</code> -<p><br><a name="maxconnections"></a> -<li><strong><strong>max connections (S)</strong></strong> -<p><br>This option allows the number of simultaneous connections to a service +<p><a name="maxconnections"></a> +<p></p><dt><strong><strong>max connections (S)</strong></strong><dd> +<p>This option allows the number of simultaneous connections to a service to be limited. If <strong>"max connections"</strong> is greater than 0 then connections will be refused if this number of connections to the service are already open. A value of zero mean an unlimited number of connections may be made. -<p><br>Record lock files are used to implement this feature. The lock files -will be stored in the directory specified by the <a href="../yodldocs/smb.conf.5.html#lockdirectory"><strong>"lock +<p>Record lock files are used to implement this feature. The lock files +will be stored in the directory specified by the <a href="smb.conf.5.html#lockdirectory"><strong>"lock directory"</strong></a> option. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> max connections = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> max connections = 10</code> -<p><br><a name="maxdisksize"></a> -<li><strong><strong>max disk size (G)</strong></strong> -<p><br>This option allows you to put an upper limit on the apparent size of +<p><a name="maxdisksize"></a> +<p></p><dt><strong><strong>max disk size (G)</strong></strong><dd> +<p>This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size. -<p><br>Note that this option does not limit the amount of data you can put on +<p>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 <strong>"max disk size"</strong>. -<p><br>This option is primarily useful to work around bugs in some pieces of +<p>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. -<p><br>A <strong>"max disk size"</strong> of 0 means no limit. -<p><br><strong>Default:</strong> +<p>A <strong>"max disk size"</strong> of 0 means no limit. +<p><strong>Default:</strong> <code> max disk size = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> max disk size = 1000</code> -<p><br><a name="maxlogsize"></a> -<li><strong><strong>max log size (G)</strong></strong> -<p><br>This option (an integer in kilobytes) specifies the max size the log +<p><a name="maxlogsize"></a> +<p></p><dt><strong><strong>max log size (G)</strong></strong><dd> +<p>This option (an integer in kilobytes) specifies the max size the log file should grow to. Samba periodically checks the size and if it is exceeded it will rename the file, adding a <code>".old"</code> extension. -<p><br>A size of 0 means no limit. -<p><br><strong>Default:</strong> +<p>A size of 0 means no limit. +<p><strong>Default:</strong> <code> max log size = 5000</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> max log size = 1000</code> -<p><br><a name="maxmux"></a> -<li><strong><strong>max mux (G)</strong></strong> -<p><br>This option controls the maximum number of outstanding simultaneous +<p><a name="maxmux"></a> +<p></p><dt><strong><strong>max mux (G)</strong></strong><dd> +<p>This option controls the maximum number of outstanding simultaneous SMB operations that samba tells the client it will allow. You should never need to set this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> max mux = 50</code> -<p><br><a name="maxopenfiles"></a> -<li><strong><strong>max open files (G)</strong></strong> -<p><br>This parameter limits the maximum number of open files that one +<p><a name="maxopenfiles"></a> +<p></p><dt><strong><strong>max open files (G)</strong></strong><dd> +<p>This parameter limits the maximum number of open files that one <a href="smbd.8.html"><strong>smbd</strong></a> file serving process may have open for a client at any one time. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file. -<p><br>The limit of the number of open files is usually set by the +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> max open files = 10000</code> -<p><br><a name="maxpacket"></a> -<li><strong><strong>max packet (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#packetsize"><strong>"packet size"</strong></a>. -<p><br><a name="maxttl"></a> -<li><strong><strong>max ttl (G)</strong></strong> -<p><br>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> what the default 'time +<p><a name="maxpacket"></a> +<p></p><dt><strong><strong>max packet (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#packetsize"><strong>"packet size"</strong></a>. +<p><a name="maxttl"></a> +<p></p><dt><strong><strong>max ttl (G)</strong></strong><dd> +<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> what the default 'time to live' of NetBIOS names should be (in seconds) when <a href="nmbd.8.html"><strong>nmbd</strong></a> is requesting a name using either a broadcast packet or from a WINS server. You should never need to change this parameter. The default is 3 days. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> max ttl = 259200</code> -<p><br><a name="maxwinsttl"></a> -<li><strong><strong>max wins ttl (G)</strong></strong> -<p><br>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS -server <a href="../yodldocs/smb.conf.5.html#winssupport"><strong>(wins support =true)</strong></a> what the maximum +<p><a name="maxwinsttl"></a> +<p></p><dt><strong><strong>max wins ttl (G)</strong></strong><dd> +<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS +server <a href="smb.conf.5.html#winssupport"><strong>(wins support =true)</strong></a> what the maximum 'time to live' of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will grant will be (in seconds). You should never need to change this parameter. The default is 6 days (518400 seconds). -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#minwinsttl"><strong>"min wins ttl"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#minwinsttl"><strong>"min wins ttl"</strong></a> parameter. +<p><strong>Default:</strong> <code> max wins ttl = 518400</code> -<p><br><a name="maxxmit"></a> -<li><strong><strong>max xmit (G)</strong></strong> -<p><br>This option controls the maximum packet size that will be negotiated +<p><a name="maxxmit"></a> +<p></p><dt><strong><strong>max xmit (G)</strong></strong><dd> +<p>This option controls the maximum packet size that will be negotiated by Samba. The default is 65535, which is the maximum. In some cases you may find you get better performance with a smaller value. A value below 2048 is likely to cause problems. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> max xmit = 65535</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> max xmit = 8192</code> -<p><br><a name="messagecommand"></a> -<li><strong><strong>message command (G)</strong></strong> -<p><br>This specifies what command to run when the server receives a WinPopup +<p><a name="messagecommand"></a> +<p></p><dt><strong><strong>message command (G)</strong></strong><dd> +<p>This specifies what command to run when the server receives a WinPopup style message. -<p><br>This would normally be a command that would deliver the message +<p>This would normally be a command that would deliver the message somehow. How this is to be done is up to your imagination. -<p><br>An example is: -<p><br><code> message command = csh -c 'xedit %s;rm %s' &</code> -<p><br>This delivers the message using <strong>xedit</strong>, then removes it +<p>An example is: +<p><code> message command = csh -c 'xedit %s;rm %s' &</code> +<p>This delivers the message using <strong>xedit</strong>, then removes it afterwards. <em>NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY</em>. That's why I have the <code>'&'</code> on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30secs, hopefully). -<p><br>All messages are delivered as the global guest user. The command takes -the standard substitutions, although <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a> won't work -(<a href="../yodldocs/smb.conf.5.html#percentU"><strong>%U</strong></a> may be better in this case). -<p><br>Apart from the standard substitutions, some additional ones apply. In +<p>All messages are delivered as the global guest user. The command takes +the standard substitutions, although <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> won't work +(<a href="smb.conf.5.html#percentU"><strong>%U</strong></a> may be better in this case). +<p>Apart from the standard substitutions, some additional ones apply. In particular: -<p><br><ul> -<p><br><li > <code>"%s"</code> = the filename containing the message. -<p><br><li > <code>"%t"</code> = the destination that the message was sent to (probably the server +<p><dl> +<p><li > <code>"%s"</code> = the filename containing the message. +<p><li > <code>"%t"</code> = the destination that the message was sent to (probably the server name). -<p><br><li > <code>"%f"</code> = who the message is from. -<p><br></ul> -<p><br>You could make this command send mail, or whatever else takes your +<p><li > <code>"%f"</code> = who the message is from. +<p></dl> +<p>You could make this command send mail, or whatever else takes your fancy. Please let us know of any really interesting ideas you have. -<p><br>Here's a way of sending the messages as mail to root: -<p><br><code>message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s</code> -<p><br>If you don't have a message command then the message won't be +<p>Here's a way of sending the messages as mail to root: +<p><code>message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s</code> +<p>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. -<p><br>If you want to silently delete it then try: -<p><br><code>"message command = rm %s"</code>. -<p><br><strong>Default:</strong> +<p>If you want to silently delete it then try: +<p><code>"message command = rm %s"</code>. +<p><strong>Default:</strong> <code> no message command</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> message command = csh -c 'xedit %s;rm %s' &</code> -<p><br><a name="minprintspace"></a> -<li><strong><strong>min print space (S)</strong></strong> -<p><br>This sets the minimum amount of free disk space that must be available +<p><a name="minprintspace"></a> +<p></p><dt><strong><strong>min print space (S)</strong></strong><dd> +<p>This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job. It is specified in kilobytes. The default is 0, which means a user can always spool a print job. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>printing</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#printing"><strong>printing</strong></a> parameter. +<p><strong>Default:</strong> <code> min print space = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> min print space = 2000</code> -<p><br><a name="minpasswdlength"></a> -<li><strong><strong>min passwd length (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#minpasswordlength"><strong>"min password length"</strong></a>. -<p><br><a name="minpasswordlength"></a> -<li><strong><strong>min password length (G)</strong></strong> -<p><br>This option sets the minimum length in characters of a plaintext password +<p><a name="minpasswdlength"></a> +<p></p><dt><strong><strong>min passwd length (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#minpasswordlength"><strong>"min password length"</strong></a>. +<p><a name="minpasswordlength"></a> +<p></p><dt><strong><strong>min password length (G)</strong></strong><dd> +<p>This option sets the minimum length in characters of a plaintext password than smbd will accept when performing UNIX password changing. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="../yodldocs/smb.conf.5.html#passwdchatdebug"><strong>"passwd chat +<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>, +<a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="smb.conf.5.html#passwdchatdebug"><strong>"passwd chat debug"</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> min password length = 5</code> -<p><br><a name="minwinsttl"></a> -<li><strong><strong>min wins ttl (G)</strong></strong> -<p><br>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS -server <a href="../yodldocs/smb.conf.5.html#winssupport"><strong>(wins support = true)</strong></a> what the minimum +<p><a name="minwinsttl"></a> +<p></p><dt><strong><strong>min wins ttl (G)</strong></strong><dd> +<p>This option tells <a href="nmbd.8.html"><strong>nmbd</strong></a> when acting as a WINS +server <a href="smb.conf.5.html#winssupport"><strong>(wins support = true)</strong></a> what the minimum 'time to live' of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will grant will be (in seconds). You should never need to change this parameter. The default is 6 hours (21600 seconds). -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> min wins ttl = 21600</code> -<p><br><a name="nameresolveorder"></a> -<li><strong><strong>name resolve order (G)</strong></strong> -<p><br>This option is used by the programs in the Samba suite to determine +<p><a name="nameresolveorder"></a> +<p></p><dt><strong><strong>name resolve order (G)</strong></strong><dd> +<p>This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space separated string of different name resolution options. -<p><br>The options are :"lmhosts", "host", "wins" and "bcast". They cause +<p>The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows : -<p><br><ul> -<p><br><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. +<p><dl> +<p><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html"><strong>lmhosts (5)</strong></a> for details) then any name type matches for lookup. -<p><br><li > <strong>host</strong> : Do a standard host name to IP address resolution, +<p><li > <strong>host</strong> : Do a standard host name to IP address resolution, using the system /etc/hosts, NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the <em>/etc/nsswitch.conf</em> file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored. -<p><br><li > <strong>wins</strong> : Query a name with the IP address listed in the -<a href="../yodldocs/smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter. If no WINS server has +<p><li > <strong>wins</strong> : Query a name with the IP address listed in the +<a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter. If no WINS server has been specified this method will be ignored. -<p><br><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces -listed in the <a href="../yodldocs/smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter. This is the +<p><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces +listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet. -<p><br></ul> -<p><br><strong>Default:</strong> +<p></dl> +<p><strong>Default:</strong> <code> name resolve order = lmhosts host wins bcast</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> name resolve order = lmhosts bcast host</code> -<p><br>This will cause the local lmhosts file to be examined first, followed +<p>This will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup. -<p><br><a name="netbiosaliases"></a> -<li><strong><strong>netbios aliases (G)</strong></strong> -<p><br>This is a list of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will +<p><a name="netbiosaliases"></a> +<p></p><dt><strong><strong>netbios aliases (G)</strong></strong><dd> +<p>This is a list of NetBIOS names that <a href="nmbd.8.html"><strong>nmbd</strong></a> will advertise as additional names by which the Samba server is known. This allows one machine to appear in browse lists under multiple names. If -a machine is acting as a <a href="../yodldocs/smb.conf.5.html#localmaster"><strong>browse server</strong></a> or -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a> none of these names will be +a machine is acting as a <a href="smb.conf.5.html#localmaster"><strong>browse server</strong></a> or +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a> none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#netbiosname"><strong>"netbios name"</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#netbiosname"><strong>"netbios name"</strong></a>. +<p><strong>Default:</strong> <code> empty string (no additional names)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> netbios aliases = TEST TEST1 TEST2</code> -<p><br><a name="netbiosname"></a> -<li><strong><strong>netbios name (G)</strong></strong> -<p><br>This sets the NetBIOS name by which a Samba server is known. By +<p><a name="netbiosname"></a> +<p></p><dt><strong><strong>netbios name (G)</strong></strong><dd> +<p>This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host's DNS name. -If a machine is a <a href="../yodldocs/smb.conf.5.html#localmaster"><strong>browse server</strong></a> or -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a> this name (or the first component +If a machine is a <a href="smb.conf.5.html#localmaster"><strong>browse server</strong></a> or +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a> this name (or the first component of the hosts DNS name) will be the name that these services are advertised under. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#netbiosaliases"><strong>"netbios aliases"</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#netbiosaliases"><strong>"netbios aliases"</strong></a>. +<p><strong>Default:</strong> <code> Machine DNS name.</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> netbios name = MYNAME</code> -<p><br><a name="netbiosscope"></a> -<li><strong><strong>netbios scope (G)</strong></strong> -<p><br>This sets the NetBIOS scope that Samba will operate under. This should +<p><a name="netbiosscope"></a> +<p></p><dt><strong><strong>netbios scope (G)</strong></strong><dd> +<p>This sets the NetBIOS scope that Samba will operate under. This should not be set unless every machine on your LAN also sets this value. -<p><br><a name="nishomedir"></a> -<li><strong><strong>nis homedir (G)</strong></strong> -<p><br>Get the home share server from a NIS map. For UNIX systems that use an +<p><a name="nishomedir"></a> +<p></p><dt><strong><strong>nis homedir (G)</strong></strong><dd> +<p>Get the home share server from a NIS map. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server. -<p><br>When the Samba logon server is not the actual home directory server, +<p>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. -<p><br>This option allows Samba to return the home share as being on a +<p>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 -<a href="../yodldocs/smb.conf.5.html#homedirmap"><strong>"homedir map"</strong></a> and return the server listed +<a href="smb.conf.5.html#homedirmap"><strong>"homedir map"</strong></a> and return the server listed there. -<p><br>Note that for this option to work there must be a working NIS +<p>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 -<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. -<p><br><strong>Default:</strong> +<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>. +<p><strong>Default:</strong> <code> nis homedir = false</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> nis homedir = true</code> -<p><br><a name="ntaclsupport"></a> -<li><strong><strong>nt acl support (G)</strong></strong> -<p><br>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> +<p><a name="ntaclsupport"></a> +<p></p><dt><strong><strong>nt acl support (G)</strong></strong><dd> +<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will attempt to map UNIX permissions into Windows NT access control lists. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> nt acl support = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> nt acl support = no</code> -<p><br><a name="ntpipesupport"></a> -<li><strong><strong>nt pipe support (G)</strong></strong> -<p><br>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> +<p><a name="ntpipesupport"></a> +<p></p><dt><strong><strong>nt pipe support (G)</strong></strong><dd> +<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will allow Windows NT clients to connect to the NT SMB specific <code>IPC$</code> pipes. This is a developer debugging option and can be left alone. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> nt pipe support = yes</code> -<p><br><a name="ntsmbsupport"></a> -<li><strong><strong>nt smb support (G)</strong></strong> -<p><br>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> +<p><a name="ntsmbsupport"></a> +<p></p><dt><strong><strong>nt smb support (G)</strong></strong><dd> +<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will negotiate NT specific SMB support with Windows NT clients. Although this is a developer debugging option and should be left alone, benchmarking has discovered that Windows NT clients give @@ -2950,19 +2950,19 @@ being investigated. If this option is set to <code>"no"</code> then Samba offers exactly the same SMB calls that versions prior to Samba2.0 offered. This information may be of use if any users are having problems with NT SMB support. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> nt support = yes</code> -<p><br><a name="nullpasswords"></a> -<li><strong><strong>null passwords (G)</strong></strong> -<p><br>Allow or disallow client access to accounts that have null passwords. -<p><br>See also <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a>. -<p><br><strong>Default:</strong> +<p><a name="nullpasswords"></a> +<p></p><dt><strong><strong>null passwords (G)</strong></strong><dd> +<p>Allow or disallow client access to accounts that have null passwords. +<p>See also <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a>. +<p><strong>Default:</strong> <code> null passwords = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> null passwords = yes</code> -<p><br><a name="olelockingcompatibility"></a> -<li><strong><strong>ole locking compatibility (G)</strong></strong> -<p><br>This parameter allows an administrator to turn off the byte range lock +<p><a name="olelockingcompatibility"></a> +<p></p><dt><strong><strong>ole locking compatibility (G)</strong></strong><dd> +<p>This parameter allows an administrator to turn off the byte range lock manipulation that is done within Samba to give compatibility for OLE applications. Windows OLE applications use byte range locking as a form of inter-process communication, by locking ranges of bytes around @@ -2970,467 +2970,467 @@ the 2^32 region of a file range. This can cause certain UNIX lock managers to crash or otherwise cause problems. Setting this parameter to <code>"no"</code> means you trust your UNIX lock manager to handle such cases correctly. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ole locking compatibility = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> ole locking compatibility = no</code> -<p><br><a name="onlyguest"></a> -<li><strong><strong>only guest (S)</strong></strong> -<p><br>A synonym for <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>. -<p><br><a name="onlyuser"></a> -<li><strong><strong>only user (S)</strong></strong> -<p><br>This is a boolean option that controls whether connections with -usernames not in the <a href="../yodldocs/smb.conf.5.html#user"><strong>user=</strong></a> list will be allowed. By +<p><a name="onlyguest"></a> +<p></p><dt><strong><strong>only guest (S)</strong></strong><dd> +<p>A synonym for <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>. +<p><a name="onlyuser"></a> +<p></p><dt><strong><strong>only user (S)</strong></strong><dd> +<p>This is a boolean option that controls whether connections with +usernames not in the <a href="smb.conf.5.html#user"><strong>user=</strong></a> list will be allowed. By default this option is disabled so a client can supply a username to be used by the server. -<p><br>Note that this also means Samba won't try to deduce usernames from the -service name. This can be annoying for the <a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> -section. To get around this you could use "<a href="../yodldocs/smb.conf.5.html#user"><strong>user</strong></a> = -<a href="../yodldocs/smb.conf.5.html#percentS"><strong>%S</strong></a>" which means your <a href="../yodldocs/smb.conf.5.html#user"><strong>"user"</strong></a> list +<p>Note that this also means Samba won't try to deduce usernames from the +service name. This can be annoying for the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> +section. To get around this you could use "<a href="smb.conf.5.html#user"><strong>user</strong></a> = +<a href="smb.conf.5.html#percentS"><strong>%S</strong></a>" which means your <a href="smb.conf.5.html#user"><strong>"user"</strong></a> list will be just the service name, which for home directories is the name of the user. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#user"><strong>user</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#user"><strong>user</strong></a> parameter. +<p><strong>Default:</strong> <code> only user = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> only user = True</code> -<p><br><a name="oplocks"></a> -<li><strong><strong>oplocks (S)</strong></strong> -<p><br>This boolean option tells smbd whether to issue oplocks (opportunistic +<p><a name="oplocks"></a> +<p></p><dt><strong><strong>oplocks (S)</strong></strong><dd> +<p>This boolean option tells smbd whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients to aggressively cache files locally and you may want to disable this option for unreliable network environments (it is turned on by default in Windows NT Servers). For more information see the file Speed.txt in the Samba docs/ directory. -<p><br>Oplocks may be selectively turned off on certain files on a per share basis. +<p>Oplocks may be selectively turned off on certain files on a per share basis. 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 <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> parameter +UNIX process. See the <a href="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> parameter for details. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> and -<a href="../yodldocs/smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a> parameters. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> and +<a href="smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a> parameters. +<p><strong>Default:</strong> <code> oplocks = True</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> oplocks = False</code> -<p><br><a name="oplockbreakwaittime"></a> -<li><strong><strong>oplock break wait time (G)</strong></strong> -<p><br>This is a tuning parameter added due to bugs in both Windows 9x and WinNT. +<p><a name="oplockbreakwaittime"></a> +<p></p><dt><strong><strong>oplock break wait time (G)</strong></strong><dd> +<p>This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the client redirector can fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients. -<p><br><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA +<p><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE</em>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> oplock break wait time = 10</code> -<p><br><a name="oplockcontentionlimit"></a> -<li><strong><strong>oplock contention limit (S)</strong></strong> -<p><br>This is a <em>very</em> advanced <a href="smbd.8.html"><strong>smbd</strong></a> tuning option to improve +<p><a name="oplockcontentionlimit"></a> +<p></p><dt><strong><strong>oplock contention limit (S)</strong></strong><dd> +<p>This is a <em>very</em> advanced <a href="smbd.8.html"><strong>smbd</strong></a> tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file. -<p><br>In brief it specifies a number, which causes smbd not to grant an oplock even +<p>In brief it specifies a number, which causes smbd not 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 <a href="smbd.8.html"><strong>smbd</strong></a> to behave in a similar way to Windows NT. -<p><br><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA +<p><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE</em>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> oplock contention limit = 2</code> -<p><br><a name="oslevel"></a> -<li><strong><strong>os level (G)</strong></strong> -<p><br>This integer value controls what level Samba advertises itself as for +<p><a name="oslevel"></a> +<p></p><dt><strong><strong>os level (G)</strong></strong><dd> +<p>This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether <a href="nmbd.8.html"><strong>nmbd</strong></a> has a chance of becoming a local master -browser for the <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>WORKGROUP</strong></a> in the local broadcast +browser for the <a href="smb.conf.5.html#workgroup"><strong>WORKGROUP</strong></a> in the local broadcast area. The default is zero, which means <a href="nmbd.8.html"><strong>nmbd</strong></a> will lose elections to Windows machines. See BROWSING.txt in the Samba docs/ directory for details. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> os level = 20</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> os level = 65 ; This will win against any NT Server</code> -<p><br><a name="packetsize"></a> -<li><strong><strong>packet size (G)</strong></strong> -<p><br>This is a deprecated parameter that has no effect on the current +<p><a name="packetsize"></a> +<p></p><dt><strong><strong>packet size (G)</strong></strong><dd> +<p>This is a deprecated parameter that has no effect on the current Samba code. It is left in the parameter list to prevent breaking old <strong>smb.conf</strong> files. -<p><br><a name="panicaction"></a> -<li><strong><strong>panic action (G)</strong></strong> -<p><br>This is a Samba developer option that allows a system command to be +<p><a name="panicaction"></a> +<p></p><dt><strong><strong>panic action (G)</strong></strong><dd> +<p>This is a Samba developer option that allows a system command to be called when either <a href="smbd.8.html"><strong>smbd</strong></a> or <a href="nmbd.8.html"><strong>nmbd</strong></a> crashes. This is usually used to draw attention to the fact that a problem occurred. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> panic action = <empty string></code> -<p><br><a name="passwdchat"></a> -<li><strong><strong>passwd chat (G)</strong></strong> -<p><br>This string controls the <em>"chat"</em> conversation that takes places +<p><a name="passwdchat"></a> +<p></p><dt><strong><strong>passwd chat (G)</strong></strong><dd> +<p>This string controls the <em>"chat"</em> conversation that takes places between <a href="smbd.8.html"><strong>smbd</strong></a> and the local password changing program to change the users password. The string describes a sequence of response-receive pairs that <a href="smbd.8.html"><strong>smbd</strong></a> uses to -determine what to send to the <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>passwd</strong></a> program +determine what to send to the <a href="smb.conf.5.html#passwdprogram"><strong>passwd</strong></a> program and what to expect back. If the expected output is not received then the password is not changed. -<p><br>This chat sequence is often quite site specific, depending on what +<p>This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc). -<p><br>The string can contain the macros <code>"%o"</code> and <code>"%n"</code> which are +<p>The string can contain the macros <code>"%o"</code> and <code>"%n"</code> which are substituted for the old and new passwords respectively. It can also contain the standard macros <code>"\n"</code>, <code>"\r"</code>, <code>"\t"</code> and <code>"\s"</code> to give line-feed, carriage-return, tab and space. -<p><br>The string can also contain a <code>'*'</code> which matches any sequence of +<p>The string can also contain a <code>'*'</code> which matches any sequence of characters. -<p><br>Double quotes can be used to collect strings with spaces in them into +<p>Double quotes can be used to collect strings with spaces in them into a single string. -<p><br>If the send string in any part of the chat sequence is a fullstop +<p>If the send string in any part of the chat sequence is a fullstop <code>"."</code> then no string is sent. Similarly, is the expect string is a fullstop then no string is expected. -<p><br>Note that if the <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> +<p>Note that if the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is set to true, then this sequence is called <em>*AS ROOT*</em> when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext. In this case the old password cleartext is set to <code>""</code> (the empty string). -<p><br>See also <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="../yodldocs/smb.conf.5.html#passwdchatdebug"><strong>"passwd chat +<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>, +<a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and <a href="smb.conf.5.html#passwdchatdebug"><strong>"passwd chat debug"</strong></a>. -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <pre> passwd chat = "*Enter OLD password*" %o\n "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*" </pre> -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <pre> passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed* </pre> -<p><br><a name="passwdchatdebug"></a> -<li><strong><strong>passwd chat debug (G)</strong></strong> -<p><br>This boolean specifies if the passwd chat script parameter is run in +<p><a name="passwdchatdebug"></a> +<p></p><dt><strong><strong>passwd chat debug (G)</strong></strong><dd> +<p>This boolean specifies if the passwd chat script parameter is run in <code>"debug"</code> mode. In this mode the strings passed to and received from the passwd chat are printed in the <a href="smbd.8.html"><strong>smbd</strong></a> log with -a <a href="../yodldocs/smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> of 100. This is a dangerous +a <a href="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> of 100. This is a dangerous option as it will allow plaintext passwords to be seen in the <a href="smbd.8.html"><strong>smbd</strong></a> log. It is available to help Samba admins -debug their <a href="../yodldocs/smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a> scripts when calling -the <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and should be turned off +debug their <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a> scripts when calling +the <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> and should be turned off after this has been done. This parameter is off by default. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a>, <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd +<p>See also <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a>, <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>. -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> passwd chat debug = True</code> -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> passwd chat debug = False</code> -<p><br><a name="passwdprogram"></a> -<li><strong><strong>passwd program (G)</strong></strong> -<p><br>The name of a program that can be used to set UNIX user passwords. -Any occurrences of <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a> will be replaced with the +<p><a name="passwdprogram"></a> +<p></p><dt><strong><strong>passwd program (G)</strong></strong><dd> +<p>The name of a program that can be used to set UNIX user passwords. +Any occurrences of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> will be replaced with the user name. The user name is checked for existence before calling the password changing program. -<p><br>Also note that many passwd programs insist in <em>"reasonable"</em> +<p>Also note that many passwd programs insist in <em>"reasonable"</em> 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. -<p><br><em>Note</em> that if the <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> +<p><em>Note</em> that if the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is set to <code>"True"</code> then this program is called <em>*AS ROOT*</em> before the SMB password in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is changed. If this UNIX password change fails, then <a href="smbd.8.html"><strong>smbd</strong></a> will fail to change the SMB password also (this is by design). -<p><br>If the <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is +<p>If the <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is set this parameter <em>MUST USE ABSOLUTE PATHS</em> for <em>ALL</em> programs called, and must be examined for security implications. Note that by -default <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> is set to +default <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> is set to <code>"False"</code>. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>. +<p><strong>Default:</strong> <code> passwd program = /bin/passwd</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> passwd program = /sbin/passwd %u</code> -<p><br><a name="passwordlevel"></a> -<li><strong><strong>password level (G)</strong></strong> -<p><br>Some client/server combinations have difficulty with mixed-case +<p><a name="passwordlevel"></a> +<p></p><dt><strong><strong>password level (G)</strong></strong><dd> +<p>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! -<p><br>This parameter defines the maximum number of characters that may be +<p>This parameter defines the maximum number of characters that may be upper case in passwords. -<p><br>For example, say the password given was <code>"FRED"</code>. If <strong>password +<p>For example, say the password given was <code>"FRED"</code>. If <strong>password level</strong> is set to 1, the following combinations would be tried if <code>"FRED"</code> failed: -<p><br><code>"Fred"</code>, <code>"fred"</code>, <code>"fRed"</code>, <code>"frEd"</code>, <code>"freD"</code> -<p><br>If <strong>password level</strong> was set to 2, the following combinations would +<p><code>"Fred"</code>, <code>"fred"</code>, <code>"fRed"</code>, <code>"frEd"</code>, <code>"freD"</code> +<p>If <strong>password level</strong> was set to 2, the following combinations would also be tried: -<p><br><code>"FRed"</code>, <code>"FrEd"</code>, <code>"FreD"</code>, <code>"fREd"</code>, <code>"fReD"</code>, +<p><code>"FRed"</code>, <code>"FrEd"</code>, <code>"FreD"</code>, <code>"fREd"</code>, <code>"fReD"</code>, <code>"frED"</code>, <code>..</code> -<p><br>And so on. -<p><br>The higher value this parameter is set to the more likely it is that a +<p>And so on. +<p>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. -<p><br>A value of zero will cause only two attempts to be made - the password +<p>A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> password level = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> password level = 4</code> -<p><br><a name="passwordserver"></a> -<li><strong><strong>password server (G)</strong></strong> -<p><br>By specifying the name of another SMB server (such as a WinNT box) -with this option, and using <a href="../yodldocs/smb.conf.5.html#security"><strong>"security = domain"</strong></a> or -<a href="../yodldocs/smb.conf.5.html#security"><strong>"security = server"</strong></a> you can get Samba to do all +<p><a name="passwordserver"></a> +<p></p><dt><strong><strong>password server (G)</strong></strong><dd> +<p>By specifying the name of another SMB server (such as a WinNT box) +with this option, and using <a href="smb.conf.5.html#security"><strong>"security = domain"</strong></a> or +<a href="smb.conf.5.html#security"><strong>"security = server"</strong></a> you can get Samba to do all its username/password validation via a remote server. -<p><br>This options sets the name of the password server to use. It must be a +<p>This options 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 <strong>smb.conf</strong> file. -<p><br>The name of the password server is looked up using the parameter -<a href="../yodldocs/smb.conf.5.html#nameresolveorder"><strong>"name resolve order="</strong></a> and so may resolved +<p>The name of the password server is looked up using the parameter +<a href="smb.conf.5.html#nameresolveorder"><strong>"name resolve order="</strong></a> and so may resolved by any method and order described in that parameter. -<p><br>The password server much be a machine capable of using the "LM1.2X002" +<p>The password server much be a machine capable of using the "LM1.2X002" or the "LM NT 0.12" protocol, and it must be in user level security mode. -<p><br>NOTE: Using a password server means your UNIX box (running Samba) is +<p>NOTE: Using a password server means your UNIX box (running Samba) is only as secure as your password server. <em>DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST</em>. -<p><br>Never point a Samba server at itself for password serving. This will +<p>Never point a Samba server at itself for password serving. This will cause a loop and could lock up your Samba server! -<p><br>The name of the password server takes the standard substitutions, but -probably the only useful one is <a href="../yodldocs/smb.conf.5.html#percentm"><strong>%m</strong></a>, which means +<p>The name of the password server takes the standard substitutions, but +probably the only useful one is <a href="smb.conf.5.html#percentm"><strong>%m</strong></a>, 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 better restrict them with hosts allow! -<p><br>If the <a href="../yodldocs/smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to +<p>If the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to <strong>"domain"</strong>, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the -<a href="../yodldocs/smb.conf.5.html#workgroup"><strong>Domain</strong></a> or the character <code>*</code>, as the Samba server is cryptographicly +<a href="smb.conf.5.html#workgroup"><strong>Domain</strong></a> or the character <code>*</code>, as the Samba server is cryptographicly in that domain, and will use cryptographicly authenticated RPC calls to authenticate the user logging on. The advantage of using -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> is that if you list +<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> is that if you list several hosts in the <strong>"password server"</strong> option then <a href="smbd.8.html"><strong>smbd</strong></a> will try each in turn till it finds one that responds. This is useful in case your primary server goes down. -<p><br>If the <strong>"password server"</strong> option is set to the character <code>*</code>, +<p>If the <strong>"password server"</strong> option is set to the character <code>*</code>, then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name <code>WORKGROUP<1C></code> and then contacting each server returned in the list of IP addresses -from the <a href="../yodldocs/smb.conf.5.html#nameresolveorder"><strong>name resolution</strong></a> source. -<p><br>If the <a href="../yodldocs/smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>"server"</strong></a>, then there are different -restrictions that <a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> +from the <a href="smb.conf.5.html#nameresolveorder"><strong>name resolution</strong></a> source. +<p>If the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to +<a href="smb.conf.5.html#securityequalserver"><strong>"server"</strong></a>, then there are different +restrictions that <a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> doesn't suffer from: -<p><br><ul> -<p><br><li > You may list several password servers in the <strong>"password server"</strong> +<p><dl> +<p><li > You may list several password servers in the <strong>"password server"</strong> parameter, however if an <a href="smbd.8.html"><strong>smbd</strong></a> makes a connection to a password server, and then the password server fails, no more users will be able to be authenticated from this <a href="smbd.8.html"><strong>smbd</strong></a>. This is a restriction of the SMB/CIFS -protocol when in <a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode +protocol when in <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode and cannot be fixed in Samba. -<p><br><li > If you are using a Windows NT server as your password server then +<p><li > If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode the network +<a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode the network logon will appear to come from there rather than from the users workstation. -<p><br></ul> -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#security"><strong>"security"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p></dl> +<p>See also the <a href="smb.conf.5.html#security"><strong>"security"</strong></a> parameter. +<p><strong>Default:</strong> <code> password server = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> password server = NT-PDC, NT-BDC1, NT-BDC2</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> password server = *</code> -<p><br><a name="path"></a> -<li><strong><strong>path (S)</strong></strong> -<p><br>This parameter specifies a directory to which the user of the service +<p><a name="path"></a> +<p></p><dt><strong><strong>path (S)</strong></strong><dd> +<p>This parameter specifies a directory to which the user of the service is to be given access. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing. -<p><br>For a printable service offering guest access, the service should be +<p>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. -<p><br>Any occurrences of <a href="../yodldocs/smb.conf.5.html#percentu"><strong>%u</strong></a> in the path will be replaced +<p>Any occurrences of <a href="smb.conf.5.html#percentu"><strong>%u</strong></a> in the path will be replaced with the UNIX username that the client is using on this -connection. Any occurrences of <a href="../yodldocs/smb.conf.5.html#percentm"><strong>%m</strong></a> will be replaced +connection. Any occurrences of <a href="smb.conf.5.html#percentm"><strong>%m</strong></a> 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. -<p><br>Note that this path will be based on <a href="../yodldocs/smb.conf.5.html#rootdir"><strong>"root dir"</strong></a> if +<p>Note that this path will be based on <a href="smb.conf.5.html#rootdir"><strong>"root dir"</strong></a> if one was specified. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> none</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> path = /home/fred</code> -<p><br><a name="postexec"></a> -<li><strong><strong>postexec (S)</strong></strong> -<p><br>This option specifies a command to be run whenever the service is +<p><a name="postexec"></a> +<p></p><dt><strong><strong>postexec (S)</strong></strong><dd> +<p>This option specifies a command to be run whenever the service is disconnected. It takes the usual substitutions. The command may be run as the root on some systems. -<p><br>An interesting example may be do unmount server resources: -<p><br><code>postexec = /etc/umount /cdrom</code> -<p><br>See also <a href="../yodldocs/smb.conf.5.html#preexec"><strong>preexec</strong></a>. -<p><br><strong>Default:</strong> +<p>An interesting example may be do unmount server resources: +<p><code>postexec = /etc/umount /cdrom</code> +<p>See also <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>. +<p><strong>Default:</strong> <code> none (no command executed)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> postexec = echo "%u disconnected from %S from %m (%I)" >> /tmp/log</code> -<p><br><a name="postscript"></a> -<li><strong><strong>postscript (S)</strong></strong> -<p><br>This parameter forces a printer to interpret the print files as +<p><a name="postscript"></a> +<p></p><dt><strong><strong>postscript (S)</strong></strong><dd> +<p>This parameter forces a printer to interpret the print files as postscript. This is done by adding a <code>%!</code> to the start of print output. -<p><br>This is most useful when you have lots of PCs that persist in putting +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> postscript = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> postscript = True</code> -<p><br><a name="preexec"></a> -<li><strong><strong>preexec (S)</strong></strong> -<p><br>This option specifies a command to be run whenever the service is +<p><a name="preexec"></a> +<p></p><dt><strong><strong>preexec (S)</strong></strong><dd> +<p>This option specifies a command to be run whenever the service is connected to. It takes the usual substitutions. -<p><br>An interesting example is to send the users a welcome message every +<p>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: -<p><br><pre> +<p><pre> preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' & </pre> -<p><br>Of course, this could get annoying after a while :-) -<p><br>See also <a href="../yodldocs/smb.conf.5.html#preexecclose"><strong>preexec close</strong></a> and <a href="../yodldocs/smb.conf.5.html#postexec"><strong>postexec</strong></a>. -<p><br><strong>Default:</strong> +<p>Of course, this could get annoying after a while :-) +<p>See also <a href="smb.conf.5.html#preexecclose"><strong>preexec close</strong></a> and <a href="smb.conf.5.html#postexec"><strong>postexec</strong></a>. +<p><strong>Default:</strong> <code> none (no command executed)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log</code> -<p><br><a name="preexecclose"></a> -<li><strong><strong>preexec close (S)</strong></strong> -<p><br>This boolean option controls whether a non-zero return code from -<a href="../yodldocs/smb.conf.5.html#preexec"><strong>"preexec"</strong></a> should close the service being connected to. -<p><br><strong>Default:</strong> +<p><a name="preexecclose"></a> +<p></p><dt><strong><strong>preexec close (S)</strong></strong><dd> +<p>This boolean option controls whether a non-zero return code from +<a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> should close the service being connected to. +<p><strong>Default:</strong> <code> preexec close = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> preexec close = yes</code> -<p><br><a name="preferredmaster"></a> -<li><strong><strong>preferred master (G)</strong></strong> -<p><br>This boolean parameter controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> is a +<p><a name="preferredmaster"></a> +<p></p><dt><strong><strong>preferred master (G)</strong></strong><dd> +<p>This boolean parameter controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> is a preferred master browser for its workgroup. -<p><br>If this is set to true, on startup, <a href="nmbd.8.html"><strong>nmbd</strong></a> will +<p>If this is set to true, on startup, <a href="nmbd.8.html"><strong>nmbd</strong></a> 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 <a href="../yodldocs/smb.conf.5.html#domainmaster"><strong>"domain master = yes"</strong></a>, so +conjunction with <a href="smb.conf.5.html#domainmaster"><strong>"domain master = yes"</strong></a>, so that <a href="nmbd.8.html"><strong>nmbd</strong></a> can guarantee becoming a domain master. -<p><br>Use this option with caution, because if there are several hosts +<p>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. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#oslevel"><strong>os level</strong></a>. -<p><br><strong>Default:</strong> +<p>See also <a href="smb.conf.5.html#oslevel"><strong>os level</strong></a>. +<p><strong>Default:</strong> <code> preferred master = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> preferred master = yes</code> -<p><br><a name="preferedmaster"></a> -<li><strong><strong>prefered master (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#preferredmaster"><strong>"preferred master"</strong></a> for people +<p><a name="preferedmaster"></a> +<p></p><dt><strong><strong>prefered master (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#preferredmaster"><strong>"preferred master"</strong></a> for people who cannot spell :-). -<p><br><a name="preload"></a> -<li><strong><strong>preload</strong></strong> -Synonym for <a href="../yodldocs/smb.conf.5.html#autoservices"><strong>"auto services"</strong></a>. -<p><br><a name="preservecase"></a> -<li><strong><strong>preserve case (S)</strong></strong> -<p><br>This controls if new filenames are created with the case that the +<p><a name="preload"></a> +<p></p><dt><strong><strong>preload</strong></strong><dd> +Synonym for <a href="smb.conf.5.html#autoservices"><strong>"auto services"</strong></a>. +<p><a name="preservecase"></a> +<p></p><dt><strong><strong>preserve case (S)</strong></strong><dd> +<p>This controls if new filenames are created with the case that the client passes, or if they are forced to be the <code>"default"</code> case. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> preserve case = yes</code> -<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for a +<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for a fuller discussion. -<p><br><a name="printcommand"></a> -<li><strong><strong>print command (S)</strong></strong> -<p><br>After a print job has finished spooling to a service, this command +<p><a name="printcommand"></a> +<p></p><dt><strong><strong>print command (S)</strong></strong><dd> +<p>After a print job has finished spooling to a service, this command will be used via a <code>system()</code> call to process the spool file. Typically the command specified will submit the spool file to the host's printing subsystem, but there is no requirement that this be the case. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files. -<p><br>The print command is simply a text string. It will be used verbatim, +<p>The print command is simply a text string. It will be used verbatim, with two exceptions: All occurrences of <code>"%s"</code> and <code>"%f"</code> will be replaced by the appropriate spool file name, and all occurrences of <code>"%p"</code> will be replaced by the appropriate printer name. The spool file name is generated automatically by the server, the printer name is discussed below. -<p><br>The print command <em>MUST</em> contain at least one occurrence of <code>"%s"</code> +<p>The print command <em>MUST</em> contain at least one occurrence of <code>"%s"</code> or <code>"%f"</code> - the <code>"%p"</code> is optional. At the time a job is submitted, if no printer name is supplied the <code>"%p"</code> will be silently removed from the printer command. -<p><br>If specified in the <a href="../yodldocs/smb.conf.5.html#global"><strong>"[global]"</strong></a> section, the print +<p>If specified in the <a href="smb.conf.5.html#global"><strong>"[global]"</strong></a> section, the print command given will be used for any printable service that does not have its own print command specified. -<p><br>If there is neither a specified print command for a printable service +<p>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. -<p><br>Note that printing may fail on some UNIXs from the <code>"nobody"</code> +<p>Note that printing may fail on some UNIXs from the <code>"nobody"</code> account. If this happens then create an alternative guest account that -can print and set the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a> in the -<a href="../yodldocs/smb.conf.5.html#global"><strong>"[global]"</strong></a> section. -<p><br>You can form quite complex print commands by realizing that they are +can print and set the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a> in the +<a href="smb.conf.5.html#global"><strong>"[global]"</strong></a> section. +<p>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 <code>';'</code> is the usual separator for command in shell scripts. -<p><br><code>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</code> -<p><br>You may have to vary this command considerably depending on how you +<p><code>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</code> +<p>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 <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing="</strong></a> +varies depending on the setting of the <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> parameter. -<p><br><strong>Default:</strong> - For <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing="</strong></a> BSD, AIX, QNX, LPRNG or PLP : +<p><strong>Default:</strong> + For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> BSD, AIX, QNX, LPRNG or PLP : <code> print command = lpr -r -P%p %s</code> -<p><br>For <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing="</strong></a> SYS or HPUX : +<p>For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> SYS or HPUX : <code> print command = lp -c -d%p %s; rm %s</code> -<p><br>For <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing="</strong></a> SOFTQ : +<p>For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> SOFTQ : <code> print command = lp -d%p -s %s; rm %s</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> print command = /usr/local/samba/bin/myprintscript %p %s</code> -<p><br><a name="printok"></a> -<li><strong><strong>print ok (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#printable"><strong>printable</strong></a>. -<p><br><a name="printable"></a> -<li><strong><strong>printable (S)</strong></strong> -<p><br>If this parameter is <code>"yes"</code>, then clients may open, write to and +<p><a name="printok"></a> +<p></p><dt><strong><strong>print ok (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#printable"><strong>printable</strong></a>. +<p><a name="printable"></a> +<p></p><dt><strong><strong>printable (S)</strong></strong><dd> +<p>If this parameter is <code>"yes"</code>, then clients may open, write to and submit spool files on the directory specified for the service. -<p><br>Note that a printable service will ALWAYS allow writing to the service +<p>Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data. The -<a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a> parameter controls only non-printing +<a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> parameter controls only non-printing access to the resource. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> printable = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> printable = yes</code> -<p><br><a name="printcap"></a> -<li><strong><strong>printcap (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>printcapname</strong></a>. -<p><br><a name="printcapname"></a> -<li><strong><strong>printcap name (G)</strong></strong> -<p><br>This parameter may be used to override the compiled-in default +<p><a name="printcap"></a> +<p></p><dt><strong><strong>printcap (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#printcapname"><strong>printcapname</strong></a>. +<p><a name="printcapname"></a> +<p></p><dt><strong><strong>printcap name (G)</strong></strong><dd> +<p>This parameter may be used to override the compiled-in default printcap name used by the server (usually /etc/printcap). See the -discussion of the <a href="../yodldocs/smb.conf.5.html#printers"><strong>[printers]</strong></a> section above for +discussion of the <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> section above for reasons why you might want to do this. -<p><br>On System V systems that use <strong>lpstat</strong> to list available printers you +<p>On System V systems that use <strong>lpstat</strong> to list available printers you can use <code>"printcap name = lpstat"</code> 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 <strong>"printcap name"</strong> is set to <strong>lpstat</strong> on these systems then Samba will launch <code>"lpstat -v"</code> and attempt to parse the output to obtain a printer list. -<p><br>A minimal printcap file would look something like this: -<p><br><pre> +<p>A minimal printcap file would look something like this: +<p><pre> print1|My Printer 1 print2|My Printer 2 @@ -3440,287 +3440,287 @@ to obtain a printer list. </pre> -<p><br>where the <code>'|'</code> separates aliases of a printer. The fact that the +<p>where the <code>'|'</code> 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. -<p><br><em>NOTE</em>: Under AIX the default printcap name is +<p><em>NOTE</em>: Under AIX the default printcap name is <code>"/etc/qconfig"</code>. Samba will assume the file is in AIX <code>"qconfig"</code> format if the string <code>"/qconfig"</code> appears in the printcap filename. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> printcap name = /etc/printcap</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> printcap name = /etc/myprintcap</code> -<p><br><a name="printer"></a> -<li><strong><strong>printer (S)</strong></strong> -<p><br>This parameter specifies the name of the printer to which print jobs +<p><a name="printer"></a> +<p></p><dt><strong><strong>printer (S)</strong></strong><dd> +<p>This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent. -<p><br>If specified in the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> section, the printer +<p>If specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section, the printer name given will be used for any printable service that does not have its own printer name specified. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> none (but may be <code>"lp"</code> on many systems) -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> printer name = laserwriter -<p><br><a name="printerdriver"></a> -<li><strong><strong>printer driver (S)</strong></strong> -<p><br>This option allows you to control the string that clients receive when +<p><a name="printerdriver"></a> +<p></p><dt><strong><strong>printer driver (S)</strong></strong><dd> +<p>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 WindowsNT then you can use this to automate the setup of printers on your system. -<p><br>You need to set this parameter to the exact string (case sensitive) +<p>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 <strong>"printer driver"</strong> option set and the client will give you a list of printer drivers. The appropriate strings are shown in a scrollbox after you have chosen the printer manufacturer. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>. -<p><br><strong>Example:</strong> +<p>See also <a href="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>. +<p><strong>Example:</strong> printer driver = HP LaserJet 4L -<p><br><a name="printerdriverfile"></a> -<li><strong><strong>printer driver file (G)</strong></strong> -<p><br>This parameter tells Samba where the printer driver definition file, +<p><a name="printerdriverfile"></a> +<p></p><dt><strong><strong>printer driver file (G)</strong></strong><dd> +<p>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 : -<p><br><code>SAMBA_INSTALL_DIRECTORY/lib/printers.def</code> -<p><br>This file is created from Windows 95 <code>"msprint.def"</code> files found on +<p><code>SAMBA_INSTALL_DIRECTORY/lib/printers.def</code> +<p>This file is created from Windows 95 <code>"msprint.def"</code> files found on the Windows 95 client system. For more details on setting up serving of printer drivers to Windows 95 clients, see the documentation file in the docs/ directory, PRINTER_DRIVER.txt. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> None (set in compile).</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> printer driver file = /usr/local/samba/printers/drivers.def</code> -<p><br>See also <a href="../yodldocs/smb.conf.5.html#printerdriverlocation"><strong>"printer driver location"</strong></a>. -<p><br><a name="printerdriverlocation"></a> -<li><strong><strong>printer driver location (S)</strong></strong> -<p><br>This parameter tells clients of a particular printer share where to +<p>See also <a href="smb.conf.5.html#printerdriverlocation"><strong>"printer driver location"</strong></a>. +<p><a name="printerdriverlocation"></a> +<p></p><dt><strong><strong>printer driver location (S)</strong></strong><dd> +<p>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 -<p><br><code>\\MACHINE\PRINTER$</code> -<p><br>Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$ +<p><code>\\MACHINE\PRINTER$</code> +<p>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 documentation file in the docs/ directory, PRINTER_DRIVER.txt. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> None</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> printer driver location = \\MACHINE\PRINTER$</code> -<p><br>See also <a href="../yodldocs/smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>. -<p><br><a name="printername"></a> -<li><strong><strong>printer name (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#printer"><strong>printer</strong></a>. -<p><br><a name="printing"></a> -<li><strong><strong>printing (S)</strong></strong> -<p><br>This parameters controls how printer status information is interpreted +<p>See also <a href="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>. +<p><a name="printername"></a> +<p></p><dt><strong><strong>printer name (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#printer"><strong>printer</strong></a>. +<p><a name="printing"></a> +<p></p><dt><strong><strong>printing (S)</strong></strong><dd> +<p>This parameters controls how printer status information is interpreted on your system. It also affects the default values for the -<a href="../yodldocs/smb.conf.5.html#printcommand"><strong>"print command"</strong></a>, <a href="../yodldocs/smb.conf.5.html#lpqcommand"><strong>"lpq -command"</strong></a> <a href="../yodldocs/smb.conf.5.html#lppausecommand"><strong>"lppause command"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#lpresumecommand"><strong>"lpresume command"</strong></a>, and <a href="../yodldocs/smb.conf.5.html#lprmcommand"><strong>"lprm -command"</strong></a> if specified in the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> +<a href="smb.conf.5.html#printcommand"><strong>"print command"</strong></a>, <a href="smb.conf.5.html#lpqcommand"><strong>"lpq +command"</strong></a> <a href="smb.conf.5.html#lppausecommand"><strong>"lppause command"</strong></a>, +<a href="smb.conf.5.html#lpresumecommand"><strong>"lpresume command"</strong></a>, and <a href="smb.conf.5.html#lprmcommand"><strong>"lprm +command"</strong></a> if specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section. -<p><br>Currently eight printing styles are supported. They are +<p>Currently eight printing styles are supported. They are <strong>"printing=BSD"</strong>, <strong>"printing=AIX"</strong>, <strong>"printing=LPRNG"</strong>, <strong>"printing=PLP"</strong>, <strong>"printing=SYSV"</strong>, <strong>"printing="HPUX"</strong>, <strong>"printing=QNX"</strong>, <strong>"printing=SOFTQ"</strong>, and <strong>"printing=CUPS"</strong>. -<p><br>To see what the defaults are for the other print commands when using +<p>To see what the defaults are for the other print commands when using the various options use the <a href="testparm.1.html"><strong>"testparm"</strong></a> program. -<p><br>This option can be set on a per printer basis -<p><br>See also the discussion in the <a href="../yodldocs/smb.conf.5.html#printers"><strong>[printers]</strong></a> section. -<p><br><a name="protocol"></a> -<li><strong><strong>protocol (G)</strong></strong> -<p><br>The value of the parameter (a string) is the highest protocol level +<p>This option can be set on a per printer basis +<p>See also the discussion in the <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> section. +<p><a name="protocol"></a> +<p></p><dt><strong><strong>protocol (G)</strong></strong><dd> +<p>The value of the parameter (a string) is the highest protocol level that will be supported by the server. -<p><br>Possible values are : -<p><br><ul> -<p><br><li > CORE: Earliest version. No concept of user names. -<p><br><li > COREPLUS: Slight improvements on CORE for efficiency. -<p><br><li > LANMAN1: First <em>"modern"</em> version of the protocol. Long +<p>Possible values are : +<p><dl> +<p><li > CORE: Earliest version. No concept of user names. +<p><li > COREPLUS: Slight improvements on CORE for efficiency. +<p><li > LANMAN1: First <em>"modern"</em> version of the protocol. Long filename support. -<p><br><li > LANMAN2: Updates to Lanman1 protocol. -<p><br><li > NT1: Current up to date version of the protocol. Used by Windows +<p><li > LANMAN2: Updates to Lanman1 protocol. +<p><li > NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS. -<p><br></ul> -<p><br>Normally this option should not be set as the automatic negotiation +<p></dl> +<p>Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> protocol = NT1</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> protocol = LANMAN1</code> -<p><br><a name="public"></a> -<li><strong><strong>public (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#guestok"><strong>"guest ok"</strong></a>. -<p><br><a name="queuepausecommand"></a> -<li><strong><strong>queuepause command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="public"></a> +<p></p><dt><strong><strong>public (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a>. +<p><a name="queuepausecommand"></a> +<p></p><dt><strong><strong>queuepause command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to pause the printerqueue. -<p><br>This command should be a program or script which takes a printer name +<p>This command should be a program or script which takes a printer name as its only parameter and stops the printerqueue, such that no longer jobs are submitted to the printer. -<p><br>This command is not supported by Windows for Workgroups, but can be +<p>This command is not supported by Windows for Workgroups, but can be issued from the Printer's window under Windows 95 & NT. -<p><br>If a <code>"%p"</code> is given then the printername is put in its +<p>If a <code>"%p"</code> is given then the printername is put in its place. Otherwise it is placed at the end of the command. -<p><br>Note that it is good practice to include the absolute path in the +<p>Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> depends on the setting of "printing ="</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> queuepause command = disable %p</code> -<p><br><a name="queueresumecommand"></a> -<li><strong><strong>queueresume command (S)</strong></strong> -<p><br>This parameter specifies the command to be executed on the server host +<p><a name="queueresumecommand"></a> +<p></p><dt><strong><strong>queueresume command (S)</strong></strong><dd> +<p>This parameter specifies the command to be executed on the server host in order to resume the printerqueue. It is the command to undo the behavior that is caused by the previous parameter -(<a href="../yodldocs/smb.conf.5.html#queuepausecommand"><strong>"queuepause command</strong></a>). -<p><br>This command should be a program or script which takes a printer name +(<a href="smb.conf.5.html#queuepausecommand"><strong>"queuepause command</strong></a>). +<p>This command should be a program or script which takes a printer name as its only parameter and resumes the printerqueue, such that queued jobs are resubmitted to the printer. -<p><br>This command is not supported by Windows for Workgroups, but can be +<p>This command is not supported by Windows for Workgroups, but can be issued from the Printer's window under Windows 95 & NT. -<p><br>If a <code>"%p"</code> is given then the printername is put in its +<p>If a <code>"%p"</code> is given then the printername is put in its place. Otherwise it is placed at the end of the command. -<p><br>Note that it is good practice to include the absolute path in the +<p>Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> depends on the setting of "printing ="</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> queuepause command = enable %p</code> -<p><br><a name="readbmpx"></a> -<li><strong><strong>read bmpx (G)</strong></strong> -<p><br>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> +<p><a name="readbmpx"></a> +<p></p><dt><strong><strong>read bmpx (G)</strong></strong><dd> +<p>This boolean parameter controls whether <a href="smbd.8.html"><strong>smbd</strong></a> will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to off. You should never need to set this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> read bmpx = No -<p><br><a name="readlist"></a> -<li><strong><strong>read list (S)</strong></strong> -<p><br>This is a list of users that are given read-only access to a +<p><a name="readlist"></a> +<p></p><dt><strong><strong>read list (S)</strong></strong><dd> +<p>This is a list of users that are given read-only access to a service. If the connecting user is in this list then they will not be -given write access, no matter what the <a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a> +given write access, no matter what the <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> option is set to. The list can include group names using the syntax -described in the <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#writelist"><strong>"write list"</strong></a> parameter and -the <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter. -<p><br><strong>Default:</strong> +described in the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter. +<p>See also the <a href="smb.conf.5.html#writelist"><strong>"write list"</strong></a> parameter and +the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter. +<p><strong>Default:</strong> <code> read list = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> read list = mary, @students</code> -<p><br><a name="readonly"></a> -<li><strong><strong>read only (S)</strong></strong> -<p><br>Note that this is an inverted synonym for -<a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a>. -<p><br><a name="readprediction"></a> -<li><strong><strong>read prediction (G)</strong></strong> -<p><br><em>NOTE</em>: This code is currently disabled in Samba2.0 and +<p><a name="readonly"></a> +<p></p><dt><strong><strong>read only (S)</strong></strong><dd> +<p>Note that this is an inverted synonym for +<a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a>. +<p><a name="readprediction"></a> +<p></p><dt><strong><strong>read prediction (G)</strong></strong><dd> +<p><em>NOTE</em>: This code is currently disabled in Samba2.0 and may be removed at a later date. Hence this parameter has no effect. -<p><br>This options enables or disables the read prediction code used to +<p>This options enables or disables the read prediction code used to speed up reads from the server. When enabled the server will try to pre-read data from the last accessed file that was opened read-only while waiting for packets. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> read prediction = False</code> -<p><br><a name="readraw"></a> -<li><strong><strong>read raw (G)</strong></strong> -<p><br>This parameter controls whether or not the server will support the raw +<p><a name="readraw"></a> +<p></p><dt><strong><strong>read raw (G)</strong></strong><dd> +<p>This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients. -<p><br>If enabled, raw reads allow reads of 65535 bytes in one packet. This +<p>If enabled, raw reads allow reads of 65535 bytes in one packet. This typically provides a major performance benefit. -<p><br>However, some clients either negotiate the allowable block size +<p>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. -<p><br>In general this parameter should be viewed as a system tuning tool and left -severely alone. See also <a href="../yodldocs/smb.conf.5.html#writeraw"><strong>"write raw"</strong></a>. -<p><br><strong>Default:</strong> +<p>In general this parameter should be viewed as a system tuning tool and left +severely alone. See also <a href="smb.conf.5.html#writeraw"><strong>"write raw"</strong></a>. +<p><strong>Default:</strong> <code> read raw = yes</code> -<p><br><a name="readsize"></a> -<li><strong><strong>read size (G)</strong></strong> -<p><br>The option <strong>"read size"</strong> affects the overlap of disk reads/writes +<p><a name="readsize"></a> +<p></p><dt><strong><strong>read size (G)</strong></strong><dd> +<p>The option <strong>"read size"</strong> affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing the data before it has received the whole packet from the network, or in the case of SMBreadbraw, it begins writing to the network before all the data has been read from disk. -<p><br>This overlapping works best when the speeds of disk and network access +<p>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. -<p><br>The default value is 16384, but very little experimentation has been +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> read size = 16384</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> read size = 8192</code> -<p><br><a name="remoteannounce"></a> -<li><strong><strong>remote announce (G)</strong></strong> -<p><br>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> to +<p><a name="remoteannounce"></a> +<p></p><dt><strong><strong>remote announce (G)</strong></strong><dd> +<p>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name. -<p><br>This is useful if you want your Samba server to appear in a remote +<p>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. -<p><br>For example: -<p><br><code> remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</code> -<p><br>the above line would cause nmbd to announce itself to the two given IP +<p>For example: +<p><code> remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</code> +<p>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 -<a href="../yodldocs/smb.conf.5.html#workgroup"><strong>"workgroup"</strong></a> parameter is used instead. -<p><br>The IP addresses you choose would normally be the broadcast addresses +<a href="smb.conf.5.html#workgroup"><strong>"workgroup"</strong></a> parameter is used instead. +<p>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. -<p><br>See the documentation file BROWSING.txt in the docs/ directory. -<p><br><strong>Default:</strong> +<p>See the documentation file BROWSING.txt in the docs/ directory. +<p><strong>Default:</strong> <code> remote announce = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF</code> -<p><br><a name="remotebrowsesync"></a> -<li><strong><strong>remote browse sync (G)</strong></strong> -<p><br>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> to +<p><a name="remotebrowsesync"></a> +<p></p><dt><strong><strong>remote browse sync (G)</strong></strong><dd> +<p>This option allows you to setup <a href="nmbd.8.html"><strong>nmbd</strong></a> 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. -<p><br>This is useful if you want your Samba server and all local clients to +<p>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. -<p><br>For example: -<p><br><code> remote browse sync = 192.168.2.255 192.168.4.255</code> -<p><br>the above line would cause <a href="nmbd.8.html"><strong>nmbd</strong></a> to request the +<p>For example: +<p><code> remote browse sync = 192.168.2.255 192.168.4.255</code> +<p>the above line would cause <a href="nmbd.8.html"><strong>nmbd</strong></a> to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server. -<p><br>The IP addresses you choose would normally be the broadcast addresses +<p>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 it's segment. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> remote browse sync = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> remote browse sync = 192.168.2.255 192.168.4.255</code> -<p><br><a name="restrictanonymous"></a> -<li><strong><strong>restrict anonymous (G)</strong></strong> -<p><br>This is a boolean parameter. If it is true, then anonymous access +<p><a name="restrictanonymous"></a> +<p></p><dt><strong><strong>restrict anonymous (G)</strong></strong><dd> +<p>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 recommened for homogenous NT client environments. -<p><br>This parameter makes the use of macro expansions that rely +<p>This parameter makes the use of macro expansions that rely on the username (%U, %G, etc) consistant. NT 4.0 likes to use anonymous connections when refreshing the share list, and this is a way to work around that. -<p><br>When restrict anonymous is true, all anonymous connections are denied +<p>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 it's machine account after someone else has logged on the client interactively. The @@ -3729,42 +3729,42 @@ 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". -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> restrict anonymous = false</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> restrict anonymous = true</code> -<p><br><a name="revalidate"></a> -<li><strong><strong>revalidate (S)</strong></strong> -<p><br>Note that this option only works with -<a href="../yodldocs/smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> and will be ignored if +<p><a name="revalidate"></a> +<p></p><dt><strong><strong>revalidate (S)</strong></strong><dd> +<p>Note that this option only works with +<a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> and will be ignored if this is not the case. -<p><br>This option controls whether Samba will allow a previously validated +<p>This option controls whether Samba will allow a previously validated username/password pair to be used to attach to a share. Thus if you connect to <code>\\server\share1</code> then to <code>\\server\share2</code> it won't automatically allow the client to request connection to the second share as the same username as the first without a password. -<p><br>If <strong>"revalidate"</strong> is <code>"True"</code> then the client will be denied +<p>If <strong>"revalidate"</strong> is <code>"True"</code> then the client will be denied automatic access as the same username. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> revalidate = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> revalidate = True</code> -<p><br><a name="root"></a> -<li><strong><strong>root (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>. -<p><br><a name="rootdir"></a> -<li><strong><strong>root dir (G)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>. -<p><br><a name="rootdirectory"></a> -<li><strong><strong>root directory (G)</strong></strong> -<p><br>The server will <code>"chroot()"</code> (i.e. Change it's root directory) to +<p><a name="root"></a> +<p></p><dt><strong><strong>root (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>. +<p><a name="rootdir"></a> +<p></p><dt><strong><strong>root dir (G)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>. +<p><a name="rootdirectory"></a> +<p></p><dt><strong><strong>root directory (G)</strong></strong><dd> +<p>The server will <code>"chroot()"</code> (i.e. Change it's root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use <code>".."</code> in file names to access other directories (depending on the -setting of the <a href="../yodldocs/smb.conf.5.html#widelinks"><strong>"wide links"</strong></a> parameter). -<p><br>Adding a <strong>"root directory"</strong> entry other than <code>"/"</code> adds an extra +setting of the <a href="smb.conf.5.html#widelinks"><strong>"wide links"</strong></a> parameter). +<p>Adding a <strong>"root directory"</strong> entry other than <code>"/"</code> 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 <strong>"root directory"</strong> option, <em>*including*</em> some files needed for complete @@ -3774,71 +3774,71 @@ directory"</strong> 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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> root directory = /</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> root directory = /homes/smb</code> -<p><br><a name="rootpostexec"></a> -<li><strong><strong>root postexec (S)</strong></strong> -<p><br>This is the same as the <a href="../yodldocs/smb.conf.5.html#postexec"><strong>"postexec"</strong></a> parameter +<p><a name="rootpostexec"></a> +<p></p><dt><strong><strong>root postexec (S)</strong></strong><dd> +<p>This is the same as the <a href="smb.conf.5.html#postexec"><strong>"postexec"</strong></a> parameter except that the command is run as root. This is useful for unmounting filesystems (such as cdroms) after a connection is closed. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#postexec"><strong>"postexec"</strong></a>. -<p><br><a name="rootpreexec"></a> -<li><strong><strong>root preexec (S)</strong></strong> -<p><br>This is the same as the <a href="../yodldocs/smb.conf.5.html#preexec"><strong>"preexec"</strong></a> parameter except +<p>See also <a href="smb.conf.5.html#postexec"><strong>"postexec"</strong></a>. +<p><a name="rootpreexec"></a> +<p></p><dt><strong><strong>root preexec (S)</strong></strong><dd> +<p>This is the same as the <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> parameter except that the command is run as root. This is useful for mounting filesystems (such as cdroms) before a connection is finalized. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#preexec"><strong>"preexec"</strong></a> -and <a href="../yodldocs/smb.conf.5.html#rootpreexecclose"><strong>"root preexec close"</strong></a>. -<p><br><a name="rootpreexecclose"></a> -<li><strong><strong>root preexec close (S)</strong></strong> -<p><br>This is the same as the <a href="../yodldocs/smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a> parameter +<p>See also <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> +and <a href="smb.conf.5.html#rootpreexecclose"><strong>"root preexec close"</strong></a>. +<p><a name="rootpreexecclose"></a> +<p></p><dt><strong><strong>root preexec close (S)</strong></strong><dd> +<p>This is the same as the <a href="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a> parameter except that the command is run as root. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#preexec"><strong>"preexec"</strong></a>, <a href="../yodldocs/smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a>. -<p><br><a name="security"></a> -<li><strong><strong>security (G)</strong></strong> -<p><br>This option affects how clients respond to Samba and is one of the most +<p>See also <a href="smb.conf.5.html#preexec"><strong>"preexec"</strong></a>, <a href="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a>. +<p><a name="security"></a> +<p></p><dt><strong><strong>security (G)</strong></strong><dd> +<p>This option affects how clients respond to Samba and is one of the most important settings in the <strong>smb.conf</strong> file. -<p><br>The option sets the <code>"security mode bit"</code> in replies to protocol +<p>The option sets the <code>"security mode bit"</code> in replies to protocol negotiations with <a href="smbd.8.html"><strong>smbd</strong></a> 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. -<p><br>The default is <a href="../yodldocs/smb.conf.5.html#securityequaluser">"security=user"</a>, as this is +<p>The default is <a href="smb.conf.5.html#securityequaluser">"security=user"</a>, as this is the most common setting needed when talking to Windows 98 and Windows NT. -<p><br>The alternatives are <a href="../yodldocs/smb.conf.5.html#securityequalshare"><strong>"security = share"</strong></a>, -<a href="../yodldocs/smb.conf.5.html#securityequalserver"><strong>"security = server"</strong></a> or -<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>. -<p><br><em>*****NOTE THAT THIS DEFAULT IS DIFFERENT IN SAMBA2.0 THAN FOR +<p>The alternatives are <a href="smb.conf.5.html#securityequalshare"><strong>"security = share"</strong></a>, +<a href="smb.conf.5.html#securityequalserver"><strong>"security = server"</strong></a> or +<a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>. +<p><em>*****NOTE THAT THIS DEFAULT IS DIFFERENT IN SAMBA2.0 THAN FOR PREVIOUS VERSIONS OF SAMBA *******</em>. -<p><br>In previous versions of Samba the default was -<a href="../yodldocs/smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> mainly because that was +<p>In previous versions of Samba the default was +<a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> mainly because that was the only option at one stage. -<p><br>There is a bug in WfWg that has relevance to this setting. When in +<p>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. -<p><br>If your PCs use usernames that are the same as their usernames on the +<p>If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use <strong>"security = user"</strong>. If you mostly use usernames that don't exist on the UNIX box then use <strong>"security = share"</strong>. -<p><br>You should also use <a href="../yodldocs/smb.conf.5.html#securityequalshare"><strong>security=share</strong></a> if +<p>You should also use <a href="smb.conf.5.html#securityequalshare"><strong>security=share</strong></a> 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 -<a href="../yodldocs/smb.conf.5.html#securityequaluser"><strong>security=user</strong></a>, see the <a href="../yodldocs/smb.conf.5.html#maptoguest"><strong>"map to +<a href="smb.conf.5.html#securityequaluser"><strong>security=user</strong></a>, see the <a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a>parameter for details. -<p><br>It is possible to use <a href="smbd.8.html"><strong>smbd</strong></a> in a <em>"hybrid +<p>It is possible to use <a href="smbd.8.html"><strong>smbd</strong></a> in a <em>"hybrid mode"</em> where it is offers both user and share level security under -different <a href="../yodldocs/smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a>. See the -<a href="../yodldocs/smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a> and the -<a href="../yodldocs/smb.conf.5.html#include"><strong>include</strong></a> parameters for more information. -<p><br>The different settings will now be explained. -<p><br><ul> -<p><br><a name="securityequalshare"></a> -<li><strong><strong>"security=share"</strong></strong> When clients connect to a share level +different <a href="smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a>. See the +<a href="smb.conf.5.html#netbiosaliases"><strong>NetBIOS aliases</strong></a> and the +<a href="smb.conf.5.html#include"><strong>include</strong></a> parameters for more information. +<p>The different settings will now be explained. +<p><dl> +<p><a name="securityequalshare"></a> +<p></p><dt><strong><strong>"security=share"</strong></strong><dd> When clients connect to a share level security server then 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 @@ -3846,193 +3846,193 @@ will send a logon request with a username but no password when talking to a <strong>security=share</strong> server). Instead, the clients send authentication information (passwords) on a per-share basis, at the time they attempt to connect to that share. -<p><br>Note that <a href="smbd.8.html"><strong>smbd</strong></a> <em>*ALWAYS*</em> uses a valid UNIX +<p>Note that <a href="smbd.8.html"><strong>smbd</strong></a> <em>*ALWAYS*</em> uses a valid UNIX user to act on behalf of the client, even in <strong>"security=share"</strong> level security. -<p><br>As clients are not required to send a username to the server +<p>As clients are not required to send a username to the server in share level security, <a href="smbd.8.html"><strong>smbd</strong></a> uses several techniques to determine the correct UNIX user to use on behalf of the client. -<p><br>A list of possible UNIX usernames to match with the given +<p>A list of possible UNIX usernames to match with the given client password is constructed using the following methods : -<p><br><ul> -<p><br><li > If the <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, then -all the other stages are missed and only the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest +<p><dl> +<p><li > If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, then +all the other stages are missed and only the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a> username is checked. -<p><br><li > Is a username is sent with the share connection request, then -this username (after mapping - see <a href="../yodldocs/smb.conf.5.html#usernamemap"><strong>"username +<p><li > Is a username is sent with the share connection request, then +this username (after mapping - see <a href="smb.conf.5.html#usernamemap"><strong>"username map"</strong></a>), is added as a potential username. -<p><br><li > If the client did a previous <em>"logon"</em> request (the +<p><li > If the client did a previous <em>"logon"</em> request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username. -<p><br><li > The name of the service the client requested is added +<p><li > The name of the service the client requested is added as a potential username. -<p><br><li > The NetBIOS name of the client is added to the list as a +<p><li > The NetBIOS name of the client is added to the list as a potential username. -<p><br><li > Any users on the <a href="../yodldocs/smb.conf.5.html#user"><strong>"user"</strong></a> list are added +<p><li > Any users on the <a href="smb.conf.5.html#user"><strong>"user"</strong></a> list are added as potential usernames. -<p><br></ul> -<p><br>If the <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is not set, then +<p></dl> +<p>If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> 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. -<p><br>If the <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, or no +<p>If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, or no username can be determined then if the share is marked as available to -the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>, then this guest user will +the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>, then this guest user will be used, otherwise access is denied. -<p><br>Note that it can be <em>*very*</em> confusing in share-level security as to +<p>Note that it can be <em>*very*</em> confusing in share-level security as to which UNIX username will eventually be used in granting access. -<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD +<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD VALIDATION"</strong></a>. -<p><br><a name="securityequaluser"></a> -<li><strong><strong>"security=user"</strong></strong> -<p><br>This is the default security setting in Samba2.0. With user-level +<p><a name="securityequaluser"></a> +<p></p><dt><strong><strong>"security=user"</strong></strong><dd> +<p>This is the default security setting in Samba2.0. With user-level security a client must first <code>"log-on"</code> with a valid username and -password (which can be mapped using the <a href="../yodldocs/smb.conf.5.html#usernamemap"><strong>"username +password (which can be mapped using the <a href="smb.conf.5.html#usernamemap"><strong>"username map"</strong></a> parameter). Encrypted passwords (see the -<a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter) can also +<a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter) can also be used in this security mode. Parameters such as -<a href="../yodldocs/smb.conf.5.html#user"><strong>"user"</strong></a> and <a href="../yodldocs/smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>, if set +<a href="smb.conf.5.html#user"><strong>"user"</strong></a> and <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>, 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. -<p><br><em>Note</em> that the name of the resource being requested is +<p><em>Note</em> that the name of the resource being requested is <em>*not*</em> 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 <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the -<a href="../yodldocs/smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on +users into the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the +<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on doing this. -<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD +<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD VALIDATION"</strong></a>. -<p><br><a name="securityequalserver"></a> -<li><strong><strong>"security=server"</strong></strong> -<p><br>In this mode Samba will try to validate the username/password by +<p><a name="securityequalserver"></a> +<p></p><dt><strong><strong>"security=server"</strong></strong><dd> +<p>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 <strong>"security = user"</strong>, 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. -<p><br><em>Note</em> that from the clients point of view <strong>"security=server"</strong> is -the same as <a href="../yodldocs/smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only +<p><em>Note</em> that from the clients point of view <strong>"security=server"</strong> is +the same as <a href="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only affects how the server deals with the authentication, it does not in any way affect what the client sees. -<p><br><em>Note</em> that the name of the resource being requested is +<p><em>Note</em> that the name of the resource being requested is <em>*not*</em> sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in server level security without allowing the server to automatically map unknown -users into the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the -<a href="../yodldocs/smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on +users into the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the +<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on doing this. -<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD +<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD VALIDATION"</strong></a>. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter. -and the <a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter. -<p><br><a name="securityequaldomain"></a> -<li><strong><strong>"security=domain"</strong></strong> -<p><br>This mode will only work correctly if +<p>See also the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter. +and the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter. +<p><a name="securityequaldomain"></a> +<p></p><dt><strong><strong>"security=domain"</strong></strong><dd> +<p>This mode will only work correctly if <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a> has been used to add this machine -into a Windows NT Domain. It expects the <a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypted +into a Windows NT Domain. It expects the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter to be set to <code>"true"</code>. 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. -<p><br><em>Note</em> that a valid UNIX user must still exist as well as the +<p><em>Note</em> 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. -<p><br><em>Note</em> that from the clients point of view <strong>"security=domain"</strong> is -the same as <a href="../yodldocs/smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only +<p><em>Note</em> that from the clients point of view <strong>"security=domain"</strong> is +the same as <a href="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only affects how the server deals with the authentication, it does not in any way affect what the client sees. -<p><br><em>Note</em> that the name of the resource being requested is +<p><em>Note</em> that the name of the resource being requested is <em>*not*</em> sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in domain level security without allowing the server to automatically map unknown -users into the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the -<a href="../yodldocs/smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on +users into the <a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. See the +<a href="smb.conf.5.html#maptoguest"><strong>"map to guest"</strong></a> parameter for details on doing this. -<p><br><em>BUG:</em> There is currently a bug in the implementation of +<p><em>BUG:</em> There is currently a bug in the implementation of <strong>"security=domain</strong> 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. -<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD +<p>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD VALIDATION"</strong></a>. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter. -and the <a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter. -<p><br></ul> -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> parameter. +and the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter. +<p></dl> +<p><strong>Default:</strong> <code> security = USER</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> security = DOMAIN</code> -<p><br><a name="securitymask"></a> -<li><strong><strong>security mask (S)</strong></strong> -<p><br>This parameter controls what UNIX permission bits can be modified +<p><a name="securitymask"></a> +<p></p><dt><strong><strong>security mask (S)</strong></strong><dd> +<p>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box. -<p><br>This parameter is applied as a mask (AND'ed with) to the changed +<p>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. -<p><br>If not set explicitly this parameter is set to the same value as the -<a href="../yodldocs/smb.conf.5.html#createmask"><strong>create mask</strong></a> parameter. To allow a user to +<p>If not set explicitly this parameter is set to the same value as the +<a href="smb.conf.5.html#createmask"><strong>create mask</strong></a> parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter to 0777. -<p><br><em>Note</em> that users who can access the Samba server through other +<p><em>Note</em> 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 set it to 0777. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security -mode</strong></a>, <a href="../yodldocs/smb.conf.5.html#directorysecuritymask"><strong>directory security -mask</strong></a>, <a href="../yodldocs/smb.conf.5.html#forcesecuritymode"><strong>force security +<p>See also the <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security +mode</strong></a>, <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security +mask</strong></a>, <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a> parameters. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> security mask = <same as create mask></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> security mask = 0777</code> -<p><br><a name="serverstring"></a> -<li><strong><strong>server string (G)</strong></strong> -<p><br>This controls what string will show up in the printer comment box in +<p><a name="serverstring"></a> +<p></p><dt><strong><strong>server string (G)</strong></strong><dd> +<p>This controls what string will show up in the printer comment box in print manager and next to the IPC connection in <code>"net view"</code>. It can be any string that you wish to show to your users. -<p><br>It also sets what will appear in browse lists next to the machine +<p>It also sets what will appear in browse lists next to the machine name. -<p><br>A <code>"%v"</code> will be replaced with the Samba version number. -<p><br>A <code>"%h"</code> will be replaced with the hostname. -<p><br><strong>Default:</strong> +<p>A <code>"%v"</code> will be replaced with the Samba version number. +<p>A <code>"%h"</code> will be replaced with the hostname. +<p><strong>Default:</strong> <code> server string = Samba %v</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> server string = University of GNUs Samba Server</code> -<p><br><a name="setdirectory"></a> -<li><strong><strong>set directory (S)</strong></strong> -<p><br>If <code>"set directory = no"</code>, then users of the service may not use the +<p><a name="setdirectory"></a> +<p></p><dt><strong><strong>set directory (S)</strong></strong><dd> +<p>If <code>"set directory = no"</code>, then users of the service may not use the setdir command to change directory. -<p><br>The setdir command is only implemented in the Digital Pathworks +<p>The setdir command is only implemented in the Digital Pathworks client. See the Pathworks documentation for details. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> set directory = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> set directory = yes</code> -<p><br><a name="sharemodes"></a> -<li><strong><strong>share modes (S)</strong></strong> -<p><br>This enables or disables the honoring of the <code>"share modes"</code> during a +<p><a name="sharemodes"></a> +<p></p><dt><strong><strong>share modes (S)</strong></strong><dd> +<p>This enables or disables the honoring of the <code>"share modes"</code> during a file open. These modes are used by clients to gain exclusive read or write access to a file. -<p><br>These open modes are not directly supported by UNIX, so they are +<p>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). -<p><br>The share modes that are enabled by this option are DENY_DOS, +<p>The share modes that are enabled by this option are DENY_DOS, DENY_ALL, DENY_READ, DENY_WRITE, DENY_NONE and DENY_FCB. -<p><br>This option gives full share compatibility and enabled by default. -<p><br>You should <em>*NEVER*</em> turn this parameter off as many Windows +<p>This option gives full share compatibility and enabled by default. +<p>You should <em>*NEVER*</em> turn this parameter off as many Windows applications will break if you do so. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> share modes = yes</code> -<p><br><a name="sharedmemsize"></a> -<li><strong><strong>shared mem size (G)</strong></strong> -<p><br>It specifies the size of the shared memory (in bytes) to use between +<p><a name="sharedmemsize"></a> +<p></p><dt><strong><strong>shared mem size (G)</strong></strong><dd> +<p>It specifies the size of the shared memory (in bytes) to use between <a href="smbd.8.html"><strong>smbd</strong></a> processes. This parameter defaults to one megabyte of shared memory. It is possible that if you have a large server with many files open simultaneously that you may need to @@ -4040,160 +4040,160 @@ increase this parameter. Signs that this parameter is set too low are users reporting strange problems trying to save files (locking errors) and error messages in the smbd log looking like <code>"ERROR smb_shm_alloc : alloc of XX bytes failed"</code>. -<p><br>If your OS refuses the size that Samba asks for then Samba will try a +<p>If your OS refuses the size that Samba asks for then Samba will try a smaller size, reducing by a factor of 0.8 until the OS accepts it. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> shared mem size = 1048576</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> shared mem size = 5242880 ; Set to 5mb for a large number of files.</code> -<p><br><a name="shortpreservecase"></a> -<li><strong><strong>short preserve case (S)</strong></strong> -<p><br>This boolean parameter controls if new files which conform to 8.3 +<p><a name="shortpreservecase"></a> +<p></p><dt><strong><strong>short preserve case (S)</strong></strong><dd> +<p>This boolean parameter controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the <code>"default"</code> case. This -option can be use with <a href="../yodldocs/smb.conf.5.html#preservecaseoption"><strong>"preserve case +option can be use with <a href="smb.conf.5.html#preservecaseoption"><strong>"preserve case =yes"</strong></a> to permit long filenames to retain their case, while short names are lowered. Default <em>Yes</em>. -<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>. -<p><br><strong>Default:</strong> +<p>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>. +<p><strong>Default:</strong> <code> short preserve case = yes</code> -<p><br><a name="smbpasswdfile"></a> -<li><strong><strong>smb passwd file (G)</strong></strong> -<p><br>This option sets the path to the encrypted smbpasswd file. By default +<p><a name="smbpasswdfile"></a> +<p></p><dt><strong><strong>smb passwd file (G)</strong></strong><dd> +<p>This option sets the path to the encrypted smbpasswd file. By default the path to the smbpasswd file is compiled into Samba. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> smb passwd file= <compiled default></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> smb passwd file = /usr/samba/private/smbpasswd</code> -<p><br><a name="smbrun"></a> -<li><strong><strong>smbrun (G)</strong></strong> -<p><br>This sets the full path to the <strong>smbrun</strong> binary. This defaults to the +<p><a name="smbrun"></a> +<p></p><dt><strong><strong>smbrun (G)</strong></strong><dd> +<p>This sets the full path to the <strong>smbrun</strong> binary. This defaults to the value in the Makefile. -<p><br>You must get this path right for many services to work correctly. -<p><br>You should not need to change this parameter so long as Samba +<p>You must get this path right for many services to work correctly. +<p>You should not need to change this parameter so long as Samba is installed correctly. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> smbrun=<compiled default></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> smbrun = /usr/local/samba/bin/smbrun</code> -<p><br><a name="socketaddress"></a> -<li><strong><strong>socket address (G)</strong></strong> -<p><br>This option allows you to control what address Samba will listen for +<p><a name="socketaddress"></a> +<p></p><dt><strong><strong>socket address (G)</strong></strong><dd> +<p>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. -<p><br>By default samba will accept connections on any address. -<p><br><strong>Example:</strong> +<p>By default samba will accept connections on any address. +<p><strong>Example:</strong> <code> socket address = 192.168.2.20</code> -<p><br><a name="socketoptions"></a> -<li><strong><strong>socket options (G)</strong></strong> -<p><br>This option allows you to set socket options to be used when talking +<p><a name="socketoptions"></a> +<p></p><dt><strong><strong>socket options (G)</strong></strong><dd> +<p>This option allows you to set socket options to be used when talking with the client. -<p><br>Socket options are controls on the networking layer of the operating +<p>Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned. -<p><br>This option will typically be used to tune your Samba server for +<p>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 <strong>"man setsockopt"</strong> will help). -<p><br>You may find that on some systems Samba will say "Unknown socket +<p>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 <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. -<p><br>Any of the supported socket options may be combined in any way you +<p>Any of the supported socket options may be combined in any way you like, as long as your OS allows it. -<p><br>This is the list of socket options currently settable using this +<p>This is the list of socket options currently settable using this option: -<p><br><ul> -<p><br><li > SO_KEEPALIVE -<p><br><li > SO_REUSEADDR -<p><br><li > SO_BROADCAST -<p><br><li > TCP_NODELAY -<p><br><li > IPTOS_LOWDELAY -<p><br><li > IPTOS_THROUGHPUT -<p><br><li > SO_SNDBUF * -<p><br><li > SO_RCVBUF * -<p><br><li > SO_SNDLOWAT * -<p><br><li > SO_RCVLOWAT * -<p><br></ul> -<p><br>Those marked with a <code>*</code> take an integer argument. The others can +<p><dl> +<p><li > SO_KEEPALIVE +<p><li > SO_REUSEADDR +<p><li > SO_BROADCAST +<p><li > TCP_NODELAY +<p><li > IPTOS_LOWDELAY +<p><li > IPTOS_THROUGHPUT +<p><li > SO_SNDBUF * +<p><li > SO_RCVBUF * +<p><li > SO_SNDLOWAT * +<p><li > SO_RCVLOWAT * +<p></dl> +<p>Those marked with a <code>*</code> 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. -<p><br>To specify an argument use the syntax SOME_OPTION=VALUE for example +<p>To specify an argument use the syntax SOME_OPTION=VALUE for example <code>SO_SNDBUF=8192</code>. Note that you must not have any spaces before or after the = sign. -<p><br>If you are on a local network then a sensible option might be -<p><br><code>socket options = IPTOS_LOWDELAY</code> -<p><br>If you have a local network then you could try: -<p><br><code>socket options = IPTOS_LOWDELAY TCP_NODELAY</code> -<p><br>If you are on a wide area network then perhaps try setting +<p>If you are on a local network then a sensible option might be +<p><code>socket options = IPTOS_LOWDELAY</code> +<p>If you have a local network then you could try: +<p><code>socket options = IPTOS_LOWDELAY TCP_NODELAY</code> +<p>If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT. -<p><br>Note that several of the options may cause your Samba server to fail +<p>Note that several of the options may cause your Samba server to fail completely. Use these options with caution! -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> socket options = TCP_NODELAY</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> socket options = IPTOS_LOWDELAY</code> -<p><br><a name="sourceenvironment"></a> -<li><strong><strong>source environment (G)</strong></strong> -<p><br>This parameter causes Samba to set environment variables as per the +<p><a name="sourceenvironment"></a> +<p></p><dt><strong><strong>source environment (G)</strong></strong><dd> +<p>This parameter causes Samba to set environment variables as per the content of the file named. -<p><br>The file <strong>must</strong> be owned by root and not world writable in order +<p>The file <strong>must</strong> be owned by root and not world writable in order to be read (this is a security check). -<p><br>If the value of this parameter starts with a "|" character then Samba will +<p>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 oput of the pipe. This command must not be world writable and must reside in a directory that is not world writable. -<p><br>The contents of the file or the output of the pipe should be formatted +<p>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 : -<p><br>Example environment entry: +<p>Example environment entry: <code> SAMBA_NETBIOS_NAME=myhostname </code> -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code>No default value</code> -<p><br><strong>Examples:</strong> -<p><br><code> source environment = |/etc/smb.conf.sh</code> -<p><br><code> source environment = /usr/local/smb_env_vars</code> -<p><br><a name="ssl"></a> -<li><strong><strong>ssl (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><strong>Examples:</strong> +<p><code> source environment = |/etc/smb.conf.sh</code> +<p><code> source environment = /usr/local/smb_env_vars</code> +<p><a name="ssl"></a> +<p></p><dt><strong><strong>ssl (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This variable enables or disables the entire SSL mode. If it is set to +<p>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 <a href="../yodldocs/smb.conf.5.html#sslhosts"><strong>"ssl -hosts"</strong></a> and <a href="../yodldocs/smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a> +set to "yes", it depends on the variables <a href="smb.conf.5.html#sslhosts"><strong>"ssl +hosts"</strong></a> and <a href="smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a> whether an SSL connection will be required. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl=no</code> <strong>Example:</strong> <code> ssl=yes</code> -<p><br><a name="sslCAcertDir"></a> -<li><strong><strong>ssl CA certDir (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslCAcertDir"></a> +<p></p><dt><strong><strong>ssl CA certDir (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This variable defines where to look up the Certification +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl CA certDir = /usr/local/ssl/certs</code> -<p><br><a name="sslCAcertFile"></a> -<li><strong><strong>ssl CA certFile (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslCAcertFile"></a> +<p></p><dt><strong><strong>ssl CA certFile (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This variable is a second way to define the trusted CAs. The +<p>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 @@ -4201,93 +4201,93 @@ 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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl CA certFile = /usr/local/ssl/certs/trustedCAs.pem</code> -<p><br><a name="sslciphers"></a> -<li><strong><strong>ssl ciphers (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslciphers"></a> +<p></p><dt><strong><strong>ssl ciphers (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This variable defines the ciphers that should be offered during SSL +<p>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. -<p><br><a name="sslclientcert"></a> -<li><strong><strong>ssl client cert (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslclientcert"></a> +<p></p><dt><strong><strong>ssl client cert (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>The certificate in this file is used by +<p>The certificate in this file is used by <a href="smbclient.1.html"><strong>smbclient</strong></a> if it exists. It's needed if the server requires a client certificate. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl client cert = /usr/local/ssl/certs/smbclient.pem</code> -<p><br><a name="sslclientkey"></a> -<li><strong><strong>ssl client key (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslclientkey"></a> +<p></p><dt><strong><strong>ssl client key (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This is the private key for <a href="smbclient.1.html"><strong>smbclient</strong></a>. It's +<p>This is the private key for <a href="smbclient.1.html"><strong>smbclient</strong></a>. It's only needed if the client should have a certificate. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl client key = /usr/local/ssl/private/smbclient.pem</code> -<p><br><a name="sslcompatibility"></a> -<li><strong><strong>ssl compatibility (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslcompatibility"></a> +<p></p><dt><strong><strong>ssl compatibility (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This variable defines whether SSLeay should be configured for bug +<p>This variable defines whether SSLeay should be configured for bug compatibility with other SSL implementations. This is probably not desirable because currently no clients with SSL implementations other than SSLeay exist. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl compatibility = no</code> -<p><br><a name="sslhosts"></a> -<li><strong><strong>ssl hosts (G)</strong></strong> -<p><br>See <a href="../yodldocs/smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a>. -<p><br><a name="sslhostsresign"></a> -<li><strong><strong>ssl hosts resign (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslhosts"></a> +<p></p><dt><strong><strong>ssl hosts (G)</strong></strong><dd> +<p>See <a href="smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a>. +<p><a name="sslhostsresign"></a> +<p></p><dt><strong><strong>ssl hosts resign (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>These two variables define whether samba will go into SSL mode or +<p>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 <a href="../yodldocs/smb.conf.5.html#sslhosts"><strong>"ssl hosts"</strong></a> variable lists +connections. If the <a href="smb.conf.5.html#sslhosts"><strong>"ssl hosts"</strong></a> variable lists hosts (by IP-address, IP-address range, net group or name), only these hosts will be forced into SSL mode. If the <strong>"ssl hosts resign"</strong> 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 -<a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="../yodldocs/smb.conf.5.html#hostsdeny"><strong>"hosts +<a href="smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="smb.conf.5.html#hostsdeny"><strong>"hosts deny"</strong></a> 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. See the <a href="../yodldocs/smb.conf.5.html#allowhosts"><strong>"allow hosts"</strong></a> parameter for +used or not. See the <a href="smb.conf.5.html#allowhosts"><strong>"allow hosts"</strong></a> parameter for details. The example below requires SSL connections from all hosts outside the local net (which is 192.168.*.*). -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl hosts = <empty string></code> <code> ssl hosts resign = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> ssl hosts resign = 192.168.</code> -<p><br><a name="sslrequireclientcert"></a> -<li><strong><strong>ssl require clientcert (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslrequireclientcert"></a> +<p></p><dt><strong><strong>ssl require clientcert (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>If this variable is set to <code>"yes"</code>, the server will not tolerate +<p>If this variable is set to <code>"yes"</code>, the server will not tolerate connections from clients that don't have a valid certificate. The -directory/file given in <a href="../yodldocs/smb.conf.5.html#sslCAcertDir"><strong>"ssl CA certDir"</strong></a> and -<a href="../yodldocs/smb.conf.5.html#sslCAcertFile"><strong>"ssl CA certFile"</strong></a> will be used to look up the +directory/file given in <a href="smb.conf.5.html#sslCAcertDir"><strong>"ssl CA certDir"</strong></a> and +<a href="smb.conf.5.html#sslCAcertFile"><strong>"ssl CA certFile"</strong></a> 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 <code>"no"</code>, clients don't need certificates. Contrary @@ -4296,100 +4296,100 @@ 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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl require clientcert = no</code> -<p><br><a name="sslrequireservercert"></a> -<li><strong><strong>ssl require servercert (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslrequireservercert"></a> +<p></p><dt><strong><strong>ssl require servercert (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>If this variable is set to <code>"yes"</code>, the +<p>If this variable is set to <code>"yes"</code>, the <a href="smbclient.1.html"><strong>smbclient</strong></a> will request a certificate from -the server. Same as <a href="../yodldocs/smb.conf.5.html#sslrequireclientcert"><strong>"ssl require +the server. Same as <a href="smb.conf.5.html#sslrequireclientcert"><strong>"ssl require clientcert"</strong></a> for the server. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl require servercert = no</code> -<p><br><a name="sslservercert"></a> -<li><strong><strong>ssl server cert (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslservercert"></a> +<p></p><dt><strong><strong>ssl server cert (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This is the file containing the server's certificate. The server _must_ +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl server cert = <empty string></code> -<p><br><a name="sslserverkey"></a> -<li><strong><strong>ssl server key (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslserverkey"></a> +<p></p><dt><strong><strong>ssl server key (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This file contains the private key of the server. If this variable is +<p>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 <em>*must*</em> have a private key and the certificate <em>*must*</em> match this private key. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl server key = <empty string></code> -<p><br><a name="sslversion"></a> -<li><strong><strong>ssl version (G)</strong></strong> -<p><br>This variable is part of SSL-enabled Samba. This is only available if +<p><a name="sslversion"></a> +<p></p><dt><strong><strong>ssl version (G)</strong></strong><dd> +<p>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 <code>"--with-ssl"</code> was given at configure time. -<p><br><em>Note</em> that for export control reasons this code is <em>**NOT**</em> +<p><em>Note</em> that for export control reasons this code is <em>**NOT**</em> enabled by default in any current binary version of Samba. -<p><br>This enumeration variable defines the versions of the SSL protocol +<p>This enumeration variable defines the versions of the SSL protocol that will be used. <code>"ssl2or3"</code> allows dynamic negotiation of SSL v2 or v3, <code>"ssl2"</code> results in SSL v2, <code>"ssl3"</code> results in SSL v3 and "tls1" results in TLS v1. TLS (Transport Layer Security) is the (proposed?) new standard for SSL. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> ssl version = "ssl2or3"</code> -<p><br><a name="statcache"></a> -<li><strong><strong>stat cache (G)</strong></strong> -<p><br>This parameter determines if <a href="smbd.8.html"><strong>smbd</strong></a> will use a +<p><a name="statcache"></a> +<p></p><dt><strong><strong>stat cache (G)</strong></strong><dd> +<p>This parameter determines if <a href="smbd.8.html"><strong>smbd</strong></a> will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> stat cache = yes</code> -<p><br><a name="statcachesize"></a> -<li><strong><strong>stat cache size (G)</strong></strong> -<p><br>This parameter determines the number of entries in the <a href="../yodldocs/smb.conf.5.html#statcache"><strong>stat +<p><a name="statcachesize"></a> +<p></p><dt><strong><strong>stat cache size (G)</strong></strong><dd> +<p>This parameter determines the number of entries in the <a href="smb.conf.5.html#statcache"><strong>stat cache</strong></a>. You should never need to change this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> stat cache size = 50</code> -<p><br><a name="status"></a> -<li><strong><strong>status (G)</strong></strong> -<p><br>This enables or disables logging of connections to a status file that +<p><a name="status"></a> +<p></p><dt><strong><strong>status (G)</strong></strong><dd> +<p>This enables or disables logging of connections to a status file that <a href="smbstatus.1.html"><strong>smbstatus</strong></a> can read. -<p><br>With this disabled <a href="smbstatus.1.html"><strong>smbstatus</strong></a> won't be able +<p>With this disabled <a href="smbstatus.1.html"><strong>smbstatus</strong></a> won't be able to tell you what connections are active. You should never need to change this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> status = yes -<p><br><a name="strictlocking"></a> -<li><strong><strong>strict locking (S)</strong></strong> -<p><br>This is a boolean that controls the handling of file locking in the +<p><a name="strictlocking"></a> +<p></p><dt><strong><strong>strict locking (S)</strong></strong><dd> +<p>This is a boolean that controls the handling of file locking in the server. When this is set to <code>"yes"</code> the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems. -<p><br>When strict locking is <code>"no"</code> the server does file lock checks only +<p>When strict locking is <code>"no"</code> the server does file lock checks only when the client explicitly asks for them. -<p><br>Well behaved clients always ask for lock checks when it is important, +<p>Well behaved clients always ask for lock checks when it is important, so in the vast majority of cases <strong>"strict locking = no"</strong> is preferable. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> strict locking = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> strict locking = yes</code> -<p><br><a name="strictsync"></a> -<li><strong><strong>strict sync (S)</strong></strong> -<p><br>Many Windows applications (including the Windows 98 explorer shell) +<p><a name="strictsync"></a> +<p></p><dt><strong><strong>strict sync (S)</strong></strong><dd> +<p>Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in kernel disk @@ -4401,120 +4401,120 @@ operating system itself that Samba is running on crashes, so there is little danger in this default setting. In addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#syncalways"><strong>"sync always"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#syncalways"><strong>"sync always"</strong></a> parameter. +<p><strong>Default:</strong> <code> strict sync = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> strict sync = yes</code> -<p><br><a name="stripdot"></a> -<li><strong><strong>strip dot (G)</strong></strong> -<p><br>This is a boolean that controls whether to strip trailing dots off +<p><a name="stripdot"></a> +<p></p><dt><strong><strong>strip dot (G)</strong></strong><dd> +<p>This is a boolean that controls whether to strip trailing dots off UNIX filenames. This helps with some CDROMs that have filenames ending in a single dot. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> strip dot = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> strip dot = yes</code> -<p><br><a name="syncalways"></a> -<li><strong><strong>sync always (S)</strong></strong> -<p><br>This is a boolean parameter that controls whether writes will always +<p><a name="syncalways"></a> +<p></p><dt><strong><strong>sync always (S)</strong></strong><dd> +<p>This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns. If this is false then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). If this is true then every write will be followed by a fsync() call to ensure the data is written to disk. -Note that the <a href="../yodldocs/smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter must be +Note that the <a href="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter must be set to <code>"yes"</code> in order for this parameter to have any affect. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter. +<p><strong>Default:</strong> <code> sync always = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> sync always = yes</code> -<p><br><a name="syslog"></a> -<li><strong><strong>syslog (G)</strong></strong> -<p><br>This parameter maps how Samba debug messages are logged onto the +<p><a name="syslog"></a> +<p></p><dt><strong><strong>syslog (G)</strong></strong><dd> +<p>This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug level zero maps onto syslog LOG_ERR, debug level one maps onto LOG_WARNING, debug level two maps onto LOG_NOTICE, debug level three maps onto LOG_INFO. All higher levels are mapped to LOG_DEBUG. -<p><br>This paramter sets the threshold for sending messages to syslog. +<p>This paramter sets the threshold for sending messages to syslog. Only messages with debug level less than this value will be sent to syslog. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> syslog = 1</code> -<p><br><a name="syslogonly"></a> -<li><strong><strong>syslog only (G)</strong></strong> -<p><br>If this parameter is set then Samba debug messages are logged into the +<p><a name="syslogonly"></a> +<p></p><dt><strong><strong>syslog only (G)</strong></strong><dd> +<p>If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> syslog only = no</code> -<p><br><a name="templatehomedir"></a> -<li><strong><strong>template homedir (G)</strong></strong> -<p><br>NOTE: this parameter is only available in Samba 3.0. -<p><br>When filling out the user information for a Windows NT user, the +<p><a name="templatehomedir"></a> +<p></p><dt><strong><strong>template homedir (G)</strong></strong><dd> +<p>NOTE: this parameter is only available in Samba 3.0. +<p>When filling out the user information for a Windows NT user, the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in the home directory for that user. If the string <code>%D</code> is present it is substituted with the user's Windows NT domain name. If the string <code>%U</code> is present it is substituted with the user's Windows NT user name. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> template homedir = /home/%D/%U</code> -<p><br><a name="templateshell"></a> -<li><strong><strong>template shell (G)</strong></strong> -<p><br>NOTE: this parameter is only available in Samba 3.0. -<p><br>When filling out the user information for a Windows NT user, the +<p><a name="templateshell"></a> +<p></p><dt><strong><strong>template shell (G)</strong></strong><dd> +<p>NOTE: this parameter is only available in Samba 3.0. +<p>When filling out the user information for a Windows NT user, the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in the login shell for that user. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> template shell = /bin/false</code> -<p><br><a name="timeoffset"></a> -<li><strong><strong>time offset (G)</strong></strong> -<p><br>This parameter is a setting in minutes to add to the normal GMT to +<p><a name="timeoffset"></a> +<p></p><dt><strong><strong>time offset (G)</strong></strong><dd> +<p>This parameter is a setting in minutes to add to the normal GMT to local time conversion. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> time offset = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> time offset = 60</code> -<p><br><a name="timeserver"></a> -<p><br><li><strong><strong>time server (G)</strong></strong> -<p><br>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> advertises +<p><a name="timeserver"></a> +<p><p></p><dt><strong><strong>time server (G)</strong></strong><dd> +<p>This parameter determines if <a href="nmbd.8.html"><strong>nmbd</strong></a> advertises itself as a time server to Windows clients. The default is False. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> time server = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> time server = True</code> -<p><br><a name="timestamplogs"></a> -<li><strong><strong>timestamp logs (G)</strong></strong> -<p><br>Synonym for <a href="debugtimestamp"><strong>"debug timestamp"</strong></a>. -<p><br><a name="unixpasswordsync"></a> -<li><strong><strong>unix password sync (G)</strong></strong> -<p><br>This boolean parameter controls whether Samba attempts to synchronize +<p><a name="timestamplogs"></a> +<p></p><dt><strong><strong>timestamp logs (G)</strong></strong><dd> +<p>Synonym for <a href="debugtimestamp"><strong>"debug timestamp"</strong></a>. +<p><a name="unixpasswordsync"></a> +<p></p><dt><strong><strong>unix password sync (G)</strong></strong><dd> +<p>This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. If this is set to true the -program specified in the <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> +program specified in the <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a> parameter is called <em>*AS ROOT*</em> - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password has change code has no access to the old password cleartext, only the new). By default this is set to <code>"false"</code>. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>, <a href="../yodldocs/smb.conf.5.html#passwdchat"><strong>"passwd +<p>See also <a href="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>, <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> unix password sync = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> unix password sync = True</code> -<p><br><a name="unixrealname"></a> -<li><strong><strong>unix realname (G)</strong></strong> -<p><br>This boolean parameter when set causes samba to supply the real name +<p><a name="unixrealname"></a> +<p></p><dt><strong><strong>unix realname (G)</strong></strong><dd> +<p>This boolean parameter when set causes samba to supply the real name field from the unix password file to the client. This is useful for setting up mail clients and WWW browsers on systems used by more than one person. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> unix realname = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> unix realname = yes</code> -<p><br><a name="updateencrypted"></a> -<li><strong><strong>update encrypted (G)</strong></strong> -<p><br>This boolean parameter allows a user logging on with a plaintext +<p><a name="updateencrypted"></a> +<p></p><dt><strong><strong>update encrypted (G)</strong></strong><dd> +<p>This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on. This option allows a site to migrate from plaintext password authentication (users @@ -4526,80 +4526,80 @@ change is made. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to <code>"off"</code>. -<p><br>In order for this parameter to work correctly the <a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypt +<p>In order for this parameter to work correctly the <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt passwords"</strong></a> parameter must be set to <code>"no"</code> when this parameter is set to <code>"yes"</code>. -<p><br>Note that even when this parameter is set a user authenticating to +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> update encrypted = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> update encrypted = yes</code> -<p><br><a name="userhosts"></a> -<li><strong><strong>use rhosts (G)</strong></strong> -<p><br>If this global parameter is a true, it specifies that the UNIX users +<p><a name="userhosts"></a> +<p></p><dt><strong><strong>use rhosts (G)</strong></strong><dd> +<p>If this global parameter is a true, it specifies that the UNIX users <code>".rhosts"</code> file in their home directory will be read to find the names of hosts and users who will be allowed access without specifying a password. -<p><br>NOTE: The use of <strong>use rhosts</strong> can be a major security hole. This is +<p>NOTE: The use of <strong>use rhosts</strong> 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 <strong>use rhosts</strong> option be only used if you really know what you are doing. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> use rhosts = no</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> use rhosts = yes</code> -<p><br><a name="user"></a> -<li><strong><strong>user (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#username"><strong>"username"</strong></a>. -<p><br><a name="users"></a> -<li><strong><strong>users (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#username"><strong>"username"</strong></a>. -<p><br><a name="username"></a> -<li><strong><strong>username (S)</strong></strong> -<p><br>Multiple users may be specified in a comma-delimited list, in which +<p><a name="user"></a> +<p></p><dt><strong><strong>user (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#username"><strong>"username"</strong></a>. +<p><a name="users"></a> +<p></p><dt><strong><strong>users (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#username"><strong>"username"</strong></a>. +<p><a name="username"></a> +<p></p><dt><strong><strong>username (S)</strong></strong><dd> +<p>Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right). -<p><br>The <strong>username=</strong> line is needed only when the PC is unable to supply +<p>The <strong>username=</strong> 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 <code>\\server\share%user</code> syntax instead. -<p><br>The <strong>username=</strong> line is not a great solution in many cases as it +<p>The <strong>username=</strong> 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. -<p><br>Samba relies on the underlying UNIX security. This parameter does not +<p>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. -<p><br>To restrict a service to a particular set of users you can use the -<a href="../yodldocs/smb.conf.5.html#validusers"><strong>"valid users="</strong></a> parameter. -<p><br>If any of the usernames begin with a <code>'@'</code> then the name will be +<p>To restrict a service to a particular set of users you can use the +<a href="smb.conf.5.html#validusers"><strong>"valid users="</strong></a> parameter. +<p>If any of the usernames begin with a <code>'@'</code> then the name will be looked up first in the yp 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. -<p><br>If any of the usernames begin with a <code>'+'</code> then the name will be +<p>If any of the usernames begin with a <code>'+'</code> 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. -<p><br>If any of the usernames begin with a <code>'&'</code> then the name will be +<p>If any of the usernames begin with a <code>'&'</code> then the name will be looked up only in the yp 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. -<p><br>Note that searching though a groups database can take quite some time, +<p>Note that searching though a groups database can take quite some time, and some clients may time out during the search. -<p><br>See the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD +<p>See the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD VALIDATION"</strong></a> for more information on how this parameter determines access to the services. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> The guest account if a guest service, else the name of the service.</code> -<p><br><strong>Examples:</strong> +<p><strong>Examples:</strong> <pre> username = fred @@ -4607,159 +4607,159 @@ information on how this parameter determines access to the services. </pre> -<p><br><a name="usernamelevel"></a> -<li><strong><strong>username level (G)</strong></strong> -<p><br>This option helps Samba to try and 'guess' at the real UNIX username, +<p><a name="usernamelevel"></a> +<p></p><dt><strong><strong>username level (G)</strong></strong><dd> +<p>This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine. -<p><br>If this parameter is set to non-zero the behavior changes. This +<p>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 whilst 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 <code>"AstrangeUser"</code>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> username level = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> username level = 5</code> -<p><br><a name="usernamemap"></a> -<li><strong><strong>username map (G)</strong></strong> -<p><br>This option allows you to specify a file containing a mapping of +<p><a name="usernamemap"></a> +<p></p><dt><strong><strong>username map (G)</strong></strong><dd> +<p>This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they can more easily share files. -<p><br>The map file is parsed line by line. Each line should contain a single +<p>The map file is parsed line by line. Each line should contain a single UNIX username on the left then a <code>'='</code> 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 <code>'*'</code> is a wildcard and matches any name. Each line of the map file may be up to 1023 characters long. -<p><br>The file is processed on each line by taking the supplied username and +<p>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 <code>'='</code> 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. -<p><br>If any line begins with a <code>'#'</code> or a <code>';'</code> then it is ignored -<p><br>If any line begins with an <code>'!'</code> then the processing will stop after +<p>If any line begins with a <code>'#'</code> or a <code>';'</code> then it is ignored +<p>If any line begins with an <code>'!'</code> 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 <code>'!'</code> is most useful when you have a wildcard mapping line later in the file. -<p><br>For example to map from the name <code>"admin"</code> or <code>"administrator"</code> to +<p>For example to map from the name <code>"admin"</code> or <code>"administrator"</code> to the UNIX name <code>"root"</code> you would use: -<p><br><code> root = admin administrator</code> -<p><br>Or to map anyone in the UNIX group <code>"system"</code> to the UNIX name +<p><code> root = admin administrator</code> +<p>Or to map anyone in the UNIX group <code>"system"</code> to the UNIX name <code>"sys"</code> you would use: -<p><br><code> sys = @system</code> -<p><br>You can have as many mappings as you like in a username map file. -<p><br>If your system supports the NIS NETGROUP option then the netgroup +<p><code> sys = @system</code> +<p>You can have as many mappings as you like in a username map file. +<p>If your system supports the NIS NETGROUP option then the netgroup database is checked before the <code>/etc/group</code> database for matching groups. -<p><br>You can map Windows usernames that have spaces in them by using double +<p>You can map Windows usernames that have spaces in them by using double quotes around the name. For example: -<p><br><code> tridge = "Andrew Tridgell"</code> -<p><br>would map the windows username <code>"Andrew Tridgell"</code> to the unix +<p><code> tridge = "Andrew Tridgell"</code> +<p>would map the windows username <code>"Andrew Tridgell"</code> to the unix username tridge. -<p><br>The following example would map mary and fred to the unix user sys, +<p>The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the <code>'!'</code> to tell Samba to stop processing if it gets a match on that line. -<p><br><pre> +<p><pre> !sys = mary fred guest = * </pre> -<p><br>Note that the remapping is applied to all occurrences of +<p>Note that the remapping is applied to all occurrences of usernames. Thus if you connect to <code>"\\server\fred"</code> and <code>"fred"</code> is remapped to <code>"mary"</code> then you will actually be connecting to <code>"\\server\mary"</code> and will need to supply a password suitable for <code>"mary"</code> not <code>"fred"</code>. The only exception to this is the username -passed to the <a href="../yodldocs/smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> (if you have +passed to the <a href="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> (if you have one). The password server will receive whatever username the client supplies without modification. -<p><br>Also note that no reverse mapping is done. The main effect this has is +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> no username map</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> username map = /usr/local/samba/lib/users.map</code> -<p><br><a name="utmp"></a> -<li><strong><strong>utmp (S)</strong></strong> -<p><br>This boolean parameter is only available if Samba has been configured and compiled +<p><a name="utmp"></a> +<p></p><dt><strong><strong>utmp (S)</strong></strong><dd> +<p>This boolean parameter is only available if Samba has been configured and compiled with the option <code>--with-utmp</code>. 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. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#utmpdirectory"><strong>"utmp directory"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#utmpdirectory"><strong>"utmp directory"</strong></a> parameter. +<p><strong>Default:</strong> <code>utmp = False</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code>utmp = True</code> -<p><br><a name="utmpdirectory"></a> -<li><strong><strong>utmp directory(G)</strong></strong> -<p><br>This parameter is only available if Samba has been configured and compiled +<p><a name="utmpdirectory"></a> +<p></p><dt><strong><strong>utmp directory(G)</strong></strong><dd> +<p>This parameter is only available if Samba has been configured and compiled with the option <code>--with-utmp</code>. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that -record user connections to a Samba server. See also the <a href="../yodldocs/smb.conf.5.html#utmp"><strong>"utmp"</strong></a> +record user connections to a Samba server. See also the <a href="smb.conf.5.html#utmp"><strong>"utmp"</strong></a> parameter. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually /var/run/utmp on Linux). -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code>no utmp directory</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code>utmp directory = /var/adm/</code> -<p><br><a name="winbindcachetime"></a> -<li><strong>winbind cache time</strong> -<p><br>NOTE: this parameter is only available in Samba 3.0. -<p><br>This parameter specifies the number of seconds the +<p><a name="winbindcachetime"></a> +<p></p><dt><strong>winbind cache time</strong><dd> +<p>NOTE: this parameter is only available in Samba 3.0. +<p>This parameter specifies the number of seconds the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon will cache user and group information before querying a Windows NT server again. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> winbind cache type = 15</code> -<p><br><a name="winbindgid"></a> -<li><strong>winbind gid</strong> -<p><br>NOTE: this parameter is only available in Samba 3.0. -<p><br>The winbind gid parameter specifies the range of group ids that are +<p><a name="winbindgid"></a> +<p></p><dt><strong>winbind gid</strong><dd> +<p>NOTE: this parameter is only available in Samba 3.0. +<p>The winbind gid parameter specifies the range of group ids that are allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon. This range of group ids should have no existing local or nis groups within it as strange conflicts can occur otherwise. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> winbind gid = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> winbind gid = 10000-20000</code> -<p><br><a name="winbinduid"></a> -<li><strong>winbind uid</strong> -<p><br>NOTE: this parameter is only available in Samba 3.0. -<p><br>The winbind uid parameter specifies the range of user ids that are +<p><a name="winbinduid"></a> +<p></p><dt><strong>winbind uid</strong><dd> +<p>NOTE: this parameter is only available in Samba 3.0. +<p>The winbind uid parameter specifies the range of user ids that are allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon. This range of ids should have no existing local or nis users within it as strange conflicts can occur otherwise. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> winbind uid = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> winbind uid = 10000-20000</code> -<p><br><a name="validchars"></a> -<li><strong><strong>valid chars (G)</strong></strong> -<p><br>The option allows you to specify additional characters that should be +<p><a name="validchars"></a> +<p></p><dt><strong><strong>valid chars (G)</strong></strong><dd> +<p>The option allows you to specify additional characters that should be considered valid by the server in filenames. This is particularly useful for national character sets, such as adding u-umlaut or a-ring. -<p><br>The option takes a list of characters in either integer or character +<p>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. -<p><br>If you have an editor capable of entering the characters into the +<p>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. -<p><br>For example to add the single character <code>'Z'</code> to the charset (which +<p>For example to add the single character <code>'Z'</code> to the charset (which is a pointless thing to do as it's already there) you could do one of the following -<p><br><pre> +<p><pre> valid chars = Z valid chars = z:Z @@ -4767,15 +4767,15 @@ the following </pre> -<p><br>The last two examples above actually add two characters, and alter the +<p>The last two examples above actually add two characters, and alter the uppercase and lowercase mappings appropriately. -<p><br>Note that you MUST specify this parameter after the <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client +<p>Note that you MUST specify this parameter after the <a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> parameter if you have both set. If -<a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> is set after the +<a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> is set after the <strong>"valid chars"</strong> parameter the <strong>"valid chars"</strong> settings will be overwritten. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> parameter. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> parameter. +<p><strong>Default:</strong> <pre> Samba defaults to using a reasonable set of valid characters @@ -4783,60 +4783,60 @@ overwritten. </pre> -<p><br><strong>Example</strong> +<p><strong>Example</strong> <code> valid chars = 0345:0305 0366:0326 0344:0304</code> -<p><br>The above example allows filenames to have the Swedish characters in +<p>The above example allows filenames to have the Swedish characters in them. -<p><br>NOTE: It is actually quite difficult to correctly produce a <strong>"valid +<p>NOTE: It is actually quite difficult to correctly produce a <strong>"valid chars"</strong> line for a particular system. To automate the process <a href="mailto:tino@augsburg.net"><em>tino@augsburg.net</em></a> has written a package called <strong>"validchars"</strong> which will automatically produce a complete <strong>"valid chars"</strong> line for a given client system. Look in the examples/validchars/ subdirectory of your Samba source code distribution for this package. -<p><br><a name="validusers"></a> -<li><strong><strong>valid users (S)</strong></strong> -<p><br>This is a list of users that should be allowed to login to this +<p><a name="validusers"></a> +<p></p><dt><strong><strong>valid users (S)</strong></strong><dd> +<p>This is a list of users that should be allowed to login to this service. Names starting with <code>'@'</code>, <code>'+'</code> and <code>'&'</code> are -interpreted using the same rules as described in the <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>"invalid +interpreted using the same rules as described in the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter. -<p><br>If this is empty (the default) then any user can login. If a username -is in both this list and the <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> +<p>If this is empty (the default) then any user can login. If a username +is in both this list and the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> list then access is denied for that user. -<p><br>The current servicename is substituted for -<a href="../yodldocs/smb.conf.5.html#percentS"><strong>"%S"</strong></a>. This is useful in the -<a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> section. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>. -<p><br><strong>Default:</strong> +<p>The current servicename is substituted for +<a href="smb.conf.5.html#percentS"><strong>"%S"</strong></a>. This is useful in the +<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> section. +<p>See also <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>. +<p><strong>Default:</strong> <code> No valid users list. (anyone can login)</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> valid users = greg, @pcusers</code> -<p><br><a name="vetofiles"></a> -<li><strong><strong>veto files(S)</strong></strong> -<p><br>This is a list of files and directories that are neither visible nor +<p><a name="vetofiles"></a> +<p></p><dt><strong><strong>veto files(S)</strong></strong><dd> +<p>This is a list of files and directories that are neither visible nor accessible. Each entry in the list must be separated by a <code>'/'</code>, which allows spaces to be included in the entry. <code>'*'</code> and <code>'?'</code> can be used to specify multiple files or directories as in DOS wildcards. -<p><br>Each entry must be a unix path, not a DOS path and must <em>*not*</em> include the +<p>Each entry must be a unix path, not a DOS path and must <em>*not*</em> include the unix directory separator <code>'/'</code>. -<p><br>Note that the <a href="../yodldocs/smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a> option is +<p>Note that the <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a> option is applicable in vetoing files. -<p><br>One feature of the veto files parameter that it is important to be +<p>One feature of the veto files parameter that it is important to be aware of, is that if a directory contains nothing but files that match the veto files parameter (which means that Windows/DOS clients cannot ever see them) is deleted, the veto files within that directory *are automatically deleted* along with it, if the user has UNIX permissions to do so. -<p><br>Setting this parameter will affect the performance of Samba, as it +<p>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. -<p><br>See also <a href="../yodldocs/smb.conf.5.html#hidefiles"><strong>"hide files"</strong></a> and <a href="../yodldocs/smb.conf.5.html#casesensitive"><strong>"case +<p>See also <a href="smb.conf.5.html#hidefiles"><strong>"hide files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> No files or directories are vetoed.</code> -<p><br><strong>Examples:</strong> -<p><br>Example 1. -<p><br><pre> +<p><strong>Examples:</strong> +<p>Example 1. +<p><pre> Veto any files containing the word Security, @@ -4847,8 +4847,8 @@ sensitive"</strong></a>. </pre> -<p><br>Example 2. -<p><br><pre> +<p>Example 2. +<p><pre> Veto the Apple specific files that a NetAtalk server creates. @@ -4857,170 +4857,170 @@ sensitive"</strong></a>. </pre> -<p><br><a name="vetooplockfiles"></a> -<li><strong><strong>veto oplock files (S)</strong></strong> -<p><br>This parameter is only valid when the <a href="../yodldocs/smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> +<p><a name="vetooplockfiles"></a> +<p></p><dt><strong><strong>veto oplock files (S)</strong></strong><dd> +<p>This parameter is only valid when the <a href="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> parameter is turned on for a share. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that match a wildcarded list, similar to the wildcarded list used in the -<a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>"veto files"</strong></a> parameter. -<p><br><strong>Default:</strong> +<a href="smb.conf.5.html#vetofiles"><strong>"veto files"</strong></a> parameter. +<p><strong>Default:</strong> <code> No files are vetoed for oplock grants.</code> -<p><br><strong>Examples:</strong> -<p><br>You might want to do this on files that you know will be heavily +<p><strong>Examples:</strong> +<p>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 <code>".SEM"</code>. To cause Samba not to grant oplocks on these -files you would use the line (either in the <a href="../yodldocs/smb.conf.5.html#global"><strong>[global]</strong></a> +files you would use the line (either in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section or in the section for the particular NetBench share : -<p><br><code> veto oplock files = /*.SEM/</code> -<p><br><a name="volume"></a> -<li><strong><strong>volume (S)</strong></strong> -<p><br>This allows you to override the volume label returned for a +<p><code> veto oplock files = /*.SEM/</code> +<p><a name="volume"></a> +<p></p><dt><strong><strong>volume (S)</strong></strong><dd> +<p>This allows you to override the volume label returned for a share. Useful for CDROMs with installation programs that insist on a particular volume label. -<p><br>The default is the name of the share. -<p><br><a name="widelinks"></a> -<li><strong><strong>wide links (S)</strong></strong> -<p><br>This parameter controls whether or not links in the UNIX file system +<p>The default is the name of the share. +<p><a name="widelinks"></a> +<p></p><dt><strong><strong>wide links (S)</strong></strong><dd> +<p>This parameter controls whether or not links in the UNIX file system may be followed by the server. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only to areas that are outside the directory tree being exported. -<p><br>Note that setting this parameter can have a negative effect on your +<p>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. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> wide links = yes</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> wide links = no</code> -<p><br><a name="winsproxy"></a> -<li><strong><strong>wins proxy (G)</strong></strong> -<p><br>This is a boolean that controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> will +<p><a name="winsproxy"></a> +<p></p><dt><strong><strong>wins proxy (G)</strong></strong><dd> +<p>This is a boolean that controls if <a href="nmbd.8.html"><strong>nmbd</strong></a> will respond to broadcast name queries on behalf of other hosts. You may need to set this to <code>"yes"</code> for some older clients. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> wins proxy = no</code> -<p><br><a name="winsserver"></a> -<li><strong><strong>wins server (G)</strong></strong> -<p><br>This specifies the IP address (or DNS name: IP address for preference) +<p><a name="winsserver"></a> +<p></p><dt><strong><strong>wins server (G)</strong></strong><dd> +<p>This specifies the IP address (or DNS name: IP address for preference) of the WINS server that <a href="nmbd.8.html"><strong>nmbd</strong></a> should register with. If you have a WINS server on your network then you should set this to the WINS server's IP. -<p><br>You should point this at your WINS server if you have a +<p>You should point this at your WINS server if you have a multi-subnetted network. -<p><br><em>NOTE</em>. You need to set up Samba to point to a WINS server if you +<p><em>NOTE</em>. 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. -<p><br>See the documentation file BROWSING.txt in the docs/ directory of your +<p>See the documentation file BROWSING.txt in the docs/ directory of your Samba source distribution. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> wins server = </code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> wins server = 192.9.200.1</code> -<p><br><a name="winshook"></a> -<li><strong><strong>wins hook (G)</strong></strong> -<p><br>When Samba is running as a WINS server this allows you to call an +<p><a name="winshook"></a> +<p></p><dt><strong><strong>wins hook (G)</strong></strong><dd> +<p>When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS. -<p><br>The wins hook parameter specifies the name of a script or executable +<p>The wins hook parameter specifies the name of a script or executable that will be called as follows: -<p><br>wins_hook operation name nametype ttl IP_list -<p><br>The first argument is the operation and is one of "add", "delete", +<p>wins_hook operation name nametype ttl IP_list +<p>The first argument is the operation and is one of "add", "delete", or "refresh". In most cases the operation can be ignored as the rest of the parameters provide sufficient information. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add. -<p><br>The second argument is the netbios name. If the name is not a legal +<p>The second argument is the netbios name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods. -<p><br>The third argument is the netbios name type as a 2 digit hexadecimal +<p>The third argument is the netbios name type as a 2 digit hexadecimal number. -<p><br>The fourth argument is the TTL (time to live) for the name in seconds. -<p><br>The fifth and subsequent arguments are the IP addresses currently +<p>The fourth argument is the TTL (time to live) for the name in seconds. +<p>The fifth and subsequent arguments are the IP addresses currently registered for that name. If this list is empty then the name should be deleted. -<p><br>An example script that calls the BIND dynamic DNS update program +<p>An example script that calls the BIND dynamic DNS update program "nsupdate" is provided in the examples directory of the Samba source code. -<p><br><a name="winssupport"></a> -<li><strong><strong>wins support (G)</strong></strong> -<p><br>This boolean controls if the <a href="nmbd.8.html"><strong>nmbd</strong></a> process in +<p><a name="winssupport"></a> +<p></p><dt><strong><strong>wins support (G)</strong></strong><dd> +<p>This boolean controls if the <a href="nmbd.8.html"><strong>nmbd</strong></a> process in Samba will act as a WINS server. You should not set this to true unless you have a multi-subnetted network and you wish a particular <a href="nmbd.8.html"><strong>nmbd</strong></a> to be your WINS server. Note that you should <em>*NEVER*</em> set this to true on more than one machine in your network. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> wins support = no</code> -<p><br><a name="workgroup"></a> -<li><strong><strong>workgroup (G)</strong></strong> -<p><br>This controls what workgroup your server will appear to be in when +<p><a name="workgroup"></a> +<p></p><dt><strong><strong>workgroup (G)</strong></strong><dd> +<p>This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain -name used with the <a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> +name used with the <a href="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> setting. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> set at compile time to WORKGROUP</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> workgroup = MYGROUP -<p><br><a name="writable"></a> -<li><strong><strong>writable (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a> for people who can't spell :-). -<p><br><a name="writelist"></a> -<li><strong><strong>write list (S)</strong></strong> -<p><br>This is a list of users that are given read-write access to a +<p><a name="writable"></a> +<p></p><dt><strong><strong>writable (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> for people who can't spell :-). +<p><a name="writelist"></a> +<p></p><dt><strong><strong>write list (S)</strong></strong><dd> +<p>This is a list of users that are given read-write access to a service. If the connecting user is in this list then they will be -given write access, no matter what the <a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a> +given write access, no matter what the <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> option is set to. The list can include group names using the @group syntax. -<p><br>Note that if a user is in both the read list and the write list then +<p>Note that if a user is in both the read list and the write list then they will be given write access. -<p><br>See also the <a href="../yodldocs/smb.conf.5.html#readlist"><strong>"read list"</strong></a> option. -<p><br><strong>Default:</strong> +<p>See also the <a href="smb.conf.5.html#readlist"><strong>"read list"</strong></a> option. +<p><strong>Default:</strong> <code> write list = <empty string></code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> write list = admin, root, @staff</code> -<p><br><a name="writecachesize"></a> -<li><strong><strong>write cache size (S)</strong></strong> -<p><br>This integer parameter (new with Samba 2.0.7) if set to non-zero causes Samba to create an in-memory +<p><a name="writecachesize"></a> +<p></p><dt><strong><strong>write cache size (S)</strong></strong><dd> +<p>This integer parameter (new with Samba 2.0.7) if set to non-zero causes Samba to create an in-memory cache for each oplocked file (it does <strong>not</strong> do this for non-oplocked files). All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible. The cache is flushed onto disk when a write comes in whose offset would not fit into the cache or when the file is closed by the client. Reads for the file are also served from this cache if the data is stored within it. -<p><br>This cache allows Samba to batch client writes into a more efficient write +<p>This cache allows Samba to batch client writes into a more efficient write size for RAID disks (ie. 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. -<p><br>The integer parameter specifies the size of this cache (per oplocked file) +<p>The integer parameter specifies the size of this cache (per oplocked file) in bytes. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> write cache size = 0</code> -<p><br><strong>Example:</strong> +<p><strong>Example:</strong> <code> write cache size = 262144</code> for a 256k cache size per file. -<p><br><a name="writeok"></a> -<li><strong><strong>write ok (S)</strong></strong> -<p><br>Synonym for <a href="../yodldocs/smb.conf.5.html#writeable"><strong>writeable</strong></a>. -<p><br><a name="writeraw"></a> -<li><strong><strong>write raw (G)</strong></strong> -<p><br>This parameter controls whether or not the server will support raw +<p><a name="writeok"></a> +<p></p><dt><strong><strong>write ok (S)</strong></strong><dd> +<p>Synonym for <a href="smb.conf.5.html#writeable"><strong>writeable</strong></a>. +<p><a name="writeraw"></a> +<p></p><dt><strong><strong>write raw (G)</strong></strong><dd> +<p>This parameter controls whether or not the server will support raw writes SMB's when transferring data from clients. You should never need to change this parameter. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> write raw = yes</code> -<p><br><a name="writeable"></a> -<li><strong><strong>writeable</strong></strong> -<p><br>An inverted synonym is <a href="../yodldocs/smb.conf.5.html#readonly"><strong>"read only"</strong></a>. -<p><br>If this parameter is <code>"no"</code>, then users of a service may not create +<p><a name="writeable"></a> +<p></p><dt><strong><strong>writeable</strong></strong><dd> +<p>An inverted synonym is <a href="smb.conf.5.html#readonly"><strong>"read only"</strong></a>. +<p>If this parameter is <code>"no"</code>, then users of a service may not create or modify files in the service's directory. -<p><br>Note that a printable service <a href="../yodldocs/smb.conf.5.html#printable"><strong>("printable = yes")</strong></a> +<p>Note that a printable service <a href="smb.conf.5.html#printable"><strong>("printable = yes")</strong></a> will <em>*ALWAYS*</em> allow writing to the directory (user privileges permitting), but only via spooling operations. -<p><br><strong>Default:</strong> +<p><strong>Default:</strong> <code> writeable = no</code> -<p><br><strong>Examples:</strong> +<p><strong>Examples:</strong> <pre> read only = no @@ -5029,50 +5029,50 @@ permitting), but only via spooling operations. </pre> -<p><br></ul> -<p><br><a name="WARNINGS"></a> +<p></dl> +<p><a name="WARNINGS"></a> <h2>WARNINGS</h2> -<p><br>Although the configuration file permits service names to contain +<p>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. -<p><br>On a similar note, many clients - especially DOS clients - limit +<p>On a similar note, many clients - especially DOS clients - limit service names to eight characters. <a href="smbd.8.html"><strong>Smbd</strong></a> 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. -<p><br>Use of the <a href="../yodldocs/smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="../yodldocs/smb.conf.5.html#printers"><strong>[printers]</strong></a> +<p>Use of the <a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> 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. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, +<p><a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>, <a href="testprns.1.html"><strong>testprns (1)</strong></a>, <a href="samba.7.html"><strong>Samba</strong></a>, <a href="nmblookup.1.html"><strong>nmblookup (1)</strong></a>, <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a>, <a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by +<p>The original Samba software and related utilities were created by Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index a68538aa155..42136f19474 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -3,9 +3,10 @@ + <html><head><title>smbclient (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,575 +16,574 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbclient - ftp-like client to access SMB/CIFS resources on servers -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbclient</strong> <a href="smbclient.1.html#servicename">servicename</a> [<a href="smbclient.1.html#minuss">-s smb.conf</a>] [<a href="smbclient.1.html#minusO">-O socket options</a>][<a href="smbclient.1.html#minusR">-R name resolve order</a>] [<a href="smbclient.1.html#minusM">-M NetBIOS name</a>] [<a href="smbclient.1.html#minusi">-i scope</a>] [<a href="smbclient.1.html#minusN">-N</a>] [<a href="smbclient.1.html#minusn">-n NetBIOS name</a>] [<a href="smbclient.1.html#minusd">-d debuglevel</a>] [<a href="smbclient.1.html#minusP">-P</a>] [<a href="smbclient.1.html#minusp">-p port</a>] [<a href="smbclient.1.html#minusl">-l log basename</a>] [<a href="smbclient.1.html#minush">-h</a>] [<a href="smbclient.1.html#minusI">-I dest IP</a>] [<a href="smbclient.1.html#minusE">-E</a>] [<a href="smbclient.1.html#minusU">-U username</a>] [<a href="smbclient.1.html#minusL">-L NetBIOS name</a>] [<a href="smbclient.1.html#minust">-t terminal code</a>] [<a href="smbclient.1.html#minusm">-m max protocol</a>] [<a href="smbclient.1.html#minusb">-b buffersize</a>] [<a href="smbclient.1.html#minusW">-W workgroup</a>] [<a href="smbclient.1.html#minusT">-T<c|x>IXFqgbNan</a>] [<a href="smbclient.1.html#minusD">-D directory</a>] [<a href="smbclient.1.html#minusc">-c command string</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbclient</strong> <a href="smbclient.1.html#servicename">servicename</a> [<a href="smbclient.1.html#minuss">-s smb.conf</a>] [<a href="smbclient.1.html#minusO">-O socket options</a>][<a href="smbclient.1.html#minusR">-R name resolve order</a>] [<a href="smbclient.1.html#minusM">-M NetBIOS name</a>] [<a href="smbclient.1.html#minusi">-i scope</a>] [<a href="smbclient.1.html#minusN">-N</a>] [<a href="smbclient.1.html#minusn">-n NetBIOS name</a>] [<a href="smbclient.1.html#minusd">-d debuglevel</a>] [<a href="smbclient.1.html#minusP">-P</a>] [<a href="smbclient.1.html#minusp">-p port</a>] [<a href="smbclient.1.html#minusl">-l log basename</a>] [<a href="smbclient.1.html#minush">-h</a>] [<a href="smbclient.1.html#minusI">-I dest IP</a>] [<a href="smbclient.1.html#minusE">-E</a>] [<a href="smbclient.1.html#minusU">-U username</a>] [<a href="smbclient.1.html#minusL">-L NetBIOS name</a>] [<a href="smbclient.1.html#minust">-t terminal code</a>] [<a href="smbclient.1.html#minusm">-m max protocol</a>] [<a href="smbclient.1.html#minusb">-b buffersize</a>] [<a href="smbclient.1.html#minusW">-W workgroup</a>] [<a href="smbclient.1.html#minusT">-T<c|x>IXFqgbNan</a>] [<a href="smbclient.1.html#minusD">-D directory</a>] [<a href="smbclient.1.html#minusc">-c command string</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>smbclient</strong> is a client that can 'talk' to an SMB/CIFS server. It +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>smbclient</strong> is a client that can 'talk' to an SMB/CIFS server. It offers an interface similar to that of the ftp program (see <strong>ftp (1)</strong>). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="servicename"></a> -<li><strong><strong>servicename</strong></strong> servicename is the name of the service you want +<p><dl> +<p><a name="servicename"></a> +<p></p><dt><strong><strong>servicename</strong></strong><dd> servicename is the name of the service you want to use on the server. A service name takes the form <code>//server/service</code> where <em>server</em> is the NetBIOS name of the SMB/CIFS server offering the desired service and <em>service</em> is the name of the service offered. Thus to connect to the service <em>printer</em> on the SMB/CIFS server <em>smbserver</em>, you would use the servicename -<p><br><code>//smbserver/printer</code> -<p><br>Note that the server name required is NOT necessarily the IP (DNS) +<p><code>//smbserver/printer</code> +<p>Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server. -<p><br>The server name is looked up according to either the +<p>The server name is looked up according to either the <a href="smbclient.1.html#minusR"><strong>-R</strong></a> parameter to <strong>smbclient</strong> or using the <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> parameter in the smb.conf file, allowing an administrator to change the order and methods by which server names are looked up. -<p><br><a name="password"></a> -<li><strong><strong>password</strong></strong> password is the password required to access the +<p><a name="password"></a> +<p></p><dt><strong><strong>password</strong></strong><dd> password is the password required to access the specified service on the specified server. If this parameter is supplied, the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option (suppress password prompt) is assumed. -<p><br>There is no default password. If no password is supplied on the +<p>There is no default password. If no password is supplied on the command line (either by using this parameter or adding a password to the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> option (see below)) and the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option is not specified, the client will prompt for a password, even if the desired service does not require one. (If no password is required, simply press ENTER to provide a null password.) -<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist +<p>Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers. -<p><br>Be cautious about including passwords in scripts. -<p><br><a name="minuss"></a> -<li><strong><strong>-s smb.conf</strong></strong> This parameter specifies the pathname to the +<p>Be cautious about including passwords in scripts. +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s smb.conf</strong></strong><dd> This parameter specifies the pathname to the Samba configuration file, smb.conf. This file controls all aspects of the Samba setup on the machine and smbclient also needs to read this file. -<p><br><a name="minusO"></a> -<li><strong><strong>-O socket options</strong></strong> TCP socket options to set on the client +<p><a name="minusO"></a> +<p></p><dt><strong><strong>-O socket options</strong></strong><dd> TCP socket options to set on the client socket. See the <a href="smb.conf.5.html#socketoptions">socket options</a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> manpage for the list of valid options. -<p><br><a name="minusR"></a> -<li><strong><strong>-R name resolve order</strong></strong> This option allows the user of +<p><a name="minusR"></a> +<p></p><dt><strong><strong>-R name resolve order</strong></strong><dd> This option allows the user of smbclient to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to. -<p><br>The options are :"lmhosts", "host", "wins" and "bcast". They cause +<p>The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows : -<p><br><ul> -<p><br><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. +<p><dl> +<p><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. The lmhosts file is stored in the same directory as the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. -<p><br><li > <strong>host</strong> : Do a standard host name to IP address resolution, +<p><li > <strong>host</strong> : Do a standard host name to IP address resolution, using the system /etc/hosts, NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the <em>/etc/nsswitch.conf</em> file). -<p><br><li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins +<p><li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter in the smb.conf file. If no WINS server has been specified this method will be ignored. -<p><br><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces +<p><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter in the smb.conf file. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet. -<p><br></ul> -<p><br>If this parameter is not set then the name resolve order defined +<p></dl> +<p>If this parameter is not set then the name resolve order defined in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file parameter <a href="smb.conf.5.html#nameresolveorder">(<strong>name resolve order</strong>)</a> will be used. -<p><br>The default order is lmhosts, host, wins, bcast and without this +<p>The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the <a href="smb.conf.5.html#nameresolveorder"><strong>"name resolve order"</strong></a> parameter of the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file the name resolution methods will be attempted in this order. -<p><br><a name="minusM"></a> -<li><strong><strong>-M NetBIOS name</strong></strong> This options allows you to send messages, +<p><a name="minusM"></a> +<p></p><dt><strong><strong>-M NetBIOS name</strong></strong><dd> This options allows you to send messages, using the "WinPopup" protocol, to another computer. Once a connection is established you then type your message, pressing ^D (control-D) to end. -<p><br>If the receiving computer is running WinPopup the user will receive +<p>If the receiving computer is running WinPopup the user will receive the message and probably a beep. If they are not running WinPopup the message will be lost, and no error message will occur. -<p><br>The message is also automatically truncated if the message is over +<p>The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol. -<p><br>One useful trick is to cat the message through <strong>smbclient</strong>. +<p>One useful trick is to cat the message through <strong>smbclient</strong>. For example: -<p><br><code>cat mymessage.txt | smbclient -M FRED</code> -<p><br>will send the message in the file <em>mymessage.txt</em> to the machine FRED. -<p><br>You may also find the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> and <a href="smbclient.1.html#minusI"><strong>-I</strong></a> options useful, as they allow +<p><code>cat mymessage.txt | smbclient -M FRED</code> +<p>will send the message in the file <em>mymessage.txt</em> to the machine FRED. +<p>You may also find the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> and <a href="smbclient.1.html#minusI"><strong>-I</strong></a> options useful, as they allow you to control the FROM and TO parts of the message. -<p><br>See the <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a> +<p>See the <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a> parameter in the <strong>smb.conf (5)</strong> for a description of how to handle incoming WinPopup messages in Samba. -<p><br>Note: Copy WinPopup into the startup group on your WfWg PCs if you +<p>Note: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages. -<p><br><a name="minusi"></a> -<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that smbclient will use +<p><a name="minusi"></a> +<p></p><dt><strong><strong>-i scope</strong></strong><dd> This specifies a NetBIOS scope that smbclient will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are <em>very</em> rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with. -<p><br><a name="minusN"></a> -<li><strong><strong>-N</strong></strong> If specified, this parameter suppresses the normal +<p><a name="minusN"></a> +<p></p><dt><strong><strong>-N</strong></strong><dd> If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when accessing a service that does not require a password. -<p><br>Unless a password is specified on the command line or this parameter +<p>Unless a password is specified on the command line or this parameter is specified, the client will request a password. -<p><br><a name="minusn"></a> -<li><strong><strong>-n NetBIOS name</strong></strong> By default, the client will use the local +<p><a name="minusn"></a> +<p></p><dt><strong><strong>-n NetBIOS name</strong></strong><dd> By default, the client will use the local machine's hostname (in uppercase) as its NetBIOS name. This parameter allows you to override the host name and use whatever NetBIOS name you wish. -<p><br><a name="minusd"></a> -<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10, or the +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10, or the letter 'A'. -<p><br>The default value if this parameter is not specified is zero. -<p><br>The higher this value, the more detail will be logged to the log files +<p>The default value if this parameter is not specified is zero. +<p>The higher this value, the more detail will be logged to the log files about the activities of the client. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out. -<p><br>Levels above 1 will generate considerable amounts of log data, and +<p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. If debuglevel is set to the letter 'A', then <em>all</em> debug messages will be printed. This setting is for developers only (and people who <em>really</em> want to know how the code works internally). -<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log +<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. -<p><br><a name="minusP"></a> -<li><strong><strong>-P</strong></strong> This option is no longer used. The code in Samba2.0 +<p><a name="minusP"></a> +<p></p><dt><strong><strong>-P</strong></strong><dd> This option is no longer used. The code in Samba2.0 now lets the server decide the device type, so no printer specific flag is needed. -<p><br><a name="minusp"></a> -<li><strong><strong>-p port</strong></strong> This number is the TCP port number that will be used +<p><a name="minusp"></a> +<p></p><dt><strong><strong>-p port</strong></strong><dd> This number is the TCP port number that will be used when making connections to the server. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the default. -<p><br><a name="minusl"></a> -<li><strong><strong>-l logfilename</strong></strong> If specified, logfilename specifies a base +<p><a name="minusl"></a> +<p></p><dt><strong><strong>-l logfilename</strong></strong><dd> If specified, logfilename specifies a base filename into which operational data from the running client will be logged. -<p><br>The default base name is specified at compile time. -<p><br>The base name is used to generate actual log file names. For example, +<p>The default base name is specified at compile time. +<p>The base name is used to generate actual log file names. For example, if the name specified was "log", the debug file would be <code>log.client</code>. -<p><br>The log file generated is never removed by the client. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> Print the usage message for the client. -<p><br><a name="minusI"></a> -<li><strong><strong>-I IP address</strong></strong> IP address is the address of the server to +<p>The log file generated is never removed by the client. +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> Print the usage message for the client. +<p><a name="minusI"></a> +<p></p><dt><strong><strong>-I IP address</strong></strong><dd> IP address is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation. -<p><br>Normally the client would attempt to locate a named SMB/CIFS server by +<p>Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the <a href="smbclient.1.html#minusR"><strong>name resolve order</strong></a> parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored. -<p><br>There is no default for this parameter. If not supplied, it will be +<p>There is no default for this parameter. If not supplied, it will be determined automatically by the client as described above. -<p><br><a name="minusE"></a> -<li><strong><strong>-E</strong></strong> This parameter causes the client to write messages to the +<p><a name="minusE"></a> +<p></p><dt><strong><strong>-E</strong></strong><dd> This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream. -<p><br>By default, the client writes messages to standard output - typically +<p>By default, the client writes messages to standard output - typically the user's tty. -<p><br><a name="minusU"></a> -<li><strong><strong>-U username</strong></strong> This specifies the user name that will be used by +<p><a name="minusU"></a> +<p></p><dt><strong><strong>-U username</strong></strong><dd> This specifies the user name that will be used by the client to make a connection, assuming your server is not a downlevel server that is running a protocol level that uses passwords on shares, not on usernames. -<p><br>Some servers are fussy about the case of this name, and some insist +<p>Some servers are fussy about the case of this name, and some insist that it must be a valid NetBIOS name. -<p><br>If no username is supplied, it will default to an uppercase version of +<p>If no username is supplied, it will default to an uppercase version of the environment variable <code>USER</code> or <code>LOGNAME</code> in that order. If no username is supplied and neither environment variable exists the username "GUEST" will be used. -<p><br>If the <code>USER</code> environment variable contains a '%' character, +<p>If the <code>USER</code> environment variable contains a '%' character, everything after that will be treated as a password. This allows you to set the environment variable to be <code>USER=username%password</code> so that a password is not passed on the command line (where it may be seen by the ps command). -<p><br>If the service you are connecting to requires a password, it can be +<p>If the service you are connecting to requires a password, it can be supplied using the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> option, by appending a percent symbol ("%") then the password to username. For example, to attach to a service as user <code>"fred"</code> with password <code>"secret"</code>, you would specify. <br> -<p><br><code>-U fred%secret</code> <br> -<p><br>on the command line. Note that there are no spaces around the percent +<p><code>-U fred%secret</code> <br> +<p>on the command line. Note that there are no spaces around the percent symbol. -<p><br>If you specify the password as part of username then the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option +<p>If you specify the password as part of username then the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option (suppress password prompt) is assumed. -<p><br>If you specify the password as a parameter <em>AND</em> as part of username +<p>If you specify the password as a parameter <em>AND</em> as part of username then the password as part of username will take precedence. Putting nothing before or nothing after the percent symbol will cause an empty username or an empty password to be used, respectively. -<p><br>The password may also be specified by setting up an environment +<p>The password may also be specified by setting up an environment variable called <code>PASSWD</code> that contains the users password. Note that this may be very insecure on some systems but on others allows users to script smbclient commands without having a password appear in the command line of a process listing. -<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist +<p>Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers. -<p><br>Be cautious about including passwords in scripts or in the +<p>Be cautious about including passwords in scripts or in the <code>PASSWD</code> environment variable. Also, on many systems the command line of a running process may be seen via the <code>ps</code> command to be safe always allow smbclient to prompt for a password and type it in directly. -<p><br><a name="minusL"></a> -<li><strong><strong>-L</strong></strong> This option allows you to look at what services are +<p><a name="minusL"></a> +<p></p><dt><strong><strong>-L</strong></strong><dd> This option allows you to look at what services are available on a server. You use it as <code>"smbclient -L host"</code> and a list should appear. The <a href="smbclient.1.html#minusI"><strong>-I</strong></a> option may be useful if your NetBIOS names don't match your tcp/ip dns host names or if you are trying to reach a host on another network. -<p><br><a name="minust"></a> -<li><strong><strong>-t terminal code</strong></strong> This option tells smbclient how to interpret +<p><a name="minust"></a> +<p></p><dt><strong><strong>-t terminal code</strong></strong><dd> This option tells smbclient how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (<em>EUC</em> instead of <em>SJIS</em> for example). Setting this parameter will let smbclient convert between the UNIX filenames and the SMB filenames correctly. This option has not been seriously tested and may have some problems. -<p><br>The terminal codes include <code>sjis</code>, <code>euc</code>, <code>jis7</code>, <code>jis8</code>, +<p>The terminal codes include <code>sjis</code>, <code>euc</code>, <code>jis7</code>, <code>jis8</code>, <code>junet</code>, <code>hex</code>, <code>cap</code>. This is not a complete list, check the Samba source code for the complete list. -<p><br><a name="minusm"></a> -<li><strong><strong>-m max protocol level</strong></strong> With the new code in Samba2.0, +<p><a name="minusm"></a> +<p></p><dt><strong><strong>-m max protocol level</strong></strong><dd> With the new code in Samba2.0, <strong>smbclient</strong> always attempts to connect at the maximum protocols level the server supports. This parameter is preserved for backwards compatibility, but any string following the <strong>-m</strong> will be ignored. -<p><br><a name="minusb"></a> -<li><strong><strong>-b buffersize</strong></strong> This option changes the transmit/send buffer +<p><a name="minusb"></a> +<p></p><dt><strong><strong>-b buffersize</strong></strong><dd> This option changes the transmit/send buffer size when getting or putting a file from/to the server. The default is 65520 bytes. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server. -<p><br><a name="minusW"></a> -<li><strong><strong>-W WORKGROUP</strong></strong> Override the default workgroup specified in the +<p><a name="minusW"></a> +<p></p><dt><strong><strong>-W WORKGROUP</strong></strong><dd> Override the default workgroup specified in the <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> parameter of the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file for this connection. This may be needed to connect to some servers. -<p><br><a name="minusT"></a> <li><strong><strong>-T tar options</strong></strong> smbclient may be used to create +<p><a name="minusT"></a> <p></p><dt><strong><strong>-T tar options</strong></strong><dd> smbclient may be used to create <strong>tar (1)</strong> compatible backups of all the files on an SMB/CIFS share. The secondary tar flags that can be given to this option are : -<p><br><ul> -<p><br><li><strong><strong>c</strong></strong> Create a tar file on UNIX. Must be followed by the +<p><dl> +<p><p></p><dt><strong><strong>c</strong></strong><dd> Create a tar file on UNIX. Must be followed by the name of a tar file, tape device or <code>"-"</code> for standard output. If using standard output you must turn the log level to its lowest value <code>-d0</code> to avoid corrupting your tar file. This flag is mutually exclusive with the <strong>x</strong> flag. -<p><br><li><strong><strong>x</strong></strong> Extract (restore) a local tar file back to a +<p><p></p><dt><strong><strong>x</strong></strong><dd> Extract (restore) a local tar file back to a share. Unless the <a href="smbclient.1.html#minusD"><strong>-D</strong></a> option is given, the tar files will be restored from the top level of the share. Must be followed by the name of the tar file, device or <code>"-"</code> for standard input. Mutually exclusive with the <strong>c</strong> flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get their creation dates restored properly. -<p><br><li><strong><strong>I</strong></strong> Include files and directories. Is the default +<p><p></p><dt><strong><strong>I</strong></strong><dd> Include files and directories. Is the default behavior when filenames are specified above. Causes tar files to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing works in one of two ways. See <strong>r</strong> below. -<p><br><li><strong><strong>X</strong></strong> Exclude files and directories. Causes tar files to +<p><p></p><dt><strong><strong>X</strong></strong><dd> Exclude files and directories. Causes tar files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. See <strong>r</strong> below. -<p><br><li><strong><strong>b</strong></strong> Blocksize. Must be followed by a valid (greater than +<p><p></p><dt><strong><strong>b</strong></strong><dd> Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. -<p><br><li><strong><strong>g</strong></strong> Incremental. Only back up files that have the +<p><p></p><dt><strong><strong>g</strong></strong><dd> Incremental. Only back up files that have the archive bit set. Useful only with the <strong>c</strong> flag. -<p><br><li><strong><strong>q</strong></strong> Quiet. Keeps tar from printing diagnostics as it +<p><p></p><dt><strong><strong>q</strong></strong><dd> Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet. -<p><br><li><strong><strong>r</strong></strong> Regular expression include or exclude. Uses regular +<p><p></p><dt><strong><strong>r</strong></strong><dd> Regular expression include or exclude. Uses regular regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on * and ?. -<p><br><li><strong><strong>N</strong></strong> Newer than. Must be followed by the name of a file +<p><p></p><dt><strong><strong>N</strong></strong><dd> Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the <strong>c</strong> flag. -<p><br><li><strong><strong>a</strong></strong> Set archive bit. Causes the archive bit to be reset +<p><p></p><dt><strong><strong>a</strong></strong><dd> Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the <strong>g</strong> and <strong>c</strong> flags. -<p><br></ul> -<p><br><em>Tar Long File Names</em> -<p><br>smbclient's tar option now supports long file names both on backup and +<p></dl> +<p><em>Tar Long File Names</em> +<p>smbclient's tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when a tar archive is created, smbclient's tar option places all files in the archive with relative names, not absolute names. -<p><br><em>Tar Filenames</em> -<p><br>All file names can be given as DOS path names (with <code>\</code> as the +<p><em>Tar Filenames</em> +<p>All file names can be given as DOS path names (with <code>\</code> as the component separator) or as UNIX path names (with <code>/</code> as the component separator). -<p><br><em>Examples</em> -<p><br><ul> -<p><br><li > Restore from tar file backup.tar into myshare on mypc (no password on share). -<p><br><code>smbclient //mypc/myshare "" -N -Tx backup.tar</code> -<p><br><li > Restore everything except users/docs -<p><br><code>smbclient //mypc/myshare "" -N -TXx backup.tar users/docs</code> -<p><br><li > Create a tar file of the files beneath users/docs. -<p><br><code>smbclient //mypc/myshare "" -N -Tc backup.tar users/docs</code> -<p><br><li > Create the same tar file as above, but now use a DOS path name. -<p><br><code>smbclient //mypc/myshare "" -N -tc backup.tar users\edocs</code> -<p><br><li > Create a tar file of all the files and directories in the share. -<p><br><code>smbclient //mypc/myshare "" -N -Tc backup.tar *</code> -<p><br></ul> -<p><br><a name="minusD"></a> -<li><strong><strong>-D initial directory</strong></strong> Change to initial directory before +<p><em>Examples</em> +<p><dl> +<p><li > Restore from tar file backup.tar into myshare on mypc (no password on share). +<p><code>smbclient //mypc/myshare "" -N -Tx backup.tar</code> +<p><li > Restore everything except users/docs +<p><code>smbclient //mypc/myshare "" -N -TXx backup.tar users/docs</code> +<p><li > Create a tar file of the files beneath users/docs. +<p><code>smbclient //mypc/myshare "" -N -Tc backup.tar users/docs</code> +<p><li > Create the same tar file as above, but now use a DOS path name. +<p><code>smbclient //mypc/myshare "" -N -tc backup.tar users\edocs</code> +<p><li > Create a tar file of all the files and directories in the share. +<p><code>smbclient //mypc/myshare "" -N -Tc backup.tar *</code> +<p></dl> +<p><a name="minusD"></a> +<p></p><dt><strong><strong>-D initial directory</strong></strong><dd> Change to initial directory before starting. Probably only of any use with the tar <a href="smbclient.1.html#minusT"><strong>-T</strong></a> option. -<p><br><a name="minusc"></a> -<li><strong><strong>-c command string</strong></strong> command string is a semicolon separated +<p><a name="minusc"></a> +<p></p><dt><strong><strong>-c command string</strong></strong><dd> command string is a semicolon separated list of commands to be executed instead of prompting from stdin. <a href="smbclient.1.html#minusN"><strong>-N</strong></a> is implied by <strong>-c</strong>. -<p><br>This is particularly useful in scripts and for printing stdin to the +<p>This is particularly useful in scripts and for printing stdin to the server, e.g. <code>-c 'print -'</code>. -<p><br></ul> -<p><br><a name="OPERATIONS"></a> +<p></dl> +<p><a name="OPERATIONS"></a> <h2>OPERATIONS</h2> -<p><br>Once the client is running, the user is presented with a prompt : -<p><br><code>smb:\></code> -<p><br>The backslash ("\") indicates the current working directory on the +<p>Once the client is running, the user is presented with a prompt : +<p><code>smb:\></code> +<p>The backslash ("\") indicates the current working directory on the server, and will change if the current working directory is changed. -<p><br>The prompt indicates that the client is ready and waiting to carry out +<p>The prompt indicates that the client is ready and waiting to carry out a user command. Each command is a single word, optionally followed by parameters specific to that command. Command and parameters are space-delimited unless these notes specifically state otherwise. All commands are case-insensitive. Parameters to commands may or may not be case sensitive, depending on the command. -<p><br>You can specify file names which have spaces in them by quoting the +<p>You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name". -<p><br>Parameters shown in square brackets (e.g., "[parameter]") are +<p>Parameters shown in square brackets (e.g., "[parameter]") are optional. If not given, the command will use suitable defaults. Parameters shown in angle brackets (e.g., "<parameter>") are required. -<p><br>Note that all commands operating on the server are actually performed +<p>Note that all commands operating on the server are actually performed by issuing a request to the server. Thus the behavior may vary from server to server, depending on how the server was implemented. -<p><br>The commands available are given here in alphabetical order. -<p><br><ul> -<p><br><a name="questionmark"></a> <li><strong><strong>? [command]</strong></strong> If "command" is specified, +<p>The commands available are given here in alphabetical order. +<p><dl> +<p><a name="questionmark"></a> <p></p><dt><strong><strong>? [command]</strong></strong><dd> If "command" is specified, the <strong>?</strong> command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed. -<p><br><a name="exclaimationmark"></a> <li><strong><strong>! [shell command]</strong></strong> If "shell command" +<p><a name="exclaimationmark"></a> <p></p><dt><strong><strong>! [shell command]</strong></strong><dd> If "shell command" is specified, the <strong>!</strong> command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run. -<p><br><a name="cd"></a> <li><strong><strong>cd [directory name]</strong></strong> If "directory name" is +<p><a name="cd"></a> <p></p><dt><strong><strong>cd [directory name]</strong></strong><dd> If "directory name" is specified, the current working directory on the server will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. -<p><br>If no directory name is specified, the current working directory on +<p>If no directory name is specified, the current working directory on the server will be reported. -<p><br><a name="del"></a> <li><strong><strong>del <mask></strong></strong> The client will request that the server +<p><a name="del"></a> <p></p><dt><strong><strong>del <mask></strong></strong><dd> The client will request that the server attempt to delete all files matching "mask" from the current working directory on the server. -<p><br><a name="dir"></a> <li><strong><strong>dir <mask></strong></strong> A list of the files matching "mask" in +<p><a name="dir"></a> <p></p><dt><strong><strong>dir <mask></strong></strong><dd> A list of the files matching "mask" in the current working directory on the server will be retrieved from the server and displayed. -<p><br><a name="exit"></a> <li><strong><strong>exit</strong></strong> Terminate the connection with the server and +<p><a name="exit"></a> <p></p><dt><strong><strong>exit</strong></strong><dd> Terminate the connection with the server and exit from the program. -<p><br><a name="get"></a> <li><strong><strong>get <remote file name> [local file name]</strong></strong> Copy the +<p><a name="get"></a> <p></p><dt><strong><strong>get <remote file name> [local file name]</strong></strong><dd> Copy the file called "remote file name" from the server to the machine running the client. If specified, name the local copy "local file name". Note that all transfers in smbclient are binary. See also the <a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command. -<p><br><a name="help"></a> <li><strong><strong>help [command]</strong></strong> See the <a href="smbclient.1.html#questionmark"><strong>?</strong></a> +<p><a name="help"></a> <p></p><dt><strong><strong>help [command]</strong></strong><dd> See the <a href="smbclient.1.html#questionmark"><strong>?</strong></a> command above. -<p><br><a name="lcd"></a> <li><strong><strong>lcd [directory name]</strong></strong> If "directory name" is +<p><a name="lcd"></a> <p></p><dt><strong><strong>lcd [directory name]</strong></strong><dd> If "directory name" is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. -<p><br>If no directory name is specified, the name of the current working +<p>If no directory name is specified, the name of the current working directory on the local machine will be reported. -<p><br><a name="lowercase"></a> <li><strong><strong>lowercase</strong></strong> Toggle lowercasing of filenames +<p><a name="lowercase"></a> <p></p><dt><strong><strong>lowercase</strong></strong><dd> Toggle lowercasing of filenames for the <a href="smbclient.1.html#get"><strong>get</strong></a> and <a href="smbclient.1.html#mget"><strong>mget</strong></a> commands. -<p><br>When lowercasing is toggled ON, local filenames are converted to +<p>When lowercasing is toggled ON, local filenames are converted to lowercase when using the <a href="smbclient.1.html#get"><strong>get</strong></a> and <a href="smbclient.1.html#mget"><strong>mget</strong></a> commands. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems. -<p><br><a name="ls"></a> <li><strong><strong>ls <mask></strong></strong> See the <a href="smbclient.1.html#dir"><strong>dir</strong></a> command above. -<p><br><a name="mask"></a> <li><strong><strong>mask <mask></strong></strong> This command allows the user to set +<p><a name="ls"></a> <p></p><dt><strong><strong>ls <mask></strong></strong><dd> See the <a href="smbclient.1.html#dir"><strong>dir</strong></a> command above. +<p><a name="mask"></a> <p></p><dt><strong><strong>mask <mask></strong></strong><dd> This command allows the user to set up a mask which will be used during recursive operation of the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands. -<p><br>The masks specified to the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and +<p>The masks specified to the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands act as filters for directories rather than files when recursion is toggled ON. -<p><br>The mask specified with the .B mask command is necessary to filter +<p>The mask specified with the .B mask command is necessary to filter files within those directories. For example, if the mask specified in an <a href="smbclient.1.html#mget"><strong>mget</strong></a> command is "source*" and the mask specified with the mask command is "*.c" and recursion is toggled ON, the <a href="smbclient.1.html#mget"><strong>mget</strong></a> command will retrieve all files matching "*.c" in all directories below and including all directories matching "source*" in the current working directory. -<p><br>Note that the value for mask defaults to blank (equivalent to "*") and +<p>Note that the value for mask defaults to blank (equivalent to "*") and remains so until the mask command is used to change it. It retains the most recently specified value indefinitely. To avoid unexpected results it would be wise to change the value of .I mask back to "*" after using the <a href="smbclient.1.html#mget"><strong>mget</strong></a> or <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands. -<p><br><a name="md"></a> <li><strong><strong>md <directory name></strong></strong> See the <a href="smbclient.1.html#mkdir"><strong>mkdir</strong></a> +<p><a name="md"></a> <p></p><dt><strong><strong>md <directory name></strong></strong><dd> See the <a href="smbclient.1.html#mkdir"><strong>mkdir</strong></a> command. -<p><br><a name="mget"></a> <li><strong><strong>mget <mask></strong></strong> Copy all files matching mask from the +<p><a name="mget"></a> <p></p><dt><strong><strong>mget <mask></strong></strong><dd> Copy all files matching mask from the server to the machine running the client. -<p><br>Note that mask is interpreted differently during recursive operation +<p>Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the <a href="smbclient.1.html#recurse"><strong>recurse</strong></a> and <a href="smbclient.1.html#mask"><strong>mask</strong></a> commands for more information. Note that all transfers in .B smbclient are binary. See also the <a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command. -<p><br><a name="mkdir"></a> <li><strong><strong>mkdir <directory name></strong></strong> Create a new directory on +<p><a name="mkdir"></a> <p></p><dt><strong><strong>mkdir <directory name></strong></strong><dd> Create a new directory on the server (user access privileges permitting) with the specified name. -<p><br><a name="mput"></a> <li><strong><strong>mput <mask></strong></strong> Copy all files matching mask in +<p><a name="mput"></a> <p></p><dt><strong><strong>mput <mask></strong></strong><dd> Copy all files matching mask in the current working directory on the local machine to the current working directory on the server. -<p><br>Note that mask is interpreted differently during recursive operation +<p>Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the <a href="smbclient.1.html#recurse"><strong>recurse</strong></a> and <a href="smbclient.1.html#mask"><strong>mask</strong></a> commands for more information. Note that all transfers in .B smbclient are binary. -<p><br><a name="print"></a> <li><strong><strong>print <file name></strong></strong> Print the specified file +<p><a name="print"></a> <p></p><dt><strong><strong>print <file name></strong></strong><dd> Print the specified file from the local machine through a printable service on the server. -<p><br>See also the <a href="smbclient.1.html#printmode"><strong>printmode</strong></a> command. -<p><br><a name="printmode"></a> <li><strong><strong>printmode <graphics or text></strong></strong> Set the print +<p>See also the <a href="smbclient.1.html#printmode"><strong>printmode</strong></a> command. +<p><a name="printmode"></a> <p></p><dt><strong><strong>printmode <graphics or text></strong></strong><dd> Set the print mode to suit either binary data (such as graphical information) or text. Subsequent print commands will use the currently set print mode. -<p><br><a name="prompt"></a> <li><strong><strong>prompt</strong></strong> Toggle prompting for filenames during +<p><a name="prompt"></a> <p></p><dt><strong><strong>prompt</strong></strong><dd> Toggle prompting for filenames during operation of the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands. -<p><br>When toggled ON, the user will be prompted to confirm the transfer of +<p>When toggled ON, the user will be prompted to confirm the transfer of each file during these commands. When toggled OFF, all specified files will be transferred without prompting. -<p><br><a name="put"></a> <li><strong><strong>put <local file name> [remote file name]</strong></strong> Copy the +<p><a name="put"></a> <p></p><dt><strong><strong>put <local file name> [remote file name]</strong></strong><dd> Copy the file called "local file name" from the machine running the client to the server. If specified, name the remote copy "remote file name". Note that all transfers in smbclient are binary. See also the <a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command. -<p><br><a name="queue"></a> <li><strong><strong>queue</strong></strong> Displays the print queue, showing the job +<p><a name="queue"></a> <p></p><dt><strong><strong>queue</strong></strong><dd> Displays the print queue, showing the job id, name, size and current status. -<p><br><a name="quit"></a> <li><strong><strong>quit</strong></strong> See the <a href="smbclient.1.html#exit"><strong>exit</strong></a> command. -<p><br><a name="rd"></a> <li><strong><strong>rd <directory name></strong></strong> See the <a href="smbclient.1.html#rmdir"><strong>rmdir</strong></a> +<p><a name="quit"></a> <p></p><dt><strong><strong>quit</strong></strong><dd> See the <a href="smbclient.1.html#exit"><strong>exit</strong></a> command. +<p><a name="rd"></a> <p></p><dt><strong><strong>rd <directory name></strong></strong><dd> See the <a href="smbclient.1.html#rmdir"><strong>rmdir</strong></a> command. -<p><br><a name="recurse"></a> <li><strong><strong>recurse</strong></strong> Toggle directory recursion for the +<p><a name="recurse"></a> <p></p><dt><strong><strong>recurse</strong></strong><dd> Toggle directory recursion for the commands <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a>. -<p><br>When toggled ON, these commands will process all directories in the +<p>When toggled ON, these commands will process all directories in the source directory (i.e., the directory they are copying .IR from ) and will recurse into any that match the mask specified to the command. Only files that match the mask specified using the <a href="smbclient.1.html#mask"><strong>mask</strong></a> command will be retrieved. See also the <a href="smbclient.1.html#mask"><strong>mask</strong></a> command. -<p><br>When recursion is toggled OFF, only files from the current working +<p>When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the <a href="smbclient.1.html#mget"><strong>mget</strong></a> or <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands will be copied, and any mask specified using the <a href="smbclient.1.html#mask"><strong>mask</strong></a> command will be ignored. -<p><br><a name="rm"></a> <li><strong><strong>rm <mask></strong></strong> Remove all files matching mask from +<p><a name="rm"></a> <p></p><dt><strong><strong>rm <mask></strong></strong><dd> Remove all files matching mask from the current working directory on the server. -<p><br><a name="rmdir"></a> <li><strong><strong>rmdir <directory name></strong></strong> Remove the specified +<p><a name="rmdir"></a> <p></p><dt><strong><strong>rmdir <directory name></strong></strong><dd> Remove the specified directory (user access privileges permitting) from the server. -<p><br><a name="tar"></a> <li><strong><strong>tar <c|x>[IXbgNa]</strong></strong> Performs a tar operation - see +<p><a name="tar"></a> <p></p><dt><strong><strong>tar <c|x>[IXbgNa]</strong></strong><dd> Performs a tar operation - see the <a href="smbclient.1.html#minusT"><strong>-T</strong></a> command line option above. Behavior may be affected by the <a href="smbclient.1.html#tarmode"><strong>tarmode</strong></a> command (see below). Using g (incremental) and N (newer) will affect tarmode settings. Note that using the "-" option with tar x may not work - use the command line option instead. -<p><br><a name="blocksize"></a> <li><strong><strong>blocksize <blocksize></strong></strong> Blocksize. Must be +<p><a name="blocksize"></a> <p></p><dt><strong><strong>blocksize <blocksize></strong></strong><dd> Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. -<p><br><a name="tarmode"></a> <li><strong><strong>tarmode <full|inc|reset|noreset></strong></strong> Changes tar's +<p><a name="tarmode"></a> <p></p><dt><strong><strong>tarmode <full|inc|reset|noreset></strong></strong><dd> Changes tar's behavior with regard to archive bits. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode). In incremental mode, tar will only back up files with the archive bit set. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share). -<p><br><a name="setmode"></a> <li><strong><strong>setmode <filename> <perm=[+|\-]rsha></strong></strong> A version +<p><a name="setmode"></a> <p></p><dt><strong><strong>setmode <filename> <perm=[+|\-]rsha></strong></strong><dd> A version of the DOS attrib command to set file permissions. For example: -<p><br><code>setmode myfile +r</code> -<p><br>would make myfile read only. -<p><br></ul> -<p><br><a name="NOTES"></a> +<p><code>setmode myfile +r</code> +<p>would make myfile read only. +<p></dl> +<p><a name="NOTES"></a> <h2>NOTES</h2> -<p><br>Some servers are fussy about the case of supplied usernames, +<p>Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names. If you fail to connect try giving all parameters in uppercase. -<p><br>It is often necessary to use the <a href="smbclient.1.html#minusn"><strong>-n</strong></a> option when connecting to some +<p>It is often necessary to use the <a href="smbclient.1.html#minusn"><strong>-n</strong></a> option when connecting to some types of servers. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server. -<p><br>smbclient supports long file names where the server supports the +<p>smbclient supports long file names where the server supports the LANMAN2 protocol or above. -<p><br><a name="ENVIRONMENTVARIABLES"></a> +<p><a name="ENVIRONMENTVARIABLES"></a> <h2>ENVIRONMENT VARIABLES</h2> -<p><br>The variable <strong>USER</strong> may contain the username of the person using the +<p>The variable <strong>USER</strong> may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. -<p><br>The variable <strong>PASSWD</strong> may contain the password of the person using +<p>The variable <strong>PASSWD</strong> may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. -<p><br><a name="INSTALLATION"></a> +<p><a name="INSTALLATION"></a> <h2>INSTALLATION</h2> -<p><br>The location of the client program is a matter for individual system +<p>The location of the client program is a matter for individual system administrators. The following are thus suggestions only. -<p><br>It is recommended that the smbclient software be installed in the +<p>It is recommended that the smbclient software be installed in the /usr/local/samba/bin or /usr/samba/bin directory, this directory readable by all, writeable only by root. The client program itself should be executable by all. The client should <em>NOT</em> be setuid or setgid! -<p><br>The client log files should be put in a directory readable and +<p>The client log files should be put in a directory readable and writeable only by the user. -<p><br>To test the client, you will need to know the name of a running +<p>To test the client, you will need to know the name of a running SMB/CIFS server. It is possible to run <a href="smbd.8.html"><strong>smbd (8)</strong></a> an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server. -<p><br><a name="DIAGNOSTICS"></a> +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>Most diagnostics issued by the client are logged in a specified log +<p>Most diagnostics issued by the client are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line. -<p><br>The number and nature of diagnostics available depends on the debug +<p>The number and nature of diagnostics available depends on the debug level used by the client. If you have problems, set the debug level to 3 and peruse the log files. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="AUTHOR"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 8230d50f47b..766de0853f0 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -3,9 +3,10 @@ + <html><head><title>smbd (8)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,178 +16,170 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbd - server to provide SMB/CIFS services to clients -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbd</strong> [<a href="smbd.8.html#minusD">-D</a>] [<a href="smbd.8.html#minusa">-a</a>] [<a href="smbd.8.html#minuso">-o</a>] [<a href="smbd.8.html#minusP">-P</a>] [<a href="smbd.8.html#minush">-h</a>] [<a href="smbd.8.html#minusV">-V</a>] [<a href="smbd.8.html#minusd">-d debuglevel</a>] [<a href="smbd.8.html#minusl">-l log file</a>] [<a href="smbd.8.html#minusp">-p port number</a>] [<a href="smbd.8.html#minusO">-O socket options</a>] [<a href="smbd.8.html#minuss">-s configuration file</a>] [<a href="smbd.8.html#minusi">-i scope</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbd</strong> [<a href="smbd.8.html#minusD">-D</a>] [<a href="smbd.8.html#minusa">-a</a>] [<a href="smbd.8.html#minuso">-o</a>] [<a href="smbd.8.html#minusP">-P</a>] [<a href="smbd.8.html#minush">-h</a>] [<a href="smbd.8.html#minusV">-V</a>] [<a href="smbd.8.html#minusd">-d debuglevel</a>] [<a href="smbd.8.html#minusl">-l log file</a>] [<a href="smbd.8.html#minusp">-p port number</a>] [<a href="smbd.8.html#minusO">-O socket options</a>] [<a href="smbd.8.html#minuss">-s configuration file</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>smbd</strong> is the server daemon that provides filesharing and printing +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>smbd</strong> is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95, Windows NT, OS/2, DAVE for Macintosh, and smbfs for Linux. -<p><br>An extensive description of the services that the server can provide +<p>An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. This man page will not describe the services, but will concentrate on the administrative aspects of running the server. -<p><br>Please note that there are significant security implications to +<p>Please note that there are significant security implications to running this server, and the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> manpage should be regarded as mandatory reading before proceeding with installation. -<p><br>A session is created whenever a client requests one. Each client gets +<p>A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all connections from its client are closed, the copy of the server for that client terminates. -<p><br>The configuration file, and any files that it includes, are +<p>The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to disconnect from the service, or smbd killed and restarted. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minusD"></a> -<li><strong><strong>-D</strong></strong> If specified, this parameter causes the server to operate as a +<p><dl> +<p><a name="minusD"></a> +<p></p><dt><strong><strong>-D</strong></strong><dd> If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a daemon is the recommended way of running smbd for servers that provide more than casual use file and print services. -<p><br>By default, the server will NOT operate as a daemon. -<p><br><a name="minusa"></a> -<li><strong><strong>-a</strong></strong> If this parameter is specified, each new connection will +<p>By default, the server will NOT operate as a daemon. +<p><a name="minusa"></a> +<p></p><dt><strong><strong>-a</strong></strong><dd> If this parameter is specified, each new connection will append log messages to the log file. This is the default. -<p><br><a name="minuso"></a> -<li><strong><strong>-o</strong></strong> If this parameter is specified, the log files will be +<p><a name="minuso"></a> +<p></p><dt><strong><strong>-o</strong></strong><dd> If this parameter is specified, the log files will be overwritten when opened. By default, the log files will be appended to. -<p><br><a name="minusP"></a> -<li><strong><strong>-P</strong></strong> Passive option. Causes smbd not to send any network traffic +<p><a name="minusP"></a> +<p></p><dt><strong><strong>-P</strong></strong><dd> Passive option. Causes smbd not to send any network traffic out. Used for debugging by the developers only. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> Prints the help information (usage) for <strong>smbd</strong>. -<p><br><a name="minusV"></a> -<li><strong><strong>-V</strong></strong> Prints the version number for <strong>smbd</strong>. -<p><br><a name="minusd"></a> -<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10. -<p><br>The default value if this parameter is not specified is zero. -<p><br>The higher this value, the more detail will be logged to the log files +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> Prints the help information (usage) for <strong>smbd</strong>. +<p><a name="minusV"></a> +<p></p><dt><strong><strong>-V</strong></strong><dd> Prints the version number for <strong>smbd</strong>. +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10. +<p>The default value if this parameter is not specified is zero. +<p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out. -<p><br>Levels above 1 will generate considerable amounts of log data, and +<p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. -<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log +<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. -<p><br><a name="minusl"></a> -<li><strong><strong>-l log file</strong></strong> If specified, <em>log file</em> specifies +<p><a name="minusl"></a> +<p></p><dt><strong><strong>-l log file</strong></strong><dd> If specified, <em>log file</em> specifies a log filename into which informational and debug messages from the running server will be logged. The log file generated is never removed by the server although its size may be controlled by the <a href="smb.conf.5.html#maxlogsize"><strong>max log size</strong></a> option in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file. The default log file name is specified at compile time. -<p><br><a name="minusO"></a> -<li><strong><strong>-O socket options</strong></strong> See the <a href="smb.conf.5.html#socketoptions"><strong>socket +<p><a name="minusO"></a> +<p></p><dt><strong><strong>-O socket options</strong></strong><dd> See the <a href="smb.conf.5.html#socketoptions"><strong>socket options</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file for details. -<p><br><a name="minusp"></a> -<li><strong><strong>-p port number</strong></strong> port number is a positive integer value. The +<p><a name="minusp"></a> +<p></p><dt><strong><strong>-p port number</strong></strong><dd> port number is a positive integer value. The default value if this parameter is not specified is 139. -<p><br>This number is the port number that will be used when making +<p>This number is the port number that will be used when making connections to the server from client software. The standard (well-known) port number for the SMB over TCP is 139, hence the default. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator for help if you are in this situation. -<p><br>In order for the server to be useful by most clients, should you +<p>In order for the server to be useful by most clients, should you configure it on a port other than 139, you will require port redirection services on port 139, details of which are outlined in rfc1002.txt section 4.3.5. -<p><br>This parameter is not normally specified except in the above +<p>This parameter is not normally specified except in the above situation. -<p><br><a name="minuss"></a> -<li><strong><strong>-s configuration file</strong></strong> +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s configuration file</strong></strong><dd> The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See <strong>smb.conf (5)</strong> for more information. The default configuration file name is determined at compile time. -<p><br><a name="minusi"></a> -<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that the server will use -to communicate with when generating NetBIOS names. For details on the -use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes -are <em>very</em> rarely used, only set this parameter if you are the -system administrator in charge of all the NetBIOS systems you -communicate with. -<p><br></ul> -<p><br><a name="FILES"></a> +<p></dl> +<p><a name="FILES"></a> <h2>FILES</h2> -<p><br><strong>/etc/inetd.conf</strong> -<p><br>If the server is to be run by the inetd meta-daemon, this file must +<p><strong>/etc/inetd.conf</strong> +<p>If the server is to be run by the inetd meta-daemon, this file must contain suitable startup information for the meta-daemon. See the section <a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below. -<p><br><strong>/etc/rc</strong> -<p><br>(or whatever initialization script your system uses). -<p><br>If running the server as a daemon at startup, this file will need to +<p><strong>/etc/rc</strong> +<p>(or whatever initialization script your system uses). +<p>If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the section <a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below. -<p><br><strong>/etc/services</strong> -<p><br>If running the server via the meta-daemon inetd, this file must +<p><strong>/etc/services</strong> +<p>If running the server via the meta-daemon inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). See the section <a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below. -<p><br><strong>/usr/local/samba/lib/smb.conf</strong> -<p><br>This is the default location of the <em>smb.conf</em> server configuration +<p><strong>/usr/local/samba/lib/smb.conf</strong> +<p>This is the default location of the <em>smb.conf</em> server configuration file. Other common places that systems install this file are <em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>. -<p><br>This file describes all the services the server is to make available +<p>This file describes all the services the server is to make available to clients. See <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> for more information. -<p><br><a name="LIMITATIONS"></a> +<p><a name="LIMITATIONS"></a> <h2>LIMITATIONS</h2> -<p><br>On some systems <strong>smbd</strong> cannot change uid back to root after a +<p>On some systems <strong>smbd</strong> cannot change uid back to root after a setuid() call. Such systems are called "trapdoor" uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in "access denied" or similar. -<p><br><a name="ENVIRONMENTVARIABLES"></a> +<p><a name="ENVIRONMENTVARIABLES"></a> <h2>ENVIRONMENT VARIABLES</h2> -<p><br><strong>PRINTER</strong> -<p><br>If no printer name is specified to printable services, most systems +<p><strong>PRINTER</strong> +<p>If no printer name is specified to printable services, most systems will use the value of this variable (or "lp" if this variable is not defined) as the name of the printer to use. This is not specific to the server, however. -<p><br><a name="INSTALLATION"></a> +<p><a name="INSTALLATION"></a> <h2>INSTALLATION</h2> -<p><br>The location of the server and its support files is a matter for +<p>The location of the server and its support files is a matter for individual system administrators. The following are thus suggestions only. -<p><br>It is recommended that the server software be installed under the +<p>It is recommended that the server software be installed under the /usr/local/samba hierarchy, in a directory readable by all, writeable only by root. The server program itself should be executable by all, as users may wish to run the server themselves (in which case it will @@ -200,93 +193,93 @@ fix has only been confirmed on old versions (pre-kernel 2.0) of Linux at the time this was written. It is possible that this hole only exists in Linux, as testing on other systems has thus far shown them to be immune. -<p><br>The server log files should be put in a directory readable and +<p>The server log files should be put in a directory readable and writeable only by root, as the log files may contain sensitive information. -<p><br>The configuration file should be placed in a directory readable and +<p>The configuration file should be placed in a directory readable and writeable only by root, as the configuration file controls security for the services offered by the server. The configuration file can be made readable by all if desired, but this is not necessary for correct operation of the server and is not recommended. A sample configuration file "smb.conf.sample" is supplied with the source to the server - this may be renamed to "smb.conf" and modified to suit your needs. -<p><br>The remaining notes will assume the following: -<p><br><ul> -<p><br><li > <strong>smbd</strong> (the server program) installed in /usr/local/samba/bin -<p><br><li > <strong>smb.conf</strong> (the configuration file) installed in /usr/local/samba/lib -<p><br><li > log files stored in /var/adm/smblogs -<p><br></ul> -<p><br>The server may be run either as a daemon by users or at startup, or it +<p>The remaining notes will assume the following: +<p><dl> +<p><li > <strong>smbd</strong> (the server program) installed in /usr/local/samba/bin +<p><li > <strong>smb.conf</strong> (the configuration file) installed in /usr/local/samba/lib +<p><li > log files stored in /var/adm/smblogs +<p></dl> +<p>The server may be run either as a daemon by users or at startup, or it may be run from a meta-daemon such as inetd upon request. If run as a daemon, the server will always be ready, so starting sessions will be faster. If run from a meta-daemon some memory will be saved and utilities such as the tcpd TCP-wrapper may be used for extra security. For serious use as file server it is recommended that <strong>smbd</strong> be run as a daemon. -<p><br>When you've decided, continue with either +<p>When you've decided, continue with either <a href="smbd.8.html#RUNNINGTHESERVERASADAEMON">RUNNING THE SERVER AS A DAEMON</a> or <a href="smbd.8.html#RUNNINGTHESERVERONREQUEST">RUNNING THE SERVER ON REQUEST</a>. -<p><br><a name="RUNNINGTHESERVERASADAEMON"></a> +<p><a name="RUNNINGTHESERVERASADAEMON"></a> <h2>RUNNING THE SERVER AS A DAEMON</h2> -<p><br>To run the server as a daemon from the command line, simply put the +<p>To run the server as a daemon from the command line, simply put the <a href="smbd.8.html#minusD"><strong>-D</strong></a> option on the command line. There is no need to place an ampersand at the end of the command line - the <a href="smbd.8.html#minusD"><strong>-D</strong></a> option causes the server to detach itself from the tty anyway. -<p><br>Any user can run the server as a daemon (execute permissions +<p>Any user can run the server as a daemon (execute permissions permitting, of course). This is useful for testing purposes, and may even be useful as a temporary substitute for something like ftp. When run this way, however, the server will only have the privileges of the user who ran it. -<p><br>To ensure that the server is run as a daemon whenever the machine is +<p>To ensure that the server is run as a daemon whenever the machine is started, and to ensure that it runs as root so that it can serve multiple clients, you will need to modify the system startup files. Wherever appropriate (for example, in /etc/rc), insert the following line, substituting port number, log file location, configuration file location and debug level as desired: -<p><br><code>/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf</code> -<p><br>(The above should appear in your initialization script as a single line. +<p><code>/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf</code> +<p>(The above should appear in your initialization script as a single line. Depending on your terminal characteristics, it may not appear that way in this man page. If the above appears as more than one line, please treat any newlines or indentation as a single space or TAB character.) -<p><br>If the options used at compile time are appropriate for your system, +<p>If the options used at compile time are appropriate for your system, all parameters except <a href="smbd.8.html#minusD"><strong>-D</strong></a> may be omitted. See the section <a href="smbd.8.html#OPTIONS">OPTIONS</a> above. -<p><br><a name="RUNNINGTHESERVERONREQUEST"></a> +<p><a name="RUNNINGTHESERVERONREQUEST"></a> <h2>RUNNING THE SERVER ON REQUEST</h2> -<p><br>If your system uses a meta-daemon such as <strong>inetd</strong>, you can arrange to +<p>If your system uses a meta-daemon such as <strong>inetd</strong>, you can arrange to have the smbd server started whenever a process attempts to connect to it. This requires several changes to the startup files on the host machine. If you are experimenting as an ordinary user rather than as root, you will need the assistance of your system administrator to modify the system files. -<p><br>You will probably want to set up the NetBIOS name server <a href="nmbd.8.html"><strong>nmbd</strong></a> at +<p>You will probably want to set up the NetBIOS name server <a href="nmbd.8.html"><strong>nmbd</strong></a> at the same time as <strong>smbd</strong>. To do this refer to the man page for <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>. -<p><br>First, ensure that a port is configured in the file <code>/etc/services</code>. The +<p>First, ensure that a port is configured in the file <code>/etc/services</code>. The well-known port 139 should be used if possible, though any port may be used. -<p><br>Ensure that a line similar to the following is in <code>/etc/services</code>: -<p><br><code>netbios-ssn 139/tcp</code> -<p><br>Note for NIS/YP users - you may need to rebuild the NIS service maps +<p>Ensure that a line similar to the following is in <code>/etc/services</code>: +<p><code>netbios-ssn 139/tcp</code> +<p>Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local <code>/etc/services file</code>. -<p><br>Next, put a suitable line in the file <code>/etc/inetd.conf</code> (in the unlikely +<p>Next, put a suitable line in the file <code>/etc/inetd.conf</code> (in the unlikely event that you are using a meta-daemon other than inetd, you are on your own). Note that the first item in this line matches the service name in <code>/etc/services</code>. Substitute appropriate values for your system in this line (see <strong>inetd (8)</strong>): -<p><br><code>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -d1 -l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf</code> -<p><br>(The above should appear in <code>/etc/inetd.conf</code> as a single +<p><code>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -d1 -l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf</code> +<p>(The above should appear in <code>/etc/inetd.conf</code> as a single line. Depending on your terminal characteristics, it may not appear that way in this man page. If the above appears as more than one line, please treat any newlines or indentation as a single space or TAB character.) -<p><br>Note that there is no need to specify a port number here, even if you +<p>Note that there is no need to specify a port number here, even if you are using a non-standard port number. -<p><br>Lastly, edit the configuration file to provide suitable services. To +<p>Lastly, edit the configuration file to provide suitable services. To start with, the following two services should be all you need: -<p><br><pre> +<p><pre> [homes] @@ -301,85 +294,85 @@ start with, the following two services should be all you need: </pre> -<p><br>This will allow you to connect to your home directory and print to any +<p>This will allow you to connect to your home directory and print to any printer supported by the host (user privileges permitting). -<p><br><a name="TESTINGTHEINSTALLATION"></a> +<p><a name="TESTINGTHEINSTALLATION"></a> <h2>TESTING THE INSTALLATION</h2> -<p><br>If running the server as a daemon, execute it before proceeding. If +<p>If running the server as a daemon, execute it before proceeding. If using a meta-daemon, either restart the system or kill and restart the meta-daemon. Some versions of inetd will reread their configuration tables if they receive a HUP signal. -<p><br>If your machine's name is "fred" and your name is "mary", you should +<p>If your machine's name is "fred" and your name is "mary", you should now be able to connect to the service <code>\\fred\mary</code>. -<p><br>To properly test and experiment with the server, we recommend using +<p>To properly test and experiment with the server, we recommend using the smbclient program (see <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>) and also going through the steps outlined in the file <em>DIAGNOSIS.txt</em> in the <em>docs/</em> directory of your Samba installation. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="DIAGNOSTICS"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>Most diagnostics issued by the server are logged in a specified log +<p>Most diagnostics issued by the server are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line. -<p><br>The number and nature of diagnostics available depends on the debug +<p>The number and nature of diagnostics available depends on the debug level used by the server. If you have problems, set the debug level to 3 and peruse the log files. -<p><br>Most messages are reasonably self-explanatory. Unfortunately, at the time +<p>Most messages are reasonably self-explanatory. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing. -<p><br><a name="SIGNALS"></a> +<p><a name="SIGNALS"></a> <h2>SIGNALS</h2> -<p><br>Sending the smbd a SIGHUP will cause it to re-load its smb.conf +<p>Sending the smbd a SIGHUP will cause it to re-load its smb.conf configuration file within a short period of time. -<p><br>To shut down a users smbd process it is recommended that SIGKILL (-9) +<p>To shut down a users smbd process it is recommended that SIGKILL (-9) <em>NOT</em> be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate an smbd is to send it a SIGTERM (-15) signal and wait for it to die on its own. -<p><br>The debug log level of smbd may be raised +<p>The debug log level of smbd may be raised by sending it a SIGUSR1 <code>(kill -USR1 <smbd-pid>)</code> and lowered by sending it a SIGUSR2 <code>(kill -USR2 <smbd-pid>)</code>. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level. -<p><br>Note that as the signal handlers send a debug write, they are not +<p>Note that as the signal handlers send a debug write, they are not re-entrant in smbd. This you should wait until smbd is in a state of waiting for an incoming smb before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance. -<p><br><a name="SEEALSO"></a> +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>hosts_access (5)</strong>, <strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, +<p><strong>hosts_access (5)</strong>, <strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>, <a href="testprns.1.html"><strong>testprns (1)</strong></a>, and the Internet RFC's <strong>rfc1001.txt</strong>, <strong>rfc1002.txt</strong>. In addition the CIFS (formerly SMB) specification is available as a link from the Web page : <a href="http://samba.org/cifs/">http://samba.org/cifs/</a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> </html> diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 9ff258afad0..29690227909 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -3,9 +3,10 @@ + <html><head><title>smbpasswd (5)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,47 +16,46 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbpasswd - The Samba encrypted password file -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br>smbpasswd is the <strong>Samba</strong> encrypted password file. -<p><br><a name="DESCRIPTION"></a> +<p>smbpasswd is the <strong>Samba</strong> encrypted password file. +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This file is part of the <strong>Samba</strong> suite. -<p><br>smbpasswd is the <strong>Samba</strong> encrypted password file. It contains +<p>This file is part of the <strong>Samba</strong> suite. +<p>smbpasswd is the <strong>Samba</strong> encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past. -<p><br><a name="FILEFORMAT"></a> +<p><a name="FILEFORMAT"></a> <h2>FILE FORMAT</h2> -<p><br>The format of the smbpasswd file used by Samba 2.0 is very similar to +<p>The format of the smbpasswd file used by Samba 2.0 is very similar to the familiar Unix <strong>passwd (5)</strong> file. It is an ASCII file containing one line for each user. Each field within each line is separated from the next by a colon. Any entry beginning with # is ignored. The smbpasswd file contains the following information for each user: -<p><br><ul> -<p><br><a name="name"></a> -<li><strong><strong>name</strong></strong> <br> <br> -<p><br>This is the user name. It must be a name that already exists +<p><dl> +<p><a name="name"></a> +<p></p><dt><strong><strong>name</strong></strong><dd> <br> <br> +<p>This is the user name. It must be a name that already exists in the standard UNIX passwd file. -<p><br><a name="uid"></a> -<li><strong><strong>uid</strong></strong> <br> <br> -<p><br>This is the UNIX uid. It must match the uid field for the same +<p><a name="uid"></a> +<p></p><dt><strong><strong>uid</strong></strong><dd> <br> <br> +<p>This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this <strong>smbpasswd</strong> file entry as being valid for a user. -<p><br><a name="LanmanPasswordHash"></a> -<li><strong><strong>Lanman Password Hash</strong></strong> <br> <br> -<p><br>This is the <em>LANMAN</em> hash of the users password, encoded as 32 hex +<p><a name="LanmanPasswordHash"></a> +<p></p><dt><strong><strong>Lanman Password Hash</strong></strong><dd> <br> <br> +<p>This is the <em>LANMAN</em> hash of the users password, encoded as 32 hex digits. The <em>LANMAN</em> hash is created by DES encrypting a well known string with the users password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash @@ -67,7 +67,7 @@ smbpasswd file contains the following information for each user: is equal to 32 <code>'X'</code> characters then the users account is marked as <em>disabled</em> and the user will not be able to log onto the Samba server. -<p><br><em>WARNING !!</em>. Note that, due to the challenge-response nature of the +<p><em>WARNING !!</em>. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as <em>"plain text equivalent"</em> @@ -76,19 +76,19 @@ smbpasswd file contains the following information for each user: directory with read and traverse access only to the root user and the <strong>smbpasswd</strong> file itself must be set to be read/write only by root, with no other access. -<p><br><a name="NTPasswordHash"></a> -<li><strong><strong>NT Password Hash</strong></strong> <br> <br> -<p><br>This is the <em>Windows NT</em> hash of the users password, encoded as 32 +<p><a name="NTPasswordHash"></a> +<p></p><dt><strong><strong>NT Password Hash</strong></strong><dd> <br> <br> +<p>This is the <em>Windows NT</em> hash of the users password, encoded as 32 hex digits. The <em>Windows NT</em> hash is created by taking the users password as represented in 16-bit, little-endian UNICODE and then applying the <em>MD4</em> (internet rfc1321) hashing algorithm to it. -<p><br>This password hash is considered more secure than the <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman +<p>This password hash is considered more secure than the <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman Password Hash</strong></a> as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is not <em>"salted"</em> as the UNIX password is). -<p><br><em>WARNING !!</em>. Note that, due to the challenge-response nature of the +<p><em>WARNING !!</em>. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as <em>"plain text equivalent"</em> @@ -97,48 +97,48 @@ smbpasswd file contains the following information for each user: directory with read and traverse access only to the root user and the <strong>smbpasswd</strong> file itself must be set to be read/write only by root, with no other access. -<p><br><a name="AccountFlags"></a> -<li><strong><strong>Account Flags</strong></strong> <br> <br> -<p><br>This section contains flags that describe the attributes of the users +<p><a name="AccountFlags"></a> +<p></p><dt><strong><strong>Account Flags</strong></strong><dd> <br> <br> +<p>This section contains flags that describe the attributes of the users account. In the <strong>Samba2.0</strong> release this field is bracketed by <code>'['</code> and <code>']'</code> characters and is always 13 characters in length (including the <code>'['</code> and <code>']'</code> characters). The contents of this field may be any of the characters. -<p><br><ul> -<p><br><a name="capU"></a> +<p><dl> +<p><a name="capU"></a> <li > <strong>'U'</strong> This means this is a <em>"User"</em> account, i.e. an ordinary user. Only <strong>User</strong> and <a href="smbpasswd.5.html#capW"><strong>Workstation Trust</strong></a> accounts are currently supported in the <strong>smbpasswd</strong> file. -<p><br><a name="capN"></a> +<p><a name="capN"></a> <li > <strong>'N'</strong> This means the account has <em>no</em> password (the passwords in the fields <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman Password Hash</strong></a> and <a href="smbpasswd.5.html#NTPasswordHash"><strong>NT Password Hash</strong></a> are ignored). Note that this will only allow users to log on with no password if the <a href="smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a> parameter is set in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> config file. -<p><br><a name="capD"></a> +<p><a name="capD"></a> <li > <strong>'D'</strong> This means the account is disabled and no SMB/CIFS logins will be allowed for this user. -<p><br><a name="capW"></a> +<p><a name="capW"></a> <li > <strong>'W'</strong> This means this account is a <em>"Workstation Trust"</em> account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC. -<p><br></ul> -<p><br>Other flags may be added as the code is extended in future. The rest of +<p></dl> +<p>Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. -<p><br><a name="LastChangeTime"></a> -<li><strong><strong>Last Change Time</strong></strong> <br> <br> -<p><br>This field consists of the time the account was last modified. It consists of +<p><a name="LastChangeTime"></a> +<p></p><dt><strong><strong>Last Change Time</strong></strong><dd> <br> <br> +<p>This field consists of the time the account was last modified. It consists of the characters <code>LCT-</code> (standing for <em>"Last Change Time"</em>) followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made. -<p><br><li><strong><strong>Following fields</strong></strong> <br> <br> -<p><br>All other colon separated fields are ignored at this time. -<p><br></ul> -<p><br><a name="NOTES"></a> +<p><p></p><dt><strong><strong>Following fields</strong></strong><dd> <br> <br> +<p>All other colon separated fields are ignored at this time. +<p></dl> +<p><a name="NOTES"></a> <h2>NOTES</h2> -<p><br>In previous versions of Samba (notably the 1.9.18 series) this file +<p>In previous versions of Samba (notably the 1.9.18 series) this file did not contain the <a href="smbpasswd.5.html#AccountFlags"><strong>Account Flags</strong></a> or <a href="smbpasswd.5.html#LastChangeTime"><strong>Last Change Time</strong></a> fields. The Samba 2.0 code will read and write these older password files but will not be able to @@ -147,11 +147,11 @@ modify the old entries to add the new fields. New entries added with in the added accounts however. Thus an older <strong>smbpasswd</strong> file used with Samba 2.0 may end up with some accounts containing the new fields and some not. -<p><br>In order to convert from an old-style <strong>smbpasswd</strong> file to a new +<p>In order to convert from an old-style <strong>smbpasswd</strong> file to a new style, run the script <strong>convert_smbpasswd</strong>, installed in the Samba <code>bin/</code> directory (the same place that the <a href="smbd.8.html"><strong>smbd</strong></a> and <a href="nmbd.8.html"><strong>nmbd</strong></a> binaries are installed) as follows: -<p><br><pre> +<p><pre> cat old_smbpasswd_file | convert_smbpasswd > new_smbpasswd_file @@ -159,36 +159,36 @@ and <a href="nmbd.8.html"><strong>nmbd</strong></a> binaries are installed) as f </pre> -<p><br>The <strong>convert_smbpasswd</strong> script reads from stdin and writes to stdout +<p>The <strong>convert_smbpasswd</strong> script reads from stdin and writes to stdout so as not to overwrite any files by accident. -<p><br>Once this script has been run, check the contents of the new smbpasswd +<p>Once this script has been run, check the contents of the new smbpasswd file to ensure that it has not been damaged by the conversion script (which uses <strong>awk</strong>), and then replace the <code><old smbpasswd file></code> with the <code><new smbpasswd file></code>. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba +<p><a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba (7)</strong></a>, and the Internet RFC1321 for details on the MD4 algorithm. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy -Allison, <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +Allison, <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 2b2f4660646..a0f4577b08c 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -3,9 +3,10 @@ + <html><head><title>smbpasswd (8)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,25 +16,24 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbpasswd - change a users SMB password -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbpasswd</strong> [<a href="smbpasswd.8.html#minusa">-a</a>] [<a href="smbpasswd.8.html#minusd">-d</a>] [<a href="smbpasswd.8.html#minuse">-e</a>] [<a href="smbpasswd.8.html#minusD">-D debug level</a>] [<a href="smbpasswd.8.html#minusn">-n</a>] [<a href="smbpasswd.8.html#minusr">-r remote_machine</a>] [<a href="smbpasswd.8.html#minusR">-R name resolve order</a>] [<a href="smbpasswd.8.html#minusm">-m</a>] [<a href="smbpasswd.8.html#minusj">-j DOMAIN</a>] [<a href="smbpasswd.8.html#minusU">-U username</a>] [<a href="smbpasswd.8.html#minush">-h</a>] [<a href="smbpasswd.8.html#minuss">-s</a>] <a href="smbpasswd.8.html#username">username</a> -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbpasswd</strong> [<a href="smbpasswd.8.html#minusa">-a</a>] [<a href="smbpasswd.8.html#minusx">-x</a>] [<a href="smbpasswd.8.html#minusd">-d</a>] [<a href="smbpasswd.8.html#minuse">-e</a>] [<a href="smbpasswd.8.html#minusD">-D debug level</a>] [<a href="smbpasswd.8.html#minusn">-n</a>] [<a href="smbpasswd.8.html#minusr">-r remote_machine</a>] [<a href="smbpasswd.8.html#minusR">-R name resolve order</a>] [<a href="smbpasswd.8.html#minusm">-m</a>] [<a href="smbpasswd.8.html#minusj">-j DOMAIN</a>] [<a href="smbpasswd.8.html#minusU">-U username</a>] [<a href="smbpasswd.8.html#minush">-h</a>] [<a href="smbpasswd.8.html#minuss">-s</a>] <a href="smbpasswd.8.html#username">username</a> +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br>The <strong>smbpasswd</strong> program has several different functions, depending +<p>This program is part of the <strong>Samba</strong> suite. +<p>The <strong>smbpasswd</strong> program has several different functions, depending on whether it is run by the <em>root</em> user or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords. -<p><br>By default (when run with no arguments) it will attempt to change the +<p>By default (when run with no arguments) it will attempt to change the current users SMB password on the local machine. This is similar to the way the <strong>passwd (1)</strong> program works. <strong>smbpasswd</strong> differs from how the <strong>passwd</strong> program works however in that it is not <em>setuid root</em> @@ -42,29 +42,29 @@ running <a href="smbd.8.html"><strong>smbd</strong></a>. As a consequence in ord to succeed the <a href="smbd.8.html"><strong>smbd</strong></a> daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in the <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> file. -<p><br>When run by an ordinary user with no options. <strong>smbpasswd</strong> will +<p>When run by an ordinary user with no options. <strong>smbpasswd</strong> will prompt them for their old smb password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank smb password (specified by the string "NO PASSWORD" in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file) then just press the <Enter> key when asked for your old password. -<p><br><strong>smbpasswd</strong> can also be used by a normal user to change their SMB +<p><strong>smbpasswd</strong> can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers. See the <a href="smbpasswd.8.html#minusr">(<strong>-r</strong>)</a> and <a href="smbpasswd.8.html#minusU"><strong>-U</strong></a> options below. -<p><br>When run by root, <strong>smbpasswd</strong> allows new users to be added and +<p>When run by root, <strong>smbpasswd</strong> allows new users to be added and deleted in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file, as well as allows changes to the attributes of the user in this file to be made. When run by root, <strong>smbpasswd</strong> accesses the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file directly, thus enabling changes to be made even if <a href="smbd.8.html"><strong>smbd</strong></a> is not running. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minusa"></a> -<li><strong><strong>-a</strong></strong> This option specifies that the username following should +<p><dl> +<p><a name="minusa"></a> +<p></p><dt><strong><strong>-a</strong></strong><dd> This option specifies that the username following should be added to the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file, with the new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the @@ -72,60 +72,65 @@ option is ignored if the username following already exists in the regular change password command. Note that the user to be added <strong>must</strong> already exist in the system password file (usually /etc/passwd) else the request to add the user will fail. -<p><br>This option is only available when running <strong>smbpasswd</strong> as +<p>This option is only available when running <strong>smbpasswd</strong> as +root. +<p><a name="minusx"></a> +<p></p><dt><strong><strong>-x</strong></strong><dd> This option specifies that the username following should +be deleted from the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. +<p>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minusd"></a> -<li><strong><strong>-d</strong></strong> This option specifies that the username following should be +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d</strong></strong><dd> This option specifies that the username following should be <em>disabled</em> in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. This is done by writing a <em>'D'</em> flag into the account control space in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. Once this is done all attempts to authenticate via SMB using this username will fail. -<p><br>If the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is in the 'old' +<p>If the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is in the 'old' format (pre-Samba 2.0 format) there is no space in the users password entry to write this information and so the user is disabled by writing 'X' characters into the password space in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. See <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> for details on the 'old' and new password file formats. -<p><br>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minuse"></a> -<li><strong><strong>-e</strong></strong> This option specifies that the username following should be +<p>This option is only available when running <strong>smbpasswd</strong> as root. +<p><a name="minuse"></a> +<p></p><dt><strong><strong>-e</strong></strong><dd> This option specifies that the username following should be <em>enabled</em> in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file, if the account was previously disabled. If the account was not disabled this option has no effect. Once the account is enabled then the user will be able to authenticate via SMB once again. -<p><br>If the smbpasswd file is in the 'old' format then <strong>smbpasswd</strong> will +<p>If the smbpasswd file is in the 'old' format then <strong>smbpasswd</strong> will prompt for a new password for this user, otherwise the account will be enabled by removing the <em>'D'</em> flag from account control space in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. See <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> for details on the 'old' and new password file formats. -<p><br>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minusD"></a> -<li><strong><strong>-D debuglevel</strong></strong> debuglevel is an integer from 0 +<p>This option is only available when running <strong>smbpasswd</strong> as root. +<p><a name="minusD"></a> +<p></p><dt><strong><strong>-D debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10. The default value if this parameter is not specified is zero. -<p><br>The higher this value, the more detail will be logged to the log files +<p>The higher this value, the more detail will be logged to the log files about the activities of smbpasswd. At level 0, only critical errors and serious warnings will be logged. -<p><br>Levels above 1 will generate considerable amounts of log data, and +<p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. -<p><br><a name="minusn"></a> -<li><strong><strong>-n</strong></strong> This option specifies that the username following should +<p><a name="minusn"></a> +<p></p><dt><strong><strong>-n</strong></strong><dd> This option specifies that the username following should have their password set to null (i.e. a blank password) in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. -<p><br>Note that to allow users to logon to a Samba server once the password +<p>Note that to allow users to logon to a Samba server once the password has been set to "NO PASSWORD" in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file the administrator must set the following parameter in the [global] section of the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file : -<p><br><a href="smb.conf.5.html#nullpasswords">null passwords = true</a> -<p><br>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minusr"></a> -<li><strong><strong>-r remote machine name</strong></strong> This option allows a +<p><a href="smb.conf.5.html#nullpasswords">null passwords = true</a> +<p>This option is only available when running <strong>smbpasswd</strong> as root. +<p><a name="minusr"></a> +<p></p><dt><strong><strong>-r remote machine name</strong></strong><dd> This option allows a user to specify what machine they wish to change their password on. Without this parameter <strong>smbpasswd</strong> defaults to the local host. The <em>"remote machine name"</em> is the NetBIOS name of the @@ -134,71 +139,71 @@ is resolved into an IP address using the standard name resolution mechanism in all programs of the <a href="samba.7.html"><strong>Samba</strong></a> suite. See the <a href="smbpasswd.8.html#minusR"><strong>-R name resolve order</strong></a> parameter for details on changing this resolving mechanism. -<p><br>The username whose password is changed is that of the current UNIX +<p>The username whose password is changed is that of the current UNIX logged on user. See the <a href="smbpasswd.8.html#minusU"><strong>-U username</strong></a> parameter for details on changing the password for a different username. -<p><br>Note that if changing a Windows NT Domain password the remote machine +<p>Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read-only copy of the user account database and will not allow the password change). -<p><br><em>Note</em> that Windows 95/98 do not have a real password database +<p><em>Note</em> that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target. -<p><br><a name="minusR"></a> -<li><strong><strong>-R name resolve order</strong></strong> This option allows the user of +<p><a name="minusR"></a> +<p></p><dt><strong><strong>-R name resolve order</strong></strong><dd> This option allows the user of smbclient to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to. -<p><br>The options are :<a href="smbpasswd.8.html#lmhosts">"lmhosts"</a>, <a href="smbpasswd.8.html#host">"host"</a>, +<p>The options are :<a href="smbpasswd.8.html#lmhosts">"lmhosts"</a>, <a href="smbpasswd.8.html#host">"host"</a>, <a href="smbpasswd.8.html#wins">"wins"</a> and <a href="smbpasswd.8.html#bcast">"bcast"</a>. They cause names to be resolved as follows : -<p><br><ul> -<p><br><a name="lmhosts"></a> +<p><dl> +<p><a name="lmhosts"></a> <li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. -<p><br><a name="host"></a> +<p><a name="host"></a> <li > <strong>host</strong> : Do a standard host name to IP address resolution, using the system /etc/hosts, NIS, or DNS lookups. This method of name resolution is operating system dependent. For instance on IRIX or Solaris, this may be controlled by the <em>/etc/nsswitch.conf</em> file). -<p><br><a name="wins"></a> +<p><a name="wins"></a> <li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf file</strong></a>. If no WINS server has been specified this method will be ignored. -<p><br><a name="bcast"></a> +<p><a name="bcast"></a> <li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter in the smb.conf file. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet. -<p><br></ul> -<p><br>If this parameter is not set then the name resolve order defined +<p></dl> +<p>If this parameter is not set then the name resolve order defined in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file parameter <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> will be used. -<p><br>The default order is lmhosts, host, wins, bcast and without this +<p>The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file the name resolution methods will be attempted in this order. -<p><br><a name="minusm"></a> -<li><strong><strong>-m</strong></strong> This option tells <strong>smbpasswd</strong> that the account being +<p><a name="minusm"></a> +<p></p><dt><strong><strong>-m</strong></strong><dd> This option tells <strong>smbpasswd</strong> that the account being changed is a <em>MACHINE</em> account. Currently this is used when Samba is being used as an NT Primary Domain Controller. PDC support is not a supported feature in Samba2.0 but will become supported in a later release. If you wish to know more about using Samba as an NT PDC then please subscribe to the mailing list <a href="mailto:samba-ntdom@samba.org"><em>samba-ntdom@samba.org</em></a>. -<p><br>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minusj"></a> -<li><strong><strong>-j DOMAIN</strong></strong> This option is used to add a Samba server into a +<p>This option is only available when running <strong>smbpasswd</strong> as root. +<p><a name="minusj"></a> +<p></p><dt><strong><strong>-j DOMAIN</strong></strong><dd> This option is used to add a Samba server into a Windows NT Domain, as a Domain member capable of authenticating user accounts to any Domain Controller in the same way as a Windows NT Server. See the <a href="smb.conf.5.html#security"><strong>security=domain</strong></a> option in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page. -<p><br>In order to be used in this way, the Administrator for the Windows +<p>In order to be used in this way, the Administrator for the Windows NT Domain must have used the program <em>"Server Manager for Domains"</em> to add the <a href="smb.conf.5.html#netbiosname">primary NetBIOS name</a> of the Samba server as a member of the Domain. -<p><br>After this has been done, to join the Domain invoke <strong>smbpasswd</strong> with +<p>After this has been done, to join the Domain invoke <strong>smbpasswd</strong> with this parameter. <strong>smbpasswd</strong> will then look up the Primary Domain Controller for the Domain (found in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file in the parameter @@ -208,39 +213,39 @@ communication. This password is then stored by <strong>smbpasswd</strong> in a file, read only by root, called <code><Domain>.<Machine>.mac</code> where <code><Domain></code> is the name of the Domain we are joining and <code><Machine></code> is the primary NetBIOS name of the machine we are running on. -<p><br>Once this operation has been performed the +<p>Once this operation has been performed the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file may be updated to set the <a href="smb.conf.5.html#security"><strong>security=domain</strong></a> option and all future logins to the Samba server will be authenticated to the Windows NT PDC. -<p><br>Note that even though the authentication is being done to the PDC all +<p>Note that even though the authentication is being done to the PDC all users accessing the Samba server must still have a valid UNIX account on that machine. -<p><br>This option is only available when running <strong>smbpasswd</strong> as root. -<p><br><a name="minusU"></a> -<li><strong><strong>-U username</strong></strong> This option may only be used in +<p>This option is only available when running <strong>smbpasswd</strong> as root. +<p><a name="minusU"></a> +<p></p><dt><strong><strong>-U username</strong></strong><dd> This option may only be used in conjunction with the <a href="smbpasswd.8.html#minusr"><strong>-r</strong></a> option. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed. It is present to allow users who have different user names on different systems to change these passwords. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> This option prints the help string for <strong>smbpasswd</strong>, +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> This option prints the help string for <strong>smbpasswd</strong>, selecting the correct one for running as root or as an ordinary user. -<p><br><a name="minuss"></a> -<li><strong><strong>-s</strong></strong> This option causes <strong>smbpasswd</strong> to be silent (i.e. not +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s</strong></strong><dd> This option causes <strong>smbpasswd</strong> to be silent (i.e. not issue prompts) and to read it's old and new passwords from standard input, rather than from <code>/dev/tty</code> (like the <strong>passwd (1)</strong> program does). This option is to aid people writing scripts to drive <strong>smbpasswd</strong> -<p><br><a name="username"></a> -<li><strong><strong>username</strong></strong> This specifies the username for all of the <em>root +<p><a name="username"></a> +<p></p><dt><strong><strong>username</strong></strong><dd> This specifies the username for all of the <em>root only</em> options to operate on. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. -<p><br><a name="NOTES"></a> +<p><a name="NOTES"></a> <h2>NOTES</h2> -<p><br>Since <strong>smbpasswd</strong> works in client-server mode communicating with a +<p>Since <strong>smbpasswd</strong> works in client-server mode communicating with a local <a href="smbd.8.html"><strong>smbd</strong></a> for a non-root user then the <strong>smbd</strong> daemon must be running for this to work. A common problem is to add a restriction to the hosts that may access the <strong>smbd</strong> running on the @@ -249,27 +254,27 @@ hosts"</strong></a> or <a href="smb.conf.5.html#denyhosts"><strong>"deny hosts"</strong></a> entry in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file and neglecting to allow <em>"localhost"</em> access to the <strong>smbd</strong>. -<p><br>In addition, the <strong>smbpasswd</strong> command is only useful if <strong>Samba</strong> has +<p>In addition, the <strong>smbpasswd</strong> command is only useful if <strong>Samba</strong> has been set up to use encrypted passwords. See the file <strong>ENCRYPTION.txt</strong> in the docs directory for details on how to do this. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="AUTHOR"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbrun.1.html b/docs/htmldocs/smbrun.1.html index ccfdd6ff2ab..16133fcb220 100644 --- a/docs/htmldocs/smbrun.1.html +++ b/docs/htmldocs/smbrun.1.html @@ -3,9 +3,10 @@ + <html><head><title>smbrun (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,71 +16,70 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbrun - interface program between smbd and external programs -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbrun</strong> <a href="smbrun.1.html#shellcommand">shell-command</a> -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbrun</strong> <a href="smbrun.1.html#shellcommand">shell-command</a> +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>smbrun</strong> is a very small 'glue' program, which runs shell commands +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>smbrun</strong> is a very small 'glue' program, which runs shell commands for the <a href="smbd.8.html"><strong>smbd</strong></a> daemon <a href="smbd.8.html"><strong>smbd (8)</strong></a>. -<p><br>It first changes to the highest effective user and group ID that it +<p>It first changes to the highest effective user and group ID that it can, then runs the command line provided using the system() call. This program is necessary to allow some operating systems to run external programs as non-root. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="shellcommand"></a> -<li><strong><strong>shell-command</strong></strong> The shell command to execute. The command +<p><dl> +<p><a name="shellcommand"></a> +<p></p><dt><strong><strong>shell-command</strong></strong><dd> The shell command to execute. The command should have a fully-qualified path. -<p><br></ul> -<p><br><a name="ENVIRONMENTVARIABLES"></a> +<p></dl> +<p><a name="ENVIRONMENTVARIABLES"></a> <h2>ENVIRONMENT VARIABLES</h2> -<p><br>The <em>PATH</em> variable set for the environment in which <strong>smbrun</strong> is +<p>The <em>PATH</em> variable set for the environment in which <strong>smbrun</strong> is executed will affect what executables are located and executed if a fully-qualified path is not given in the command. -<p><br><a name="DIAGNOSTICS"></a> +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>If <strong>smbrun</strong> cannot be located or cannot be executed by +<p>If <strong>smbrun</strong> cannot be located or cannot be executed by <a href="smbd.8.html"><strong>smbd</strong></a> then appropriate messages will be found in the <a href="smbd.8.html"><strong>smbd</strong></a> logs. Other diagnostics are dependent on the shell-command being run. It is advisable for your shell commands to issue suitable diagnostics to aid trouble-shooting. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index 1cc65e81587..cdce69cdbf8 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -3,9 +3,10 @@ + <html><head><title>smbstatus (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,71 +16,70 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbstatus - report on current Samba connections -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbstatus</strong> [<a href="smbstatus.1.html#minusP">-P</a>] [<a href="smbstatus.1.html#minusb">-b</a>] [<a href="smbstatus.1.html#minusd">-d</a>] [<a href="smbstatus.1.html#minusL">-L</a>] [<a href="smbstatus.1.html#minusp">-p</a>] [<a href="smbstatus.1.html#minusS">-S</a>] [<a href="smbstatus.1.html#minuss">-s configuration file</a>] [<a href="smbstatus.1.html#minusu">-u username</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbstatus</strong> [<a href="smbstatus.1.html#minusP">-P</a>] [<a href="smbstatus.1.html#minusb">-b</a>] [<a href="smbstatus.1.html#minusd">-d</a>] [<a href="smbstatus.1.html#minusL">-L</a>] [<a href="smbstatus.1.html#minusp">-p</a>] [<a href="smbstatus.1.html#minusS">-S</a>] [<a href="smbstatus.1.html#minuss">-s configuration file</a>] [<a href="smbstatus.1.html#minusu">-u username</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>smbstatus</strong> is a very simple program to list the current Samba +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>smbstatus</strong> is a very simple program to list the current Samba connections. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minusP"></a> -<li><strong><strong>-P</strong></strong> If samba has been compiled with the profiling option, +<p><dl> +<p><a name="minusP"></a> +<p></p><dt><strong><strong>-P</strong></strong><dd> If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area. -<p><br><a name="minusb"></a> -<li><strong><strong>-b</strong></strong> gives brief output. -<p><br><a name="minusd"></a> -<li><strong><strong>-d</strong></strong> gives verbose output. -<p><br><a name="minusL"></a> -<li><strong><strong>-L</strong></strong> causes smbstatus to only list locks. -<p><br><a name="minusp"></a> -<li><strong><strong>-p</strong></strong> print a list of <a href="smbd.8.html"><strong>smbd</strong></a> +<p><a name="minusb"></a> +<p></p><dt><strong><strong>-b</strong></strong><dd> gives brief output. +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d</strong></strong><dd> gives verbose output. +<p><a name="minusL"></a> +<p></p><dt><strong><strong>-L</strong></strong><dd> causes smbstatus to only list locks. +<p><a name="minusp"></a> +<p></p><dt><strong><strong>-p</strong></strong><dd> print a list of <a href="smbd.8.html"><strong>smbd</strong></a> processes and exit. Useful for scripting. -<p><br><a name="minusS"></a> -<li><strong><strong>-S</strong></strong> causes smbstatus to only list shares. -<p><br><a name="minuss"></a> -<li><strong><strong>-s configuration file</strong></strong> The default configuration file name is +<p><a name="minusS"></a> +<p></p><dt><strong><strong>-S</strong></strong><dd> causes smbstatus to only list shares. +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s configuration file</strong></strong><dd> The default configuration file name is determined at compile time. The file specified contains the configuration details required by the server. See <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> for more information. -<p><br><a name="minusu"></a> -<li><strong><strong>-u username</strong></strong> selects information relevant to <em>username</em> +<p><a name="minusu"></a> +<p></p><dt><strong><strong>-u username</strong></strong><dd> selects information relevant to <em>username</em> only. -<p><br></ul> -<p><br><a name="VERSION"></a> +<p></dl> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index ef416f2e6c3..68aab355ed5 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -3,9 +3,10 @@ + <html><head><title>smbtar (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,106 +16,105 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> smbtar - shell script for backing up SMB/CIFS shares directly to UNIX tape drives -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>smbtar</strong> <a href="smbtar.1.html#minuss">-s server</a> [<a href="smbtar.1.html#minusp">-p password</a>] [<a href="smbtar.1.html#minusx">-x service</a>] [<a href="smbtar.1.html#minusX">-X</a>] [<a href="smbtar.1.html#minusd">-d directory</a>] [<a href="smbtar.1.html#minusu">-u user</a>] [<a href="smbtar.1.html#minust">-t tape</a>] [<a href="smbtar.1.html#minusb">-b blocksize</a>] [<a href="smbtar.1.html#minusN">-N filename</a>] [<a href="smbtar.1.html#minusi">-i</a>] [<a href="smbtar.1.html#minusr">-r</a>] [<a href="smbtar.1.html#minusl">-l log level</a>] [<a href="smbtar.1.html#minusv">-v</a>] filenames -<p><br><a name="DESCRIPTION"></a> +<p><strong>smbtar</strong> <a href="smbtar.1.html#minuss">-s server</a> [<a href="smbtar.1.html#minusp">-p password</a>] [<a href="smbtar.1.html#minusx">-x service</a>] [<a href="smbtar.1.html#minusX">-X</a>] [<a href="smbtar.1.html#minusd">-d directory</a>] [<a href="smbtar.1.html#minusu">-u user</a>] [<a href="smbtar.1.html#minust">-t tape</a>] [<a href="smbtar.1.html#minusb">-b blocksize</a>] [<a href="smbtar.1.html#minusN">-N filename</a>] [<a href="smbtar.1.html#minusi">-i</a>] [<a href="smbtar.1.html#minusr">-r</a>] [<a href="smbtar.1.html#minusl">-l log level</a>] [<a href="smbtar.1.html#minusv">-v</a>] filenames +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>smbtar</strong> is a very small shell script on top of +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>smbtar</strong> is a very small shell script on top of <a href="smbclient.1.html"><strong>smbclient</strong></a> which dumps SMB shares directly to tape. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minuss"></a> -<li><strong><strong>-s server</strong></strong> The SMB/CIFS server that the share resides upon. -<p><br><a name="minusx"></a> -<li><strong><strong>-x service</strong></strong> The share name on the server to connect +<p><dl> +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s server</strong></strong><dd> The SMB/CIFS server that the share resides upon. +<p><a name="minusx"></a> +<p></p><dt><strong><strong>-x service</strong></strong><dd> The share name on the server to connect to. The default is <code>backup</code>. -<p><br><a name="minusX"></a> -<li><strong><strong>-X</strong></strong> Exclude mode. Exclude filenames... from tar create or +<p><a name="minusX"></a> +<p></p><dt><strong><strong>-X</strong></strong><dd> Exclude mode. Exclude filenames... from tar create or restore. -<p><br><a name="minusd"></a> -<li><strong><strong>-d directory</strong></strong> Change to initial <em>directory</em> before restoring +<p><a name="minusd"></a> +<p></p><dt><strong><strong>-d directory</strong></strong><dd> Change to initial <em>directory</em> before restoring / backing up files. -<p><br><a name="minusv"></a> -<li><strong><strong>-v</strong></strong> Verbose mode. -<p><br><a name="minusp"></a> -<li><strong><strong>-p password</strong></strong> The password to use to access a share. Default: +<p><a name="minusv"></a> +<p></p><dt><strong><strong>-v</strong></strong><dd> Verbose mode. +<p><a name="minusp"></a> +<p></p><dt><strong><strong>-p password</strong></strong><dd> The password to use to access a share. Default: none -<p><br><a name="minusu"></a> -<li><strong><strong>-u user</strong></strong> The user id to connect as. Default: UNIX login name. -<p><br><a name="minust"></a> -<li><strong><strong>-t tape</strong></strong> Tape device. May be regular file or tape +<p><a name="minusu"></a> +<p></p><dt><strong><strong>-u user</strong></strong><dd> The user id to connect as. Default: UNIX login name. +<p><a name="minust"></a> +<p></p><dt><strong><strong>-t tape</strong></strong><dd> Tape device. May be regular file or tape device. Default: <em>TAPE</em> environmental variable; if not set, a file called <code>tar.out</code>. -<p><br><a name="minusb"></a> -<li><strong><strong>-b blocksize</strong></strong> Blocking factor. Defaults to 20. See <strong>tar (1)</strong> +<p><a name="minusb"></a> +<p></p><dt><strong><strong>-b blocksize</strong></strong><dd> Blocking factor. Defaults to 20. See <strong>tar (1)</strong> for a fuller explanation. -<p><br><a name="minusN"></a> -<li><strong><strong>-N filename</strong></strong> Backup only files newer than filename. Could be +<p><a name="minusN"></a> +<p></p><dt><strong><strong>-N filename</strong></strong><dd> Backup only files newer than filename. Could be used (for example) on a log file to implement incremental backups. -<p><br><a name="minusi"></a> -<li><strong><strong>-i</strong></strong> Incremental mode; tar files are only backed up if they +<p><a name="minusi"></a> +<p></p><dt><strong><strong>-i</strong></strong><dd> Incremental mode; tar files are only backed up if they have the archive bit set. The archive bit is reset after each file is read. -<p><br><a name="minusr"></a> -<li><strong><strong>-r</strong></strong> Restore. Files are restored to the share from the tar +<p><a name="minusr"></a> +<p></p><dt><strong><strong>-r</strong></strong><dd> Restore. Files are restored to the share from the tar file. -<p><br><a name="minusl"></a> -<li><strong><strong>-l log level</strong></strong> Log (debug) level. Corresponds to the +<p><a name="minusl"></a> +<p></p><dt><strong><strong>-l log level</strong></strong><dd> Log (debug) level. Corresponds to the <a href="smbclient.1.html#minusd"><strong>-d</strong></a> flag of <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>. -<p><br></ul> -<p><br><a name="ENVIRONMENTVARIABLES"></a> +<p></dl> +<p><a name="ENVIRONMENTVARIABLES"></a> <h2>ENVIRONMENT VARIABLES</h2> -<p><br>The TAPE variable specifies the default tape device to write to. May +<p>The TAPE variable specifies the default tape device to write to. May be overridden with the <a href="smbtar.1.html#minust"><strong>-t</strong></a> option. -<p><br><a name="BUGS"></a> +<p><a name="BUGS"></a> <h2>BUGS</h2> -<p><br>The <strong>smbtar</strong> script has different options from ordinary tar and tar +<p>The <strong>smbtar</strong> script has different options from ordinary tar and tar called from <a href="smbclient.1.html"><strong>smbclient</strong></a>. -<p><br><a name="CAVEATS"></a> +<p><a name="CAVEATS"></a> <h2>CAVEATS</h2> -<p><br>Sites that are more careful about security may not like the way the +<p>Sites that are more careful about security may not like the way the script handles PC passwords. Backup and restore work on entire shares, should work on file lists. <strong>smbtar</strong> works best with GNU tar and may not work well with other versions. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf +<p><a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> -<p><br><a name="DIAGNOSTICS"></a> +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>See the <a href="smbclient.1.html#DIAGNOSTICS"><strong>DIAGNOSTICS</strong></a> section for +<p>See the <a href="smbclient.1.html#DIAGNOSTICS"><strong>DIAGNOSTICS</strong></a> section for the <a href="smbclient.1.html"><strong>smbclient</strong></a> command. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>Ricky Poulten <a href="mailto:poultenr@logica.co.uk"><em>poultenr@logica.co.uk</em></a> wrote the tar extension and +<p>Ricky Poulten <a href="mailto:poultenr@logica.co.uk"><em>poultenr@logica.co.uk</em></a> wrote the tar extension and this man page. The <strong>smbtar</strong> script was heavily rewritten and improved by Martin Kraemer <a href="mailto:Martin.Kraemer@mch.sni.de"><em>Martin.Kraemer@mch.sni.de</em></a>. Many thanks to everyone who suggested extensions, improvements, bug fixes, @@ -122,9 +122,9 @@ etc. The man page sources were converted to YODL format (another excellent piece of Open Source software available at <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison, -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. -<p><br></body> +<p></body> </html> diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 3a29f17ab5e..12d83247fdd 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -3,9 +3,10 @@ + <html><head><title>swat (8)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,53 +16,52 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> swat - Samba Web Administration Tool -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>swat</strong> allows a Samba administrator to configure the complex +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>swat</strong> allows a Samba administrator to configure the complex <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file via a Web browser. In addition, a swat configuration page has help links to all the configurable options in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file allowing an administrator to easily look up the effects of any change. -<p><br><strong>swat</strong> is run from <strong>inetd</strong> -<p><br><a name="OPTIONS"></a> +<p><strong>swat</strong> is run from <strong>inetd</strong> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minuss"></a> -<li><strong><strong>-s smb configuration file</strong></strong> The default configuration file path is +<p><dl> +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s smb configuration file</strong></strong><dd> The default configuration file path is determined at compile time. -<p><br>The file specified contains the configuration details required by the +<p>The file specified contains the configuration details required by the <a href="smbd.8.html"><strong>smbd</strong></a> server. This is the file that <strong>swat</strong> will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See <a href="smb.conf.5.html">smb.conf (5)</a> for more information. -<p><br><a name="minusa"></a> -<li><strong><strong>-a</strong></strong> -<p><br>This option disables authentication and puts <strong>swat</strong> in demo mode. In +<p><a name="minusa"></a> +<p></p><dt><strong><strong>-a</strong></strong><dd> +<p>This option disables authentication and puts <strong>swat</strong> in demo mode. In that mode anyone will be able to modify the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. -<p><br>Do NOT enable this option on a production server. -<p><br></ul> -<p><br><a name="INSTALLATION"></a> +<p>Do NOT enable this option on a production server. +<p></dl> +<p><a name="INSTALLATION"></a> <h2>INSTALLATION</h2> -<p><br>After you compile SWAT you need to run <code>"make install"</code> to install the +<p>After you compile SWAT you need to run <code>"make install"</code> to install the swat binary and the various help files and images. A default install would put these in: -<p><br><pre> +<p><pre> /usr/local/samba/bin/swat /usr/local/samba/swat/images/* @@ -69,79 +69,79 @@ would put these in: </pre> -<p><br><a name="INETD"></a> +<p><a name="INETD"></a> <h2>INETD INSTALLATION</h2> -<p><br>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to +<p>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to enable <strong>SWAT</strong> to be launched via inetd. -<p><br>In <code>/etc/services</code> you need to add a line like this: -<p><br><code>swat 901/tcp</code> -<p><br>Note for NIS/YP users - you may need to rebuild the NIS service maps +<p>In <code>/etc/services</code> you need to add a line like this: +<p><code>swat 901/tcp</code> +<p>Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local <code>/etc/services</code> file. -<p><br>the choice of port number isn't really important except that it should +<p>the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your <strong>inetd</strong> daemon). -<p><br>In <code>/etc/inetd.conf</code> you should add a line like this: -<p><br><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code> -<p><br>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need +<p>In <code>/etc/inetd.conf</code> you should add a line like this: +<p><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code> +<p>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need to send a HUP signal to inetd. To do this use <code>"kill -1 PID"</code> where PID is the process ID of the inetd daemon. -<p><br><a name="LAUNCHING"></a> +<p><a name="LAUNCHING"></a> <h2>LAUNCHING</h2> -<p><br>To launch <strong>swat</strong> just run your favorite web browser and point it at +<p>To launch <strong>swat</strong> just run your favorite web browser and point it at <code>http://localhost:901/</code>. -<p><br><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but +<p><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire.</strong> -<p><br><h2>FILES</h2> +<p><h2>FILES</h2> -<p><br><strong>/etc/inetd.conf</strong> -<p><br>This file must contain suitable startup information for the +<p><strong>/etc/inetd.conf</strong> +<p>This file must contain suitable startup information for the meta-daemon. -<p><br><strong>/etc/services</strong> -<p><br>This file must contain a mapping of service name (e.g., swat) to +<p><strong>/etc/services</strong> +<p>This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp). -<p><br><strong>/usr/local/samba/lib/smb.conf</strong> -<p><br>This is the default location of the <em>smb.conf</em> server configuration +<p><strong>/usr/local/samba/lib/smb.conf</strong> +<p>This is the default location of the <em>smb.conf</em> server configuration file that <strong>swat</strong> edits. Other common places that systems install this file are <em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>. -<p><br>This file describes all the services the server is to make available +<p>This file describes all the services the server is to make available to clients. See <strong>smb.conf (5)</strong> for more information. -<p><br><a name="WARNINGS"></a> +<p><a name="WARNINGS"></a> <h2>WARNINGS</h2> -<p><br><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It +<p><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It will rearrange the entries and delete all comments, <a href="smb.conf.5.html#include"><strong>"include="</strong></a> and <a href="smb.conf.5.html#copy"><strong>"copy="</strong></a> options. If you have a carefully crafted <a href="smb.conf.5.html"><strong>smb.conf</strong></a> then back it up or don't use <strong>swat</strong>! -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, +<p><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell (samba-bugs@samba.org). Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell (samba@samba.org). Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 1e0396af337..8babecbcfab 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -3,9 +3,10 @@ + <html><head><title>testparm (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,53 +16,52 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> testparm - check an smb.conf configuration file for internal correctness -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>testparm</strong> [<a href="testparm.1.html#minuss">-s</a>] [<a href="testparm.1.html#minush">-h</a>] [<a href="testparm.1.html#minusL">-L servername</a>] [<a href="testparm.1.html#configfilename">configfilename</a>] [<a href="testparm.1.html#hostname">hostname</a> <a href="testparm.1.html#hostIP">hostIP</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>testparm</strong> [<a href="testparm.1.html#minuss">-s</a>] [<a href="testparm.1.html#minush">-h</a>] [<a href="testparm.1.html#minusL">-L servername</a>] [<a href="testparm.1.html#configfilename">configfilename</a>] [<a href="testparm.1.html#hostname">hostname</a> <a href="testparm.1.html#hostIP">hostIP</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>testparm</strong> is a very simple test program to check an +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>testparm</strong> is a very simple test program to check an <a href="smbd.8.html"><strong>smbd</strong></a> configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that <a href="smbd.8.html"><strong>smbd</strong></a> will successfully load the configuration file. -<p><br>Note that this is <em>NOT</em> a guarantee that the services specified in the +<p>Note that this is <em>NOT</em> a guarantee that the services specified in the configuration file will be available or will operate as expected. -<p><br>If the optional host name and host IP address are specified on the +<p>If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host has access to each service. -<p><br>If <strong>testparm</strong> finds an error in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> +<p>If <strong>testparm</strong> finds an error in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file it returns an exit code of 1 to the calling program, else it returns an exit code of 0. This allows shell scripts to test the output from <strong>testparm</strong>. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minuss"></a> -<li><strong><strong>-s</strong></strong> Without this option, <strong>testparm</strong> will prompt for a +<p><dl> +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s</strong></strong><dd> Without this option, <strong>testparm</strong> will prompt for a carriage return after printing the service names and before dumping the service definitions. -<p><br><a name="minush"></a> -<li><strong><strong>-h</strong></strong> Print usage message -<p><br><a name="minusL"></a> -<li><strong><strong>-L servername</strong></strong> Sets the value of the %L macro to servername. This +<p><a name="minush"></a> +<p></p><dt><strong><strong>-h</strong></strong><dd> Print usage message +<p><a name="minusL"></a> +<p></p><dt><strong><strong>-L servername</strong></strong><dd> Sets the value of the %L macro to servername. This is useful for testing include files specified with the %L macro. -<p><br><a name="configfilename"></a> -<li><strong><strong>configfilename</strong></strong> This is the name of the configuration file to +<p><a name="configfilename"></a> +<p></p><dt><strong><strong>configfilename</strong></strong><dd> This is the name of the configuration file to check. If this parameter is not present then the default <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file will be checked. -<p><br><a name="hostname"></a> -<li><strong><strong>hostname</strong></strong> If this parameter and the following are specified, +<p><a name="hostname"></a> +<p></p><dt><strong><strong>hostname</strong></strong><dd> If this parameter and the following are specified, then testparm will examine the <a href="smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="smb.conf.5.html#hostsdeny"><strong>"hosts deny"</strong></a> parameters in the @@ -69,45 +69,45 @@ deny"</strong></a> parameters in the with this IP address would be allowed access to the <a href="smbd.8.html"><strong>smbd</strong></a> server. If this parameter is supplied, the <a href="testparm.1.html#hostIP">hostIP</a> parameter must also be supplied. -<p><br><a name="hostIP"></a> -<li><strong><strong>hostIP</strong></strong> This is the IP address of the host specified in the +<p><a name="hostIP"></a> +<p></p><dt><strong><strong>hostIP</strong></strong><dd> This is the IP address of the host specified in the previous parameter. This address must be supplied if the hostname parameter is supplied. -<p><br></ul> -<p><br><a name="FILES"></a> +<p></dl> +<p><a name="FILES"></a> <h2>FILES</h2> -<p><br><a href="smb.conf.5.html"><strong>smb.conf</strong></a>. This is usually the name of the +<p><a href="smb.conf.5.html"><strong>smb.conf</strong></a>. This is usually the name of the configuration file used by <a href="smbd.8.html"><strong>smbd</strong></a>. -<p><br><a name="DIAGNOSTICS"></a> +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>The program will issue a message saying whether the configuration file +<p>The program will issue a message saying whether the configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details to stdout. -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index 8afbbb7cd48..42f5aebe742 100644 --- a/docs/htmldocs/testprns.1.html +++ b/docs/htmldocs/testprns.1.html @@ -3,9 +3,10 @@ + <html><head><title>testprns (1)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,33 +16,32 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> testprns - check printer name for validity with smbd -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>testprns</strong> <a href="testprns.1.html#printername">printername</a> [<a href="testprns.1.html#printcapname">printcapname</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>testprns</strong> <a href="testprns.1.html#printername">printername</a> [<a href="testprns.1.html#printcapname">printcapname</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>testprns</strong> is a very simple test program to determine whether a +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>testprns</strong> is a very simple test program to determine whether a given printer name is valid for use in a service to be provided by <a href="smbd.8.html"><strong>smbd</strong></a>. -<p><br>"Valid" in this context means "can be found in the printcap +<p>"Valid" in this context means "can be found in the printcap specified". This program is very stupid - so stupid in fact that it would be wisest to always specify the printcap file to use. -<p><br><a name="OPTIONS"></a> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="printername"></a> -<li><strong><strong>printername</strong></strong> The printer name to validate. -<p><br>Printer names are taken from the first field in each record in the +<p><dl> +<p><a name="printername"></a> +<p></p><dt><strong><strong>printername</strong></strong><dd> The printer name to validate. +<p>Printer names are taken from the first field in each record in the printcap file, single printer names and sets of aliases separated by vertical bars ("|") are recognized. Note that no validation or checking of the printcap syntax is done beyond that required to @@ -49,49 +49,49 @@ extract the printer name. It may be that the print spooling system is more forgiving or less forgiving than <strong>testprns</strong>. However, if <strong>testprns</strong> finds the printer then <a href="smbd.8.html"><strong>smbd</strong></a> should do so as well. -<p><br><a name="printcapname"></a> -<li><strong><strong>printcapname</strong></strong> This is the name of the printcap file within +<p><a name="printcapname"></a> +<p></p><dt><strong><strong>printcapname</strong></strong><dd> This is the name of the printcap file within which to search for the given printer name. -<p><br>If no printcap name is specified <strong>testprns</strong> will attempt to scan the +<p>If no printcap name is specified <strong>testprns</strong> will attempt to scan the printcap file name specified at compile time. -<p><br></ul> -<p><br><a name="FILES"></a> +<p></dl> +<p><a name="FILES"></a> <h2>FILES</h2> -<p><br><strong>/etc/printcap</strong> This is usually the default printcap file to +<p><strong>/etc/printcap</strong> This is usually the default printcap file to scan. See <strong>printcap (5)</strong>. -<p><br><a name="DIAGNOSTICS"></a> +<p><a name="DIAGNOSTICS"></a> <h2>DIAGNOSTICS</h2> -<p><br>If a printer is found to be valid, the message "Printer name +<p>If a printer is found to be valid, the message "Printer name <printername> is valid" will be displayed. -<p><br>If a printer is found to be invalid, the message "Printer name +<p>If a printer is found to be invalid, the message "Printer name <printername> is not valid" will be displayed. -<p><br>All messages that would normally be logged during operation of the +<p>All messages that would normally be logged during operation of the <a href="samba.7.html"><strong>Samba</strong></a> daemons are logged by this program to the file <code>test.log</code> in the current directory. The program runs at debuglevel 3, so quite extensive logging information is written. The log should be checked carefully for errors and warnings. -<p><br>Other messages are self-explanatory. -<p><br><a name="SEEALSO"></a> +<p>Other messages are self-explanatory. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>printcap (5)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient +<p><strong>printcap (5)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a> -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>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 <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index ad0edf32acb..1e6b822d345 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -36,8 +36,10 @@ different databases services such as NIS or DNS. The exact behaviour can be configured throught the <code>/etc/nsswitch.conf</code> file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system. -<p>The service provided by <strong>winbindd</strong> is called `winbind' and can be used to -resolve user and group information from a Windows NT server. +<p>The service provided by <strong>winbindd</strong> is called `winbind' and can be +used to resolve user and group information from a Windows NT server. +The service can also provide authentication services via an associated +PAM module. <p>The following nsswitch databases are implemented by the <strong>winbindd</strong> service: <p><dl> @@ -52,8 +54,13 @@ service: <code>/etc/nsswitch.conf</code> file can be used to initially resolve user and group information from <code>/etc/passwd</code> and <code>/etc/group</code> and then from the Windows NT server. -<p><code>passwd: files winbind</code> -<p><code>group: files winbind</code> +<p><pre> + + passwd: files winbind + group: files winbind + +</pre> + <p><a name="OPTIONS"></a> <h2>OPTIONS</h2> @@ -96,6 +103,20 @@ parameters in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. should be specified in the [global] section of <a href="smb.conf.5.html"><strong>smb.conf</strong></a>. <p><dl> +<p><p></p><dt><strong>winbind separator</strong><dd> +<p>The winbind separator option allows you to specify how NT domain names +and user names are combined into unix user names when presented to +users. By default winbind will use the traditional \ separator so +that the unix user names look like DOMAIN\username. In some cases +this separator character may cause problems as the \ character has +special meaning in unix shells. In that case you can use the winbind +separator option to specify an alternative sepataror character. Good +alternatives may be / (although that conflicts with the unix directory +separator) or a + character. The + character appears to be the best +choice for 100% compatibility with existing unix utilities, but may be +an aesthetically bad choice depending on your taste. +<p><strong>Example:</strong> +<code> winbind separator = +</code> <p><p></p><dt><strong>winbind uid</strong><dd> <p>The winbind uid parameter specifies the range of user ids that are allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon. This range of @@ -117,9 +138,16 @@ conflicts can occur otherwise. <p><p></p><dt><strong>winbind cache time</strong><dd> <p>This parameter specifies the number of seconds the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon will cache user and group -information before querying a Windows NT server again. +information before querying a Windows NT server again. When a item in +the cache is older than this time winbindd will ask the domain +controller for the sequence number of the servers account database. If +the sequence number has not changed then the cached item is marked as +valid for a further "winbind cache time" seconds. Otherwise the item +is fetched from the server. This means that as long as the account +database is not actively changing winbindd will only have to send one +sequence number query packet every "winbind cache time" seconds. <p><strong>Default:</strong> -<code> winbind cache type = 15</code> +<code> winbind cache time = 15</code> <p><p></p><dt><strong>template homedir</strong><dd> <p>When filling out the user information for a Windows NT user, the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in @@ -131,12 +159,85 @@ is present it is substituted with the user's Windows NT user name. <p><p></p><dt><strong>template shell</strong><dd> <p>When filling out the user information for a Windows NT user, the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in -the home directory for that user. If the string <code>%D</code> is present it is -substituted with the user's Windows NT domain name. If the string <code>%U</code> -is present it is substituted with the user's Windows NT user name. +the shell for that user. <p><strong>Default:</strong> -<code> template homedir = /home/%D/%U</code> +<code> template shell = /bin/false</code> <p></dl> +<p><a name="EXAMPLESETUP"></a> +<h2>EXAMPLE SETUP</h2> + +<p>To setup winbindd for user and group lookups plus authentication from +a domain controller use something like the following setup. This was +tested on a RedHat 6.2 Linux box. +<p>In /etc/nsswitch.conf put the following: +<pre> + + passwd: files winbind + group: files winbind + +</pre> + +<p>In /etc/pam.d/* replace the auth lines with something like this: +<pre> + + auth required /lib/security/pam_securetty.so + auth required /lib/security/pam_nologin.so + auth sufficient /lib/security/pam_winbind.so + auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok + +</pre> + +<p>Note in particular the use of the sufficient keyword and the +use_first_pass keyword. +<p>Now replace the account lines with this: +<pre> + + account required /lib/security/pam_winbind.so + +</pre> + +<p>The next step is to join the domain. To do that use the samedit +program like this: +<pre> + + samedit -S '*' -W DOMAIN -UAdministrator + +</pre> + +<p>Then within samedit run the command: +<pre> + + createuser MACHINE$ -j DOMAIN -L + +</pre> + +<p>This assumes your domain is called DOMAIN and your Samba workstation +is called MACHINE. +<p>Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to +/lib/security. +<p>Finally, setup a smb.conf containing directives like the following: +<pre> + + [global] + winbind separator = + + winbind cache time = 10 + template shell = /bin/bash + template homedir = /home/%D/%U + winbind uid = 10000-20000 + winbind gid = 10000-20000 + workgroup = DOMAIN + security = domain + password server = * + +</pre> + +<p>Now start winbindd and you should find that your user and group +database is expanded to include your NT users and groups, and that you +can login to your unix box as a domain user, using the DOMAIN+user +syntax for the username. You may wish to use the commands "getent +passwd" and "getent group" to confirm the correct operation of +winbindd. +<p>NOTE: nmbd must be running on the local machine for winbindd to work. <p><a name="FILES"></a> <h2>FILES</h2> @@ -170,9 +271,8 @@ is damaged or destroyed then the mappings will be lost. <h2>AUTHOR</h2> <p>The original Samba software and related utilities were created by -Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed -by the Samba Team as an Open Source project similar to the way the -Linux kernel is developed. +Andrew Tridgell. Samba is now developed by the Samba Team as an Open +Source project. <p>Winbindd was written by Tim Potter. </body> </html> diff --git a/docs/manpages/lmhosts.5 b/docs/manpages/lmhosts.5 index 534c2484150..3609ca256f0 100644 --- a/docs/manpages/lmhosts.5 +++ b/docs/manpages/lmhosts.5 @@ -76,7 +76,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -85,7 +85,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/make_smbcodepage.1 b/docs/manpages/make_smbcodepage.1 index 9c134201078..e6c76d9855d 100644 --- a/docs/manpages/make_smbcodepage.1 +++ b/docs/manpages/make_smbcodepage.1 @@ -61,7 +61,7 @@ provided in the Samba distribution for codepages 437 (USA), 737 866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949 (Hangul) and 950 (Traditional Chinese)\&. Users are encouraged to write text codepage definition files for their own code pages and donate -them to \fIsamba-bugs@samba\&.org\fP\&. All codepage files in the +them to samba@samba\&.org\&. All codepage files in the Samba \fIsource/codepages\fP directory are compiled and installed when a \fI\'make install\'\fP command is issued there\&. .PP @@ -128,7 +128,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -137,7 +137,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8 index 72aeaf14a77..55930f6629a 100644 --- a/docs/manpages/nmbd.8 +++ b/docs/manpages/nmbd.8 @@ -6,7 +6,7 @@ naming services to clients .PP .SH "SYNOPSIS" .PP -\fBnmbd\fP [-D] [-a] [-o] [-h] [-V] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file] [-i NetBIOS scope] +\fBnmbd\fP [-D] [-a] [-o] [-h] [-V] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file] .PP .SH "DESCRIPTION" .PP @@ -136,14 +136,6 @@ this may be changed when Samba is autoconfigured\&. The file specified contains the configuration details required by the server\&. See \fBsmb\&.conf (5)\fP for more information\&. .IP -.IP "\fB-i scope\fP" -This specifies a NetBIOS scope that \fBnmbd\fP will use -to communicate with when generating NetBIOS names\&. For details on the -use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes -are \fIvery\fP rarely used, only set this parameter if you are the -system administrator in charge of all the NetBIOS systems you -communicate with\&. -.IP .PP .SH "FILES" .PP @@ -212,7 +204,7 @@ http://samba\&.org/cifs/\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -221,7 +213,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/nmblookup.1 b/docs/manpages/nmblookup.1 index a542e6d5074..3d1491e8788 100644 --- a/docs/manpages/nmblookup.1 +++ b/docs/manpages/nmblookup.1 @@ -139,7 +139,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -148,7 +148,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7 index 96975f34c26..a508093b8b6 100644 --- a/docs/manpages/samba.7 +++ b/docs/manpages/samba.7 @@ -20,7 +20,7 @@ described in a separate manual page\&. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use\&. If the manual pages aren\'t clear enough then please send a patch or bug report -to \fIsamba-bugs@samba\&.org\fP\&. +to samba@samba\&.org\&. .PP .IP .IP "\fBsmbd\fP" @@ -121,13 +121,13 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "CONTRIBUTIONS" .PP If you wish to contribute to the Samba project, then I suggest you -join the Samba mailing list at \fIsamba@samba\&.org\fP\&. See the +join the Samba mailing list at samba@samba\&.org\&. See the Web page at http://samba\&.org/listproc for details on how to do this\&. .PP If you have patches to submit or bugs to report then you may mail them -directly to \fIsamba-bugs@samba\&.org\fP\&. Note, however, that due to +directly to samba@samba\&.org\&. Note, however, that due to the enormous popularity of this package the Samba Team may take some time to respond to mail\&. We prefer patches in \fIdiff -u\fP format\&. .PP @@ -149,7 +149,7 @@ http://samba\&.org/samba/samba-thanks\&.html\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -158,4 +158,4 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5 index ac227d91821..3847288a03e 100644 --- a/docs/manpages/smb.conf.5 +++ b/docs/manpages/smb.conf.5 @@ -86,7 +86,7 @@ write access to the path \f(CW/home/bar\fP\&. The share is accessed via the share name "foo": .PP -.DS +.nf @@ -95,7 +95,7 @@ the share name "foo": writeable = true -.DE +.fi .PP @@ -106,7 +106,7 @@ is via calls to open, write to and close a spool file\&. The as the default guest user (specified elsewhere): .PP -.DS +.nf [aprinter] @@ -115,7 +115,7 @@ as the default guest user (specified elsewhere): printable = true guest ok = true -.DE +.fi .PP @@ -175,13 +175,13 @@ section can specify, though some make more sense than others\&. The following is a typical and suitable [homes] section: .IP -.DS +.nf [homes] writeable = yes -.DE +.fi .IP @@ -237,7 +237,7 @@ directory with the sticky bit set on it\&. A typical \fB[printers]\fP entry would look like this: .IP -.DS +.nf [printers] @@ -245,7 +245,7 @@ would look like this: guest ok = yes printable = yes -.DE +.fi .IP @@ -256,10 +256,10 @@ pseudo-printcap\&. This is a file consisting of one or more lines like this: .IP -.DS +.nf alias|alias|alias|alias\&.\&.\&. -.DE +.fi .IP @@ -377,7 +377,7 @@ negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\&. machine\&. Only some are recognized, and those may not be 100% reliable\&. It currently recognizes Samba, WfWg, WinNT and Win95\&. Anything else will be known as "UNKNOWN"\&. If it gets it wrong -then sending a level 3 log to \fIsamba@samba\&.org\fP +then sending a level 3 log to samba@samba\&.org should allow it to be fixed\&. .IP .IP o @@ -1993,7 +1993,7 @@ interesting things\&. .IP \fBExample:\fP -.DS +.nf default service = pub @@ -2001,7 +2001,7 @@ interesting things\&. [pub] path = /%S -.DE +.fi .IP @@ -2138,26 +2138,26 @@ and remaining space will be used\&.\fP Where the script dfree (which must be made executable) could be: .IP -.DS +.nf #!/bin/sh df $1 | tail -1 | awk \'{print $2" "$4}\' -.DE +.fi .IP or perhaps (on Sys V based systems): .IP -.DS +.nf #!/bin/sh /usr/bin/df -k $1 | tail -1 | awk \'{print $3" "$5}\' -.DE +.fi .IP @@ -2267,7 +2267,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list \fBSamba-ntdom\fP available by sending email to -\fIlistproc@samba\&.org\fP +listproc@samba\&.org .IP .IP "\fBdomain admin users (G)\fP" .IP @@ -2276,7 +2276,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list \fBSamba-ntdom\fP available by sending email to -\fIlistproc@samba\&.org\fP +listproc@samba\&.org .IP .IP "\fBdomain groups (G)\fP" .IP @@ -2285,7 +2285,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list \fBSamba-ntdom\fP available by sending email to -\fIlistproc@samba\&.org\fP +listproc@samba\&.org .IP .IP "\fBdomain guest group (G)\fP" .IP @@ -2294,7 +2294,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list \fBSamba-ntdom\fP available by sending email to -\fIlistproc@samba\&.org\fP +listproc@samba\&.org .IP .IP "\fBdomain guest users (G)\fP" .IP @@ -2303,7 +2303,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&. To work with the latest code builds that may have more support for Samba NT Domain Controller functionality please subscribe to the mailing list \fBSamba-ntdom\fP available by sending email to -\fIlistproc@samba\&.org\fP +listproc@samba\&.org .IP .IP "\fBdomain logons (G)\fP" .IP @@ -2796,13 +2796,13 @@ files"\fP and \fB"case sensitive"\fP\&. .IP \fBDefault\fP -.DS +.nf No files or directories are hidden by this option (dot files are hidden by default because of the "hide dot files" option)\&. -.DE +.fi .IP @@ -4480,20 +4480,20 @@ debug"\fP\&. .IP \fBExample:\fP -.DS +.nf passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en "*Reenter NEW password*" %n\en "*Password changed*" -.DE +.fi .IP \fBDefault:\fP -.DS +.nf passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed* -.DE +.fi .IP @@ -4745,12 +4745,12 @@ 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: .IP -.DS +.nf preexec = csh -c \'echo \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient -M %m -I %I\' & -.DE +.fi .IP @@ -4923,7 +4923,7 @@ to obtain a printer list\&. A minimal printcap file would look something like this: .IP -.DS +.nf print1|My Printer 1 @@ -4932,7 +4932,7 @@ A minimal printcap file would look something like this: print4|My Printer 4 print5|My Printer 5 -.DE +.fi .IP @@ -5807,7 +5807,7 @@ 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 -\fIsamba@samba\&.org\fP\&. +samba@samba\&.org\&. .IP Any of the supported socket options may be combined in any way you like, as long as your OS allows it\&. @@ -6474,13 +6474,13 @@ information on how this parameter determines access to the services\&. .IP \fBExamples:\fP -.DS +.nf username = fred username = fred, mary, jack, jane, @users, @pcgroup -.DE +.fi .IP @@ -6564,13 +6564,13 @@ and map the rest to guest\&. Note the use of the \f(CW\'!\'\fP to tell Samba to stop processing if it gets a match on that line\&. .IP -.DS +.nf !sys = mary fred guest = * -.DE +.fi .IP @@ -6686,14 +6686,14 @@ is a pointless thing to do as it\'s already there) you could do one of the following .IP -.DS +.nf valid chars = Z valid chars = z:Z valid chars = 0132:0172 -.DE +.fi .IP @@ -6710,13 +6710,13 @@ See also the \fB"client code page"\fP parameter\&. .IP \fBDefault:\fP -.DS +.nf Samba defaults to using a reasonable set of valid characters for English systems -.DE +.fi .IP @@ -6728,7 +6728,7 @@ them\&. .IP NOTE: It is actually quite difficult to correctly produce a \fB"valid chars"\fP line for a particular system\&. To automate the process -\fItino@augsburg\&.net\fP has written a package called \fB"validchars"\fP +tino@augsburg\&.net has written a package called \fB"validchars"\fP which will automatically produce a complete \fB"valid chars"\fP line for a given client system\&. Look in the examples/validchars/ subdirectory of your Samba source code distribution for this package\&. @@ -6792,7 +6792,7 @@ sensitive"\fP\&. Example 1\&. .IP -.DS +.nf @@ -6802,14 +6802,14 @@ Example 1\&. veto files = /*Security*/*\&.tmp/*root*/ -.DE +.fi .IP Example 2\&. .IP -.DS +.nf Veto the Apple specific files that a NetAtalk server @@ -6817,7 +6817,7 @@ Example 2\&. veto files = /\&.AppleDouble/\&.bin/\&.AppleDesktop/Network Trash Folder/ -.DE +.fi .IP @@ -7037,14 +7037,14 @@ permitting), but only via spooling operations\&. .IP \fBExamples:\fP -.DS +.nf read only = no writeable = yes write ok = yes -.DE +.fi .IP @@ -7083,7 +7083,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -7092,7 +7092,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1 index 4346629adbd..6b3edb38fc7 100644 --- a/docs/manpages/smbclient.1 +++ b/docs/manpages/smbclient.1 @@ -760,7 +760,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -769,7 +769,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8 index 5efd6794787..5ee6cd53082 100644 --- a/docs/manpages/smbd.8 +++ b/docs/manpages/smbd.8 @@ -5,7 +5,7 @@ smbd \- server to provide SMB/CIFS services to clients .PP .SH "SYNOPSIS" .PP -\fBsmbd\fP [-D] [-a] [-o] [-P] [-h] [-V] [-d debuglevel] [-l log file] [-p port number] [-O socket options] [-s configuration file] [-i scope] +\fBsmbd\fP [-D] [-a] [-o] [-P] [-h] [-V] [-d debuglevel] [-l log file] [-p port number] [-O socket options] [-s configuration file] .PP .SH "DESCRIPTION" .PP @@ -137,14 +137,6 @@ of all the services that the server is to provide\&. See \fBsmb\&.conf (5)\fP for more information\&. The default configuration file name is determined at compile time\&. .IP -.IP "\fB-i scope\fP" -This specifies a NetBIOS scope that the server will use -to communicate with when generating NetBIOS names\&. For details on the -use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes -are \fIvery\fP rarely used, only set this parameter if you are the -system administrator in charge of all the NetBIOS systems you -communicate with\&. -.IP .PP .SH "FILES" .PP @@ -329,7 +321,7 @@ Lastly, edit the configuration file to provide suitable services\&. To start with, the following two services should be all you need: .PP -.DS +.nf @@ -343,7 +335,7 @@ start with, the following two services should be all you need: public = yes -.DE +.fi .PP @@ -423,7 +415,7 @@ http://samba\&.org/cifs/\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -432,7 +424,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, comments etc\&. diff --git a/docs/manpages/smbpasswd.5 b/docs/manpages/smbpasswd.5 index e3fbcf161ee..bc87d134d23 100644 --- a/docs/manpages/smbpasswd.5 +++ b/docs/manpages/smbpasswd.5 @@ -166,14 +166,14 @@ Samba \f(CWbin/\fP directory (the same place that the \fBsmbd\fP and \fBnmbd\fP binaries are installed) as follows: .PP -.DS +.nf cat old_smbpasswd_file | convert_smbpasswd > new_smbpasswd_file -.DE +.fi .PP @@ -198,7 +198,7 @@ algorithm\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -207,7 +207,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy -Allison, \fIsamba-bugs@samba\&.org\fP\&. +Allison, samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbpasswd.8 b/docs/manpages/smbpasswd.8 index ad502e01b12..be70fad031d 100644 --- a/docs/manpages/smbpasswd.8 +++ b/docs/manpages/smbpasswd.8 @@ -5,7 +5,7 @@ smbpasswd \- change a users SMB password .PP .SH "SYNOPSIS" .PP -\fBsmbpasswd\fP [-a] [-d] [-e] [-D debug level] [-n] [-r remote_machine] [-R name resolve order] [-m] [-j DOMAIN] [-U username] [-h] [-s] username +\fBsmbpasswd\fP [-a] [-x] [-d] [-e] [-D debug level] [-n] [-r remote_machine] [-R name resolve order] [-m] [-j DOMAIN] [-U username] [-h] [-s] username .PP .SH "DESCRIPTION" .PP @@ -62,6 +62,13 @@ else the request to add the user will fail\&. This option is only available when running \fBsmbpasswd\fP as root\&. .IP +.IP "\fB-x\fP" +This option specifies that the username following should +be deleted from the local \fBsmbpasswd\fP file\&. +.IP +This option is only available when running \fBsmbpasswd\fP as +root\&. +.IP .IP "\fB-d\fP" This option specifies that the username following should be \fIdisabled\fP in the local \fBsmbpasswd\fP file\&. @@ -199,7 +206,7 @@ being used as an NT Primary Domain Controller\&. PDC support is not a supported feature in Samba2\&.0 but will become supported in a later release\&. If you wish to know more about using Samba as an NT PDC then please subscribe to the mailing list -\fIsamba-ntdom@samba\&.org\fP\&. +samba-ntdom@samba\&.org\&. .IP This option is only available when running \fBsmbpasswd\fP as root\&. .IP @@ -285,7 +292,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .IP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .IP @@ -294,7 +301,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .IP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbrun.1 b/docs/manpages/smbrun.1 index d34b408d6bd..24d6efdfcd9 100644 --- a/docs/manpages/smbrun.1 +++ b/docs/manpages/smbrun.1 @@ -53,7 +53,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -62,7 +62,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1 index 7899344d7fb..ac7cba7149d 100644 --- a/docs/manpages/smbstatus.1 +++ b/docs/manpages/smbstatus.1 @@ -59,7 +59,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -68,7 +68,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1 index 2aaa542231e..f7979b76b1e 100644 --- a/docs/manpages/smbtar.1 +++ b/docs/manpages/smbtar.1 @@ -105,19 +105,19 @@ the \fBsmbclient\fP command\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP -Ricky Poulten \fIpoultenr@logica\&.co\&.uk\fP wrote the tar extension and +Ricky Poulten poultenr@logica\&.co\&.uk wrote the tar extension and this man page\&. The \fBsmbtar\fP script was heavily rewritten and -improved by Martin Kraemer \fIMartin\&.Kraemer@mch\&.sni\&.de\fP\&. Many +improved by Martin Kraemer Martin\&.Kraemer@mch\&.sni\&.de\&. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc\&. The man page sources were converted to YODL format (another excellent piece of Open Source software available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison, -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8 index 8798c0a566e..3fc450f3854 100644 --- a/docs/manpages/swat.8 +++ b/docs/manpages/swat.8 @@ -49,14 +49,14 @@ swat binary and the various help files and images\&. A default install would put these in: .PP -.DS +.nf /usr/local/samba/bin/swat /usr/local/samba/swat/images/* /usr/local/samba/swat/help/* -.DE +.fi .PP @@ -137,7 +137,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell (samba-bugs@samba\&.org)\&. Samba is now developed +Andrew Tridgell (samba@samba\&.org)\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -146,7 +146,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1 index 2d4c03a1641..e02b8873943 100644 --- a/docs/manpages/testparm.1 +++ b/docs/manpages/testparm.1 @@ -88,7 +88,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -97,7 +97,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1 index bb366e329c3..a9753d7637c 100644 --- a/docs/manpages/testprns.1 +++ b/docs/manpages/testprns.1 @@ -71,7 +71,7 @@ Other messages are self-explanatory\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +Andrew Tridgell samba@samba\&.org\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. .PP @@ -80,7 +80,7 @@ sources were converted to YODL format (another excellent piece of Open Source software, available at \fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) and updated for the Samba2\&.0 release by Jeremy Allison\&. -\fIsamba-bugs@samba\&.org\fP\&. +samba@samba\&.org\&. .PP See \fBsamba (7)\fP to find out how to get a full list of contributors and details on how to submit bug reports, diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8 index 0b0c8b4019f..e35fe0815b4 100644 --- a/docs/manpages/winbindd.8 +++ b/docs/manpages/winbindd.8 @@ -20,8 +20,10 @@ be configured throught the \f(CW/etc/nsswitch\&.conf\fP file\&. Users and group are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system\&. .PP -The service provided by \fBwinbindd\fP is called `winbind\' and can be used to -resolve user and group information from a Windows NT server\&. +The service provided by \fBwinbindd\fP is called `winbind\' and can be +used to resolve user and group information from a Windows NT server\&. +The service can also provide authentication services via an associated +PAM module\&. .PP The following nsswitch databases are implemented by the \fBwinbindd\fP service: @@ -43,9 +45,16 @@ For example, the following simple configuration in the information from \f(CW/etc/passwd\fP and \f(CW/etc/group\fP and then from the Windows NT server\&. .PP -\f(CWpasswd: files winbind\fP -.PP -\f(CWgroup: files winbind\fP + +.nf + + + passwd: files winbind + group: files winbind + +.fi + + .PP .SH "OPTIONS" .PP @@ -91,6 +100,23 @@ should be specified in the [global] section of \fBsmb\&.conf\fP\&. .PP .IP +.IP "winbind separator" +.IP +The winbind separator option allows you to specify how NT domain names +and user names are combined into unix user names when presented to +users\&. By default winbind will use the traditional \e separator so +that the unix user names look like DOMAIN\eusername\&. In some cases +this separator character may cause problems as the \e character has +special meaning in unix shells\&. In that case you can use the winbind +separator option to specify an alternative sepataror character\&. Good +alternatives may be / (although that conflicts with the unix directory +separator) or a + character\&. The + character appears to be the best +choice for 100% compatibility with existing unix utilities, but may be +an aesthetically bad choice depending on your taste\&. +.IP +\fBExample:\fP +\f(CW winbind separator = +\fP +.IP .IP "winbind uid" .IP The winbind uid parameter specifies the range of user ids that are @@ -121,10 +147,17 @@ conflicts can occur otherwise\&. .IP This parameter specifies the number of seconds the \fBwinbindd\fP daemon will cache user and group -information before querying a Windows NT server again\&. +information before querying a Windows NT server again\&. When a item in +the cache is older than this time winbindd will ask the domain +controller for the sequence number of the servers account database\&. If +the sequence number has not changed then the cached item is marked as +valid for a further "winbind cache time" seconds\&. Otherwise the item +is fetched from the server\&. This means that as long as the account +database is not actively changing winbindd will only have to send one +sequence number query packet every "winbind cache time" seconds\&. .IP \fBDefault:\fP -\f(CW winbind cache type = 15\fP +\f(CW winbind cache time = 15\fP .IP .IP "template homedir" .IP @@ -141,14 +174,116 @@ is present it is substituted with the user\'s Windows NT user name\&. .IP When filling out the user information for a Windows NT user, the \fBwinbindd\fP daemon uses this parameter to fill in -the home directory for that user\&. If the string \f(CW%D\fP is present it is -substituted with the user\'s Windows NT domain name\&. If the string \f(CW%U\fP -is present it is substituted with the user\'s Windows NT user name\&. +the shell for that user\&. .IP \fBDefault:\fP -\f(CW template homedir = /home/%D/%U\fP +\f(CW template shell = /bin/false\fP .IP .PP +.SH "EXAMPLE SETUP" +.PP +To setup winbindd for user and group lookups plus authentication from +a domain controller use something like the following setup\&. This was +tested on a RedHat 6\&.2 Linux box\&. +.PP +In /etc/nsswitch\&.conf put the following: + +.nf + + + passwd: files winbind + group: files winbind + +.fi + + +.PP +In /etc/pam\&.d/* replace the auth lines with something like this: + +.nf + + + auth required /lib/security/pam_securetty\&.so + auth required /lib/security/pam_nologin\&.so + auth sufficient /lib/security/pam_winbind\&.so + auth required /lib/security/pam_pwdb\&.so use_first_pass shadow nullok + +.fi + + +.PP +Note in particular the use of the sufficient keyword and the +use_first_pass keyword\&. +.PP +Now replace the account lines with this: + +.nf + + + account required /lib/security/pam_winbind\&.so + +.fi + + +.PP +The next step is to join the domain\&. To do that use the samedit +program like this: + +.nf + + + samedit -S \'*\' -W DOMAIN -UAdministrator + +.fi + + +.PP +Then within samedit run the command: + +.nf + + + createuser MACHINE$ -j DOMAIN -L + +.fi + + +.PP +This assumes your domain is called DOMAIN and your Samba workstation +is called MACHINE\&. +.PP +Next copy libnss_winbind\&.so\&.2 to /lib and pam_winbind\&.so to +/lib/security\&. +.PP +Finally, setup a smb\&.conf containing directives like the following: + +.nf + + + [global] + winbind separator = + + winbind cache time = 10 + template shell = /bin/bash + template homedir = /home/%D/%U + winbind uid = 10000-20000 + winbind gid = 10000-20000 + workgroup = DOMAIN + security = domain + password server = * + +.fi + + +.PP +Now start winbindd and you should find that your user and group +database is expanded to include your NT users and groups, and that you +can login to your unix box as a domain user, using the DOMAIN+user +syntax for the username\&. You may wish to use the commands "getent +passwd" and "getent group" to confirm the correct operation of +winbindd\&. +.PP +NOTE: nmbd must be running on the local machine for winbindd to work\&. +.PP .SH "FILES" .PP The following files are relevant to the operation of the \fBwinbindd\fP @@ -192,8 +327,7 @@ Storage for cached user and group information\&. .SH "AUTHOR" .PP The original Samba software and related utilities were created by -Andrew Tridgell samba-bugs@samba\&.org\&. Samba is now developed -by the Samba Team as an Open Source project similar to the way the -Linux kernel is developed\&. +Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open +Source project\&. .PP Winbindd was written by Tim Potter\&. diff --git a/docs/textdocs/DOMAIN_MEMBER.txt b/docs/textdocs/DOMAIN_MEMBER.txt index 53fd6d94f94..d58a8bc0994 100644 --- a/docs/textdocs/DOMAIN_MEMBER.txt +++ b/docs/textdocs/DOMAIN_MEMBER.txt @@ -3,7 +3,7 @@ TITLE INFORMATION: Joining an NT Domain with Samba 2.0 AUTHOR INFORMATION: Jeremy Allison, Samba Team DATE INFORMATION: 7th October 1999 -Contents +Table of Contents Joining an NT Domain with Samba 2.0 ----------------------------------- @@ -25,7 +25,7 @@ command smbpasswd -j DOM -r DOMPDC as we are joining the domain DOM and the PDC for that domain (the only -machine that has write access to the domain SAM database). If this is +machine that has write access to the domain SAM database) is DOMPDC. If this is successful you will see the message: smbpasswd: Joined domain DOM. @@ -35,8 +35,8 @@ man page for more details. This command goes through the machine account password change protocol, then writes the new (random) machine account password for -this Samba server into the a file in the same directory in which an -smbpasswd file would be stored (normally : +this Samba server into a file in the same directory in which an +smbpasswd file would be stored - normally : /usr/local/samba/private diff --git a/docs/yodldocs/winbindd.8.yo b/docs/yodldocs/winbindd.8.yo index 77e14ad5f44..ce32565755f 100644 --- a/docs/yodldocs/winbindd.8.yo +++ b/docs/yodldocs/winbindd.8.yo @@ -23,8 +23,10 @@ be configured throught the tt(/etc/nsswitch.conf) file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system. -The service provided by bf(winbindd) is called `winbind' and can be used to -resolve user and group information from a Windows NT server. +The service provided by bf(winbindd) is called `winbind' and can be +used to resolve user and group information from a Windows NT server. +The service can also provide authentication services via an associated +PAM module. The following nsswitch databases are implemented by the bf(winbindd) service: @@ -48,9 +50,10 @@ tt(/etc/nsswitch.conf) file can be used to initially resolve user and group information from tt(/etc/passwd) and tt(/etc/group) and then from the Windows NT server. -tt(passwd: files winbind) - -tt(group: files winbind) +verb( + passwd: files winbind + group: files winbind +) label(OPTIONS) manpageoptions() @@ -104,6 +107,23 @@ url(bf(smb.conf))(smb.conf.5.html). startdit() +dit(winbind separator) + +The winbind separator option allows you to specify how NT domain names +and user names are combined into unix user names when presented to +users. By default winbind will use the traditional \ separator so +that the unix user names look like DOMAIN\username. In some cases +this separator character may cause problems as the \ character has +special meaning in unix shells. In that case you can use the winbind +separator option to specify an alternative sepataror character. Good +alternatives may be / (although that conflicts with the unix directory +separator) or a + character. The + character appears to be the best +choice for 100% compatibility with existing unix utilities, but may be +an aesthetically bad choice depending on your taste. + + bf(Example:) +tt( winbind separator = +) + dit(winbind uid) The winbind uid parameter specifies the range of user ids that are @@ -134,10 +154,17 @@ dit(winbind cache time) This parameter specifies the number of seconds the url(bf(winbindd))(winbindd.8.html) daemon will cache user and group -information before querying a Windows NT server again. +information before querying a Windows NT server again. When a item in +the cache is older than this time winbindd will ask the domain +controller for the sequence number of the servers account database. If +the sequence number has not changed then the cached item is marked as +valid for a further "winbind cache time" seconds. Otherwise the item +is fetched from the server. This means that as long as the account +database is not actively changing winbindd will only have to send one +sequence number query packet every "winbind cache time" seconds. bf(Default:) -tt( winbind cache type = 15) +tt( winbind cache time = 15) dit(template homedir) @@ -154,15 +181,83 @@ dit(template shell) When filling out the user information for a Windows NT user, the url(bf(winbindd))(winbindd.8.html) daemon uses this parameter to fill in -the home directory for that user. If the string tt(%D) is present it is -substituted with the user's Windows NT domain name. If the string tt(%U) -is present it is substituted with the user's Windows NT user name. +the shell for that user. bf(Default:) -tt( template homedir = /home/%D/%U) +tt( template shell = /bin/false) enddit() + +label(EXAMPLESETUP) +manpagesection(EXAMPLE SETUP) + +To setup winbindd for user and group lookups plus authentication from +a domain controller use something like the following setup. This was +tested on a RedHat 6.2 Linux box. + +In /etc/nsswitch.conf put the following: +verb( + passwd: files winbind + group: files winbind +) + +In /etc/pam.d/* replace the auth lines with something like this: +verb( + auth required /lib/security/pam_securetty.so + auth required /lib/security/pam_nologin.so + auth sufficient /lib/security/pam_winbind.so + auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok +) + +Note in particular the use of the sufficient keyword and the +use_first_pass keyword. + +Now replace the account lines with this: +verb( + account required /lib/security/pam_winbind.so +) + +The next step is to join the domain. To do that use the samedit +program like this: +verb( + samedit -S '*' -W DOMAIN -UAdministrator +) + +Then within samedit run the command: +verb( + createuser MACHINE$ -j DOMAIN -L +) + +This assumes your domain is called DOMAIN and your Samba workstation +is called MACHINE. + +Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to +/lib/security. + +Finally, setup a smb.conf containing directives like the following: +verb( + [global] + winbind separator = + + winbind cache time = 10 + template shell = /bin/bash + template homedir = /home/%D/%U + winbind uid = 10000-20000 + winbind gid = 10000-20000 + workgroup = DOMAIN + security = domain + password server = * +) + +Now start winbindd and you should find that your user and group +database is expanded to include your NT users and groups, and that you +can login to your unix box as a domain user, using the DOMAIN+user +syntax for the username. You may wish to use the commands "getent +passwd" and "getent group" to confirm the correct operation of +winbindd. + +NOTE: nmbd must be running on the local machine for winbindd to work. + label(FILES) manpagefiles() @@ -211,8 +306,7 @@ label(AUTHOR) manpageauthor() The original Samba software and related utilities were created by -Andrew Tridgell email(samba-bugs@samba.org). Samba is now developed -by the Samba Team as an Open Source project similar to the way the -Linux kernel is developed. +Andrew Tridgell. Samba is now developed by the Samba Team as an Open +Source project. Winbindd was written by Tim Potter. |