Added mention of the CUPS option for the printing parameter

-jerry (This used to be commit 3fed01f9c311bb81ce3013453a5dc9630201ccf1)
author: Gerald Carter <jerry@samba.org> 2000-05-12 13:05:24 +0000
committer: Gerald Carter <jerry@samba.org> 2000-05-12 13:05:24 +0000
commit: 30129251f26a4b2b59817eb984cc76251e89691d (patch)
tree: 42006fe63c790141f49c73bae3a4d7ee1d1e75f3 /docs
parent: 75ebfc6f7a7692d772b729b2d83038a9054b4f90 (diff)
download: samba-30129251f26a4b2b59817eb984cc76251e89691d.tar.gz
samba-30129251f26a4b2b59817eb984cc76251e89691d.tar.bz2
samba-30129251f26a4b2b59817eb984cc76251e89691d.zip
3 files changed, 1216 insertions, 823 deletions
diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html
index 521c70d653..adda876afd 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -5,7 +5,7 @@
 
 <html><head><title>smb.conf (5)</title>
 
-<link rev="made" href="mailto:samba-bugs@samba.org">
+<link rev="made" href="mailto:samba@samba.org">
 </head>
 <body>
 
@@ -59,12 +59,12 @@ numeric.
 <h2>SECTION DESCRIPTIONS</h2>
     
 <p><br>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
+<a href="../yodldocs/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="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
+<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
 following notes apply to ordinary section descriptions.
 <p><br>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
@@ -72,14 +72,14 @@ the service. Some housekeeping options are also specifiable.
 <p><br>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="smb.conf.5.html#guestok"><strong>guest</strong></a> services, in which
+<p><br>Sections may be designated <a href="../yodldocs/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="smb.conf.5.html#guestaccount"><strong>guest account</strong></a> is used to define access
+<a href="../yodldocs/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
 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="smb.conf.5.html#user"><strong>"user="</strong></a> option in
+check against the password using the <a href="../yodldocs/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
@@ -102,13 +102,13 @@ the share name "foo":
 <p><br>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="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> parameter means access will be permitted
+<a href="../yodldocs/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>
 
  	[aprinter]
  		path = /usr/spool/public
- 		read only = true
+ 		writeable = false
  		printable = true
  		guest ok = true
 
@@ -122,7 +122,7 @@ as the default guest user (specified elsewhere):
 <li><strong><strong>The [global] section</strong></strong>
 <p><br>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="smb.conf.5.html#PARAMETERS"><strong>'PARAMETERS'</strong></a> for more
+items. See the notes under <a href="../yodldocs/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>
@@ -141,8 +141,8 @@ username
 <p><br><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="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>
+<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>
 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
@@ -166,26 +166,26 @@ following is a typical and suitable [homes] section:
 <p><br>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="smb.conf.5.html#readonly"><strong>read only
+actually desirable, it would be wise to also specify <a href="../yodldocs/smb.conf.5.html#readonly"><strong>read only
 access</strong></a>.
-<p><br>Note that the <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a> flag for auto home
+<p><br>Note that the <a href="../yodldocs/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="smb.conf.5.html#homes"><strong>[homes]</strong></a>, but for printers.
-<p><br>If a [printers] section occurs in the configuration file, users are
+<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
 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
 scanned. If a match is found, it is used. If no match is found, but a
-<a href="smb.conf.5.html#homes"><strong>[homes]</strong></a> section exists, it is used as described
+<a href="../yodldocs/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 [printers]
+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>
@@ -195,16 +195,15 @@ located printer name
 <p><br><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 [printers] service MUST be printable - if you specify
+<p><br>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
-directory with the sticky bit set on it. A typical [printers] entry
+directory with the sticky bit set on it. A typical <strong>[printers]</strong> entry
 would look like this:
 <p><br><pre>
 
  	[printers]
  		path = /usr/spool/public
- 		writeable = no
  		guest ok = yes
  		printable = yes 
 
@@ -220,7 +219,7 @@ this:
 </pre>
 
 <p><br>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
+subsystem. In the <a href="../yodldocs/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
@@ -230,26 +229,26 @@ 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="smb.conf.5.html#printcapname"><strong>"printcap name =
+defined on the system you may be able to use <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>"printcap name =
 lpstat"</strong></a> to automatically obtain a list of
-printers. See the <a href="smb.conf.5.html#printcapname"><strong>"printcap name"</strong></a> option for
+printers. See the <a href="../yodldocs/smb.conf.5.html#printcapname"><strong>"printcap name"</strong></a> option for
 more details.
 <p><br></ul>
 <p><br><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="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
+<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
 permissible only in normal sections. For the purposes of the following
-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.
+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.
 The letter <code>'G'</code> in parentheses indicates that a parameter is
-specific to the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section. The letter <code>'S'</code>
+specific to the <a href="../yodldocs/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="smb.conf.5.html#global"><strong>[global]</strong></a> section - in which case they will define
+<a href="../yodldocs/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
 create best bedfellows, but at least you can find them! Where there
@@ -259,7 +258,7 @@ preferred synonym.
 <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="smb.conf.5.html#path"><strong><code>"path =
+substitutions. For example the option <a href="../yodldocs/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
@@ -273,14 +272,14 @@ be relevant. These are:
 <p><br><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="smb.conf.5.html#percentu"><strong>%u</strong></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> 
 <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="smb.conf.5.html#percentU"><strong>%U</strong></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="smb.conf.5.html#percentu"><strong>%u</strong></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>
 <li > <strong>%v</strong> = the Samba version.
 <p><br><a name="percenth"></a>
@@ -297,7 +296,7 @@ personality".
 <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="smb.conf.5.html#percentL"><strong>%L</strong></a>.
+as <a href="../yodldocs/smb.conf.5.html#percentL"><strong>%L</strong></a>.
 <p><br><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".
@@ -311,7 +310,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 <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>
+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>
 <li > <strong>%I</strong> = The IP address of the client machine.
@@ -351,7 +350,7 @@ case. Default <em>Yes</em>.
 <p><br><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="smb.conf.5.html#preservecaseoption"><strong>"preserve case =
+case. This option can be use with <a href="../yodldocs/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
@@ -364,7 +363,7 @@ 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="smb.conf.5.html#guestonly"><strong>"guest only = yes"</strong></a> then
+<p><br>If the service is marked <a href="../yodldocs/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
@@ -381,17 +380,17 @@ the connection is allowed as the corresponding user.
 <p><br><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="smb.conf.5.html#revalidate"><strong>"revalidate = yes"</strong></a> for this service.
-<p><br><li> Step 5: If a <a href="smb.conf.5.html#user"><strong>"user = "</strong></a> field is given in the
+<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
 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="smb.conf.5.html#user"><strong>user=</strong></a>
+checking) with one of the usernames from the <a href="../yodldocs/smb.conf.5.html#user"><strong>user=</strong></a>
 field then the connection is made as the username in the
-<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
+<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
 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="smb.conf.5.html#guestaccount"><strong>"guest account
+made as the username given in the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest account
 ="</strong></a> for the service, irrespective of the supplied
 password.
 <p><br></ol>
@@ -401,154 +400,162 @@ password.
 <p><br>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="smb.conf.5.html#adduserscript"><strong>add user script</strong></a>
-<p><br><li > <a href="smb.conf.5.html#allowtrusteddomains"><strong>allow trusted domains</strong></a>
-<p><br><li > <a href="smb.conf.5.html#announceas"><strong>announce as</strong></a>
-<p><br><li > <a href="smb.conf.5.html#announceversion"><strong>announce version</strong></a>
-<p><br><li > <a href="smb.conf.5.html#autoservices"><strong>auto services</strong></a>
-<p><br><li > <a href="smb.conf.5.html#bindinterfacesonly"><strong>bind interfaces only</strong></a>
-<p><br><li > <a href="smb.conf.5.html#browselist"><strong>browse list</strong></a>
-<p><br><li > <a href="smb.conf.5.html#changenotifytimeout"><strong>change notify timeout</strong></a>
-<p><br><li > <a href="smb.conf.5.html#characterset"><strong>character set</strong></a>
-<p><br><li > <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>
-<p><br><li > <a href="smb.conf.5.html#codingsystem"><strong>coding system</strong></a>
-<p><br><li > <a href="smb.conf.5.html#configfile"><strong>config file</strong></a>
-<p><br><li > <a href="smb.conf.5.html#deadtime"><strong>deadtime</strong></a>
-<p><br><li > <a href="smb.conf.5.html#debughirestimestamp"><strong>debug hires timestamp</strong></a>
-<p><br><li > <a href="smb.conf.5.html#debugpid"><strong>debug pid</strong></a>
-<p><br><li > <a href="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
-<p><br><li > <a href="smb.conf.5.html#debuguid"><strong>debug uid</strong></a>
-<p><br><li > <a href="smb.conf.5.html#debuglevel"><strong>debuglevel</strong></a>
-<p><br><li > <a href="smb.conf.5.html#default"><strong>default</strong></a>
-<p><br><li > <a href="smb.conf.5.html#defaultservice"><strong>default service</strong></a>
-<p><br><li > <a href="smb.conf.5.html#deleteuserscript"><strong>delete user script</strong></a>
-<p><br><li > <a href="smb.conf.5.html#dfreecommand"><strong>dfree command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#dnsproxy"><strong>dns proxy</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainadmingroup"><strong>domain admin group</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainadminusers"><strong>domain admin users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domaincontroller"><strong>domain controller</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domaingroups"><strong>domain groups</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainguestgroup"><strong>domain guest group</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainguestusers"><strong>domain guest users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainlogons"><strong>domain logons</strong></a>
-<p><br><li > <a href="smb.conf.5.html#domainmaster"><strong>domain master</strong></a>
-<p><br><li > <a href="smb.conf.5.html#encryptpasswords"><strong>encrypt passwords</strong></a>
-<p><br><li > <a href="smb.conf.5.html#getwdcache"><strong>getwd cache</strong></a>
-<p><br><li > <a href="smb.conf.5.html#homedirmap"><strong>homedir map</strong></a>
-<p><br><li > <a href="smb.conf.5.html#hostsequiv"><strong>hosts equiv</strong></a>
-<p><br><li > <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a>
-<p><br><li > <a href="smb.conf.5.html#keepalive"><strong>keepalive</strong></a>
-<p><br><li > <a href="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldapfilter"><strong>ldap filter</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldapport"><strong>ldap port</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldapserver"><strong>ldap server</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ldapsuffix"><strong>ldap suffix</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lmannounce"><strong>lm announce</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lminterval"><strong>lm interval</strong></a>
-<p><br><li > <a href="smb.conf.5.html#loadprinters"><strong>load printers</strong></a>
-<p><br><li > <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lockdir"><strong>lock dir</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lockdirectory"><strong>lock directory</strong></a>
-<p><br><li > <a href="smb.conf.5.html#logfile"><strong>log file</strong></a>
-<p><br><li > <a href="smb.conf.5.html#loglevel"><strong>log level</strong></a>
-<p><br><li > <a href="smb.conf.5.html#logondrive"><strong>logon drive</strong></a>
-<p><br><li > <a href="smb.conf.5.html#logonhome"><strong>logon home</strong></a>
-<p><br><li > <a href="smb.conf.5.html#logonpath"><strong>logon path</strong></a>
-<p><br><li > <a href="smb.conf.5.html#logonscript"><strong>logon script</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lpqcachetime"><strong>lpq cache time</strong></a>
-<p><br><li > <a href="smb.conf.5.html#machinepasswordtimeout"><strong>machine password timeout</strong></a>
-<p><br><li > <a href="smb.conf.5.html#mangledstack"><strong>mangled stack</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maptoguest"><strong>map to guest</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxdisksize"><strong>max disk size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxlogsize"><strong>max log size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxmux"><strong>max mux</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxopenfiles"><strong>max open files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxpacket"><strong>max packet</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxttl"><strong>max ttl</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxwinsttl"><strong>max wins ttl</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxxmit"><strong>max xmit</strong></a>
-<p><br><li > <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#minpasswdlength"><strong>min passwd length</strong></a>
-<p><br><li > <a href="smb.conf.5.html#minwinsttl"><strong>min wins ttl</strong></a>
-<p><br><li > <a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a>
-<p><br><li > <a href="smb.conf.5.html#netbiosaliases"><strong>netbios aliases</strong></a>
-<p><br><li > <a href="smb.conf.5.html#netbiosname"><strong>netbios name</strong></a>
-<p><br><li > <a href="smb.conf.5.html#nishomedir"><strong>nis homedir</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ntaclsupport"><strong>nt acl support</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ntpipesupport"><strong>nt pipe support</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ntsmbsupport"><strong>nt smb support</strong></a>
-<p><br><li > <a href="smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a>
-<p><br><li > <a href="smb.conf.5.html#olelockingcompatibility"><strong>ole locking compatibility</strong></a>
-<p><br><li > <a href="smb.conf.5.html#oplockbreakwaittime"><strong>oplock break wait time</strong></a>
-<p><br><li > <a href="smb.conf.5.html#oslevel"><strong>os level</strong></a>
-<p><br><li > <a href="smb.conf.5.html#packetsize"><strong>packet size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#panicaction"><strong>panic action</strong></a>
-<p><br><li > <a href="smb.conf.5.html#passwdchat"><strong>passwd chat</strong></a>
-<p><br><li > <a href="smb.conf.5.html#passwdchatdebug"><strong>passwd chat debug</strong></a>
-<p><br><li > <a href="smb.conf.5.html#passwdprogram"><strong>passwd program</strong></a>
-<p><br><li > <a href="smb.conf.5.html#passwordlevel"><strong>password level</strong></a>
-<p><br><li > <a href="smb.conf.5.html#passwordserver"><strong>password server</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preferedmaster"><strong>prefered master</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preferredmaster"><strong>preferred master</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preload"><strong>preload</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printcap"><strong>printcap</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printcapname"><strong>printcap name</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printerdriverfile"><strong>printer driver file</strong></a>
-<p><br><li > <a href="smb.conf.5.html#protocol"><strong>protocol</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readbmpx"><strong>read bmpx</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readprediction"><strong>read prediction</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readraw"><strong>read raw</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readsize"><strong>read size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#remoteannounce"><strong>remote announce</strong></a>
-<p><br><li > <a href="smb.conf.5.html#remotebrowsesync"><strong>remote browse sync</strong></a>
-<p><br><li > <a href="smb.conf.5.html#restrictanonymous"><strong>restrict anonymous</strong></a>
-<p><br><li > <a href="smb.conf.5.html#root"><strong>root</strong></a>
-<p><br><li > <a href="smb.conf.5.html#rootdir"><strong>root dir</strong></a>
-<p><br><li > <a href="smb.conf.5.html#rootdirectory"><strong>root directory</strong></a>
-<p><br><li > <a href="smb.conf.5.html#security"><strong>security</strong></a>
-<p><br><li > <a href="smb.conf.5.html#serverstring"><strong>server string</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sharedmemsize"><strong>shared mem size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#smbpasswdfile"><strong>smb passwd file</strong></a>
-<p><br><li > <a href="smb.conf.5.html#smbrun"><strong>smbrun</strong></a>
-<p><br><li > <a href="smb.conf.5.html#socketaddress"><strong>socket address</strong></a>
-<p><br><li > <a href="smb.conf.5.html#socketoptions"><strong>socket options</strong></a>
-<p><br><li > <a href="smb.conf.5.html#ssl"><strong>ssl</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslCAcertDir"><strong>ssl CA certDir</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslCAcertFile"><strong>ssl CA certFile</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslciphers"><strong>ssl ciphers</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslclientcert"><strong>ssl client cert</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslclientkey"><strong>ssl client key</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslcompatibility"><strong>ssl compatibility</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslhosts"><strong>ssl hosts</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslhostsresign"><strong>ssl hosts resign</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslrequireclientcert"><strong>ssl require clientcert</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslrequireservercert"><strong>ssl require servercert</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslservercert"><strong>ssl server cert</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslserverkey"><strong>ssl server key</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sslversion"><strong>ssl version</strong></a>
-<p><br><li > <a href="smb.conf.5.html#statcache"><strong>stat cache</strong></a>
-<p><br><li > <a href="smb.conf.5.html#statcachesize"><strong>stat cache size</strong></a>
-<p><br><li > <a href="smb.conf.5.html#stripdot"><strong>strip dot</strong></a>
-<p><br><li > <a href="smb.conf.5.html#syslog"><strong>syslog</strong></a>
-<p><br><li > <a href="smb.conf.5.html#syslogonly"><strong>syslog only</strong></a>
-<p><br><li > <a href="smb.conf.5.html#timeoffset"><strong>time offset</strong></a>
-<p><br><li > <a href="smb.conf.5.html#timeserver"><strong>time server</strong></a>
-<p><br><li > <a href="smb.conf.5.html#timestamplogs"><strong>timestamp logs</strong></a>
-<p><br><li > <a href="smb.conf.5.html#unixpasswordsync"><strong>unix password sync</strong></a>
-<p><br><li > <a href="smb.conf.5.html#unixrealname"><strong>unix realname</strong></a>
-<p><br><li > <a href="smb.conf.5.html#updateencrypted"><strong>update encrypted</strong></a>
-<p><br><li > <a href="smb.conf.5.html#userhosts"><strong>use rhosts</strong></a>
-<p><br><li > <a href="smb.conf.5.html#usernamelevel"><strong>username level</strong></a>
-<p><br><li > <a href="smb.conf.5.html#usernamemap"><strong>username map</strong></a>
-<p><br><li > <a href="smb.conf.5.html#validchars"><strong>valid chars</strong></a>
-<p><br><li > <a href="smb.conf.5.html#winsproxy"><strong>wins proxy</strong></a>
-<p><br><li > <a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a>
-<p><br><li > <a href="smb.conf.5.html#winshook"><strong>wins hook</strong></a>
-<p><br><li > <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>
-<p><br><li > <a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a>
-<p><br><li > <a href="smb.conf.5.html#writeraw"><strong>write raw</strong></a>
+<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>
 <h2>COMPLETE LIST OF SERVICE PARAMETERS</h2>
@@ -556,116 +563,119 @@ parameter for details.  Note that some are synonyms.
 <p><br>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="smb.conf.5.html#adminusers"><strong>admin users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#allowhosts"><strong>allow hosts</strong></a>
-<p><br><li > <a href="smb.conf.5.html#alternatepermissions"><strong>alternate permissions</strong></a>
-<p><br><li > <a href="smb.conf.5.html#available"><strong>available</strong></a>
-<p><br><li > <a href="smb.conf.5.html#blockinglocks"><strong>blocking locks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#browsable"><strong>browsable</strong></a>
-<p><br><li > <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a>
-<p><br><li > <a href="smb.conf.5.html#casesensitive"><strong>case sensitive</strong></a>
-<p><br><li > <a href="smb.conf.5.html#casesignames"><strong>casesignames</strong></a>
-<p><br><li > <a href="smb.conf.5.html#comment"><strong>comment</strong></a>
-<p><br><li > <a href="smb.conf.5.html#copy"><strong>copy</strong></a>
-<p><br><li > <a href="smb.conf.5.html#createmask"><strong>create mask</strong></a>
-<p><br><li > <a href="smb.conf.5.html#createmode"><strong>create mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#defaultcase"><strong>default case</strong></a>
-<p><br><li > <a href="smb.conf.5.html#deletereadonly"><strong>delete readonly</strong></a>
-<p><br><li > <a href="smb.conf.5.html#deletevetofiles"><strong>delete veto files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#denyhosts"><strong>deny hosts</strong></a>
-<p><br><li > <a href="smb.conf.5.html#directory"><strong>directory</strong></a>
-<p><br><li > <a href="smb.conf.5.html#directorymask"><strong>directory mask</strong></a>
-<p><br><li > <a href="smb.conf.5.html#directorymode"><strong>directory mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#directorysecuritymask"><strong>directory security mask</strong></a>
-<p><br><li > <a href="smb.conf.5.html#dontdescend"><strong>dont descend</strong></a>
-<p><br><li > <a href="smb.conf.5.html#dosfiletimeresolution"><strong>dos filetime resolution</strong></a>
-<p><br><li > <a href="smb.conf.5.html#dosfiletimes"><strong>dos filetimes</strong></a>
-<p><br><li > <a href="smb.conf.5.html#exec"><strong>exec</strong></a>
-<p><br><li > <a href="smb.conf.5.html#fakedirectorycreatetimes"><strong>fake directory create times</strong></a>
-<p><br><li > <a href="smb.conf.5.html#fakeoplocks"><strong>fake oplocks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#followsymlinks"><strong>follow symlinks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forcedirectorysecuritymode"><strong>force directory security mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forcegroup"><strong>force group</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forcesecuritymode"><strong>force security mode</strong></a>
-<p><br><li > <a href="smb.conf.5.html#forceuser"><strong>force user</strong></a>
-<p><br><li > <a href="smb.conf.5.html#fstype"><strong>fstype</strong></a>
-<p><br><li > <a href="smb.conf.5.html#group"><strong>group</strong></a>
-<p><br><li > <a href="smb.conf.5.html#guestaccount"><strong>guest account</strong></a>
-<p><br><li > <a href="smb.conf.5.html#guestok"><strong>guest ok</strong></a>
-<p><br><li > <a href="smb.conf.5.html#guestonly"><strong>guest only</strong></a>
-<p><br><li > <a href="smb.conf.5.html#hidedotfiles"><strong>hide dot files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#hidefiles"><strong>hide files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>
-<p><br><li > <a href="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>
-<p><br><li > <a href="smb.conf.5.html#include"><strong>include</strong></a>
-<p><br><li > <a href="smb.conf.5.html#invalidusers"><strong>invalid users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#level2oplocks"><strong>level2 oplocks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#locking"><strong>locking</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lppausecommand"><strong>lppause command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lpqcommand"><strong>lpq command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lpresumecommand"><strong>lpresume command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#lprmcommand"><strong>lprm command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#magicoutput"><strong>magic output</strong></a>
-<p><br><li > <a href="smb.conf.5.html#magicscript"><strong>magic script</strong></a>
-<p><br><li > <a href="smb.conf.5.html#manglecase"><strong>mangle case</strong></a>
-<p><br><li > <a href="smb.conf.5.html#manglelocks"><strong>mangle locks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#mangledmap"><strong>mangled map</strong></a>
-<p><br><li > <a href="smb.conf.5.html#manglednames"><strong>mangled names</strong></a>
-<p><br><li > <a href="smb.conf.5.html#manglingchar"><strong>mangling char</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maparchive"><strong>map archive</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maphidden"><strong>map hidden</strong></a>
-<p><br><li > <a href="smb.conf.5.html#mapsystem"><strong>map system</strong></a>
-<p><br><li > <a href="smb.conf.5.html#maxconnections"><strong>max connections</strong></a>
-<p><br><li > <a href="smb.conf.5.html#minprintspace"><strong>min print space</strong></a>
-<p><br><li > <a href="smb.conf.5.html#onlyguest"><strong>only guest</strong></a>
-<p><br><li > <a href="smb.conf.5.html#onlyuser"><strong>only user</strong></a>
-<p><br><li > <a href="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
-<p><br><li > <a href="smb.conf.5.html#oplockcontentionlimit"><strong>oplock contention limit</strong></a>
-<p><br><li > <a href="smb.conf.5.html#path"><strong>path</strong></a>
-<p><br><li > <a href="smb.conf.5.html#postexec"><strong>postexec</strong></a>
-<p><br><li > <a href="smb.conf.5.html#postscript"><strong>postscript</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preexec"><strong>preexec</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preexecclose"><strong>preexec close</strong></a>
-<p><br><li > <a href="smb.conf.5.html#preservecase"><strong>preserve case</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printcommand"><strong>print command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printok"><strong>print ok</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printable"><strong>printable</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printer"><strong>printer</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printerdriver"><strong>printer driver</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printerdriverlocation"><strong>printer driver location</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printername"><strong>printer name</strong></a>
-<p><br><li > <a href="smb.conf.5.html#printing"><strong>printing</strong></a>
-<p><br><li > <a href="smb.conf.5.html#public"><strong>public</strong></a>
-<p><br><li > <a href="smb.conf.5.html#queuepausecommand"><strong>queuepause command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#queueresumecommand"><strong>queueresume command</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readlist"><strong>read list</strong></a>
-<p><br><li > <a href="smb.conf.5.html#readonly"><strong>read only</strong></a>
-<p><br><li > <a href="smb.conf.5.html#revalidate"><strong>revalidate</strong></a>
-<p><br><li > <a href="smb.conf.5.html#rootpostexec"><strong>root postexec</strong></a>
-<p><br><li > <a href="smb.conf.5.html#rootpreexec"><strong>root preexec</strong></a>
-<p><br><li > <a href="smb.conf.5.html#securitymask"><strong>security mask</strong></a>
-<p><br><li > <a href="smb.conf.5.html#rootpreexecclose"><strong>root preexec close</strong></a>
-<p><br><li > <a href="smb.conf.5.html#setdirectory"><strong>set directory</strong></a>
-<p><br><li > <a href="smb.conf.5.html#sharemodes"><strong>share modes</strong></a>
-<p><br><li > <a href="smb.conf.5.html#shortpreservecase"><strong>short preserve case</strong></a>
-<p><br><li > <a href="smb.conf.5.html#status"><strong>status</strong></a>
-<p><br><li > <a href="smb.conf.5.html#strictlocking"><strong>strict locking</strong></a>
-<p><br><li > <a href="smb.conf.5.html#strictsync"><strong>strict sync</strong></a>
-<p><br><li > <a href="smb.conf.5.html#syncalways"><strong>sync always</strong></a>
-<p><br><li > <a href="smb.conf.5.html#user"><strong>user</strong></a>
-<p><br><li > <a href="smb.conf.5.html#username"><strong>username</strong></a>
-<p><br><li > <a href="smb.conf.5.html#users"><strong>users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#validusers"><strong>valid users</strong></a>
-<p><br><li > <a href="smb.conf.5.html#vetofiles"><strong>veto files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#vetooplockfiles"><strong>veto oplock files</strong></a>
-<p><br><li > <a href="smb.conf.5.html#volume"><strong>volume</strong></a>
-<p><br><li > <a href="smb.conf.5.html#widelinks"><strong>wide links</strong></a>
-<p><br><li > <a href="smb.conf.5.html#writable"><strong>writable</strong></a>
-<p><br><li > <a href="smb.conf.5.html#writelist"><strong>write list</strong></a>
-<p><br><li > <a href="smb.conf.5.html#writeok"><strong>write ok</strong></a>
-<p><br><li > <a href="smb.conf.5.html#writeable"><strong>writeable</strong></a>
+<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>
 <h2>EXPLANATION OF EACH PARAMETER</h2>
@@ -684,14 +694,14 @@ onerous task. This option allows <a href="smbd.8.html"><strong>smbd</strong></a>
 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="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>
+<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>
 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
 <em>"login"</em>(session setup in the SMB protocol) time,
-<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password
+<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="../yodldocs/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
@@ -703,9 +713,9 @@ to be the user name to create.
 <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="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
+<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
 script</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	add user script = &lt;empty string&gt;</code>
@@ -725,10 +735,10 @@ file permissions.
 <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="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a>.
+<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="smb.conf.5.html#security"><strong>security</strong></a>
+<p><br>This option only takes effect when the <a href="../yodldocs/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
@@ -781,7 +791,7 @@ to be a downlevel server.
 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="smb.conf.5.html#loadprinters"><strong>"load printers"</strong></a> option is easier.
+then the <a href="../yodldocs/smb.conf.5.html#loadprinters"><strong>"load printers"</strong></a> option is easier.
 <p><br><strong>Default:</strong>
 <code>	no auto services</code>
 <p><br><strong>Example:</strong>
@@ -803,7 +813,7 @@ on a machine will serve smb requests. If affects file service
 in slightly different ways.
 <p><br>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="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a>
+<a href="../yodldocs/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
@@ -812,22 +822,22 @@ 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="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list. As unicast packets
+<a href="../yodldocs/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="smb.conf.5.html#interfaces"><strong>"interfaces"</strong></a> list.  IP Source address spoofing
+<a href="../yodldocs/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="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a>
+the interface list given in the <a href="../yodldocs/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="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter
+<em>127.0.0.1</em> is added to the <a href="../yodldocs/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.
@@ -835,7 +845,7 @@ reasons covered below.
 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="smb.conf.5.html#interfaces"><strong>'interfaces'</strong></a> parameter list then
+<a href="../yodldocs/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
@@ -872,7 +882,7 @@ request immediately if the lock range cannot be obtained.
 <code>	blocking locks = False</code>
 <p><br><a name="browsable"></a>
 <li><strong><strong>browsable (S)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#browseable"><strong>browseable</strong></a>.
+<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
@@ -889,11 +899,11 @@ shares in a net view and in the browse list.
 <p><br><strong>Example:</strong>
 <code>	browseable = No</code>
 <p><br><a name="casesensitive"></a>
-<li><strong><strong>case sensitive (G)</strong></strong>
-<p><br>See the discussion in the section <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></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 (G)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></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
@@ -912,38 +922,38 @@ requested directory once every <strong>change notify timeout</strong> seconds.
 <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="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> parameter) to several
+the <a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
+<a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
+<a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
+<a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a> <em>MUST</em> be set to code
+<a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>client code
+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 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
 be dynamic, like the loading of MS DOS code pages, not static.
-<p><br>See also <a href="smb.conf.5.html#clientcodepage"><strong>client code page</strong></a>.  Normally this
+<p><br>See also <a href="../yodldocs/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>
 <code>	character set = &lt;empty string&gt;</code>
@@ -982,16 +992,16 @@ 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="smb.conf.5.html#validchars"><strong>"valid
+<p><br>This parameter co-operates with the <a href="../yodldocs/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="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a> parameter
+this parameter and the <a href="../yodldocs/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="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
+<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
 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="smb.conf.5.html#validchars"><strong>"valid chars"</strong></a>
+<p><br>See also : <a href="../yodldocs/smb.conf.5.html#validchars"><strong>"valid chars"</strong></a>
 <p><br><strong>Default:</strong>
 <code>	client code page = 850</code>
 <p><br><strong>Example:</strong>
@@ -999,9 +1009,9 @@ the character settings in the "client code page" parameter.
 <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="smb.conf.5.html#clientcodepage"><strong>"client code
+characters are mapped from the incoming <a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>"client code
+UNIX filesystem. Only useful if <a href="../yodldocs/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>
@@ -1060,7 +1070,7 @@ in the configuration file than the service doing the copying.
 <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="smb.conf.5.html#createmode"><strong>'create mode'</strong></a>.
+<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
 according to the mapping from DOS modes to UNIX permissions, and the
 resulting UNIX mode is then bit-wise 'AND'ed with this parameter.
@@ -1073,18 +1083,19 @@ write and execute bits from the UNIX modes.
 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="smb.conf.5.html#directorymode"><strong>'directory mode'</strong></a> for details.
-<p><br>See also the <a href="smb.conf.5.html#forcecreatemode"><strong>"force create mode"</strong></a> 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
 for forcing particular mode bits to be set on created files. See also
-the <a href="smb.conf.5.html#directorymode"><strong>"directory mode"</strong></a> parameter for masking
+the <a href="../yodldocs/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>
 <code>	create mask = 0744</code>
 <p><br><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="smb.conf.5.html#createmask"><strong>create mask</strong></a>.
+<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
@@ -1108,7 +1119,7 @@ performed.
 <p><br>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="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
+<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
 must be on for this to have an effect.
 <p><br><strong>Default:</strong>
 <code> debug hires timestamp = No</code>
@@ -1117,8 +1128,8 @@ must be on for this to have an effect.
 <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="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> these timestamps
-can be distracting. This boolean parameter allows them to be turned
+running at a high <a href="../yodldocs/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>
 <code>	debug timestamp = Yes</code>
@@ -1130,7 +1141,7 @@ off.
 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="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
+<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
 must be on for this to have an effect.
 <p><br><strong>Default:</strong>
 <code>	debug pid = No</code>
@@ -1141,7 +1152,7 @@ must be on for this to have an effect.
 <p><br>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="smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
+<p><br>Note that the parameter <a href="../yodldocs/smb.conf.5.html#debugtimestamp"><strong>debug timestamp</strong></a>
 must be on for this to have an effect.
 <p><br><strong>Default:</strong>
 <code>	debug uid = No</code>
@@ -1158,11 +1169,11 @@ or level zero if none was specified.
 <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="smb.conf.5.html#defaultservice"><strong>default service</strong></a>.
+<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="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><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
@@ -1172,11 +1183,11 @@ below).
 <p><br>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="smb.conf.5.html#guestok"><strong>guest ok</strong></a>,
-<a href="smb.conf.5.html#readonly"><strong>read-only</strong></a> service.
+<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
 of the requested service, this is very useful as it allows you to use
-macros like <a href="smb.conf.5.html#percentS"><strong>%S</strong></a> to make a wildcard service.
+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
 in the default service will get mapped to a <code>'/'</code>. This allows for
 interesting things.
@@ -1203,21 +1214,21 @@ onerous task. This option allows <a href="smbd.8.html"><strong>smbd</strong></a>
 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="smb.conf.5.html#securityequaldomain"><strong>security=domain</strong></a> and <strong>"delete user
+<a href="../yodldocs/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="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
+<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
 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="smb.conf.5.html#securityequalserver"><strong>security=server</strong></a> mode a missing user
+<a href="../yodldocs/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
 <em>"login"</em>(session setup in the SMB protocol) time,
-<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="smb.conf.5.html#passwordserver"><strong>password
+<a href="smbd.8.html"><strong>smbd</strong></a> contacts the <a href="../yodldocs/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
@@ -1228,8 +1239,8 @@ call the specified script <em>AS ROOT</em>, expanding any <strong>%u</strong> ar
 to be the user name to delete.
 <p><br>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="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
+<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
 script</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	delete user script = &lt;empty string&gt;</code>
@@ -1249,7 +1260,7 @@ semantics prevent deletion of a read only file.
 <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="smb.conf.5.html#vetofiles"><strong>'veto
+that contains one or more vetoed directories (see the <a href="../yodldocs/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
@@ -1262,14 +1273,14 @@ DOS/Windows users from seeing (e.g. <code>.AppleDouble</code>)
 <p><br>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="smb.conf.5.html#vetofiles"><strong>veto files</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>veto files</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	delete veto files = False</code>
 <p><br><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="smb.conf.5.html#hostsdeny"><strong>hosts deny</strong></a>.
+<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
@@ -1315,7 +1326,7 @@ and remaining space will be used.</code>
 path names on some systems.
 <p><br><a name="directory"></a>
 <li><strong><strong>directory (S)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#path"><strong>path</strong></a>.
+<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
@@ -1333,18 +1344,19 @@ directory to modify it.
 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="smb.conf.5.html#forcedirectorymode"><strong>"force directory mode"</strong></a> parameter
+<p><br>See the <a href="../yodldocs/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="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>
+<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>
 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>
 <code>	directory mask = 0755</code>
 <p><br><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="smb.conf.5.html#directorymask"><strong>directory mask</strong></a>.
+<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
@@ -1355,16 +1367,16 @@ 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="smb.conf.5.html#directorymask"><strong>directory mask</strong></a> parameter. To allow a user to
+<a href="../yodldocs/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
 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="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>
+<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>
 parameters.
 <p><br><strong>Default:</strong>
 <code>	directory security mask = &lt;same as directory mask&gt;</code>
@@ -1382,7 +1394,7 @@ 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
 DNS name lookup requests, as doing a name lookup is a blocking action.
-<p><br>See also the parameter <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>.
+<p><br>See also the parameter <a href="../yodldocs/smb.conf.5.html#winssupport"><strong>wins support</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	dns proxy = yes</code>
 <p><br><a name="domainadmingroup"></a>
@@ -1401,11 +1413,6 @@ 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="domaincontroller"></a>
-<li><strong><strong>domain controller (G)</strong></strong>
-<p><br>This is a <strong>DEPRECATED</strong> parameter. It is currently not used within
-the Samba source and should be removed from all current smb.conf
-files. It is left behind for compatibility reasons.
 <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
@@ -1433,7 +1440,7 @@ mailing list <strong>Samba-ntdom</strong> available by sending email to
 <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="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> it is in. For more
+logons for the <a href="../yodldocs/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
@@ -1449,20 +1456,20 @@ also.
 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="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
+<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
 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="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> specific special NetBIOS
+claim this <a href="../yodldocs/smb.conf.5.html#workgroup"><strong>workgroup</strong></a> specific special NetBIOS
 name that identifies them as domain master browsers for that
-<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> by default (i.e. there is no way to
+<a href="../yodldocs/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="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> before a Windows NT
+special name for a <a href="../yodldocs/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>
@@ -1528,13 +1535,13 @@ shipped with the source code.
 <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="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="../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="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="smb.conf.5.html#preexec"><strong>preexec</strong></a>.
+<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
@@ -1573,7 +1580,7 @@ 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
 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="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
+<p><br>It is generally much better to use the real <a href="../yodldocs/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
 know will only be accessed from one client at a time such as
@@ -1596,13 +1603,15 @@ 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
-<em>*always*</em> be set on a file created by Samba. This is done by
-bitwise 'OR'ing these bits onto the mode bits of a file that is being
-created. 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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> parameter is applied.
-<p><br>See also the parameter <a href="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> for details
-on masking mode bits on created files.
+<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
+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
+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>
 <code>	force create mode = 000</code>
 <p><br><strong>Example:</strong>
@@ -1618,9 +1627,10 @@ 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="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> is applied.
-<p><br>See also the parameter <a href="smb.conf.5.html#directorymask"><strong>"directory mask"</strong></a> for
+<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
 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>
 <code>	force directory mode = 000</code>
 <p><br><strong>Example:</strong>
@@ -1639,15 +1649,15 @@ 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="smb.conf.5.html#forcedirectorymode"><strong>force directory mode</strong></a> parameter. To allow
+<a href="../yodldocs/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
 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="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
+<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
 mode</strong></a> parameters.
 <p><br><strong>Default:</strong>
 <code>	force directory security mode = &lt;same as force directory mode&gt;</code>
@@ -1673,10 +1683,10 @@ 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="smb.conf.5.html#forceuser"><strong>"force user"</strong></a> parameter is also set the
+<p><br>If the <a href="../yodldocs/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="smb.conf.5.html#forceuser"><strong>"force user"</strong></a>.
-<p><br>See also <a href="smb.conf.5.html#forceuser"><strong>"force user"</strong></a>
+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>
 <code>	no forced group</code>
 <p><br><strong>Example:</strong>
@@ -1692,16 +1702,16 @@ 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="smb.conf.5.html#forcecreatemode"><strong>force create mode</strong></a> parameter. To allow
+<a href="../yodldocs/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
 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="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>
+<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>
 parameters.
 <p><br><strong>Default:</strong>
 <code>	force security mode = &lt;same as force create mode&gt;</code>
@@ -1722,7 +1732,7 @@ password. Once connected, all file operations will be performed as the
 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="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>
 <p><br><strong>Default:</strong>
 <code>	no forced user</code>
 <p><br><strong>Example:</strong>
@@ -1744,18 +1754,18 @@ Windows NT but this can be changed to other strings such as "Samba" or
 <p><br>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="smb.conf.5.html#widelinks"><strong>widelinks</strong></a> parameter is set to False.
+<a href="../yodldocs/smb.conf.5.html#widelinks"><strong>widelinks</strong></a> parameter is set to False.
 <p><br><strong>Default:</strong>
 <code>	getwd cache = No</code>
 <p><br><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="smb.conf.5.html#forcegroup"><strong>"force group"</strong></a>.
+<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="smb.conf.5.html#guestok"><strong>'guest ok'</strong></a> (see below). Whatever
+specified as <a href="../yodldocs/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
@@ -1774,8 +1784,8 @@ command) and trying to print using the system print command such as
 <li><strong><strong>guest ok (S)</strong></strong>
 <p><br>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="smb.conf.5.html#guestaccount"><strong>guest account</strong></a>.
-<p><br>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more
+<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
 information about this option.
 <p><br><strong>Default:</strong>
 <code>	guest ok = no</code>
@@ -1785,9 +1795,9 @@ information about this option.
 <li><strong><strong>guest only (S)</strong></strong>
 <p><br>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="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a> or <a href="smb.conf.5.html#public"><strong>"public"</strong></a>
+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>
 is not set for the service.
-<p><br>See the section below on <a href="smb.conf.5.html#security"><strong>security</strong></a> for more
+<p><br>See the section below on <a href="../yodldocs/smb.conf.5.html#security"><strong>security</strong></a> for more
 information about this option.
 <p><br><strong>Default:</strong>
 <code>	guest only = no</code>
@@ -1815,8 +1825,8 @@ Unix directory separator <code>'/'</code>.
 <p><br>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="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><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>
 <pre>
 
@@ -1832,8 +1842,8 @@ files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case se
 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="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
+<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
 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
@@ -1843,7 +1853,7 @@ understood. The form of the map is:
 <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="smb.conf.5.html#nishomedir"><strong>"nis homedir"</strong></a>, <a href="smb.conf.5.html#domainlogons"><strong>domain
+<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
 logons</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	homedir map = auto.home</code>
@@ -1851,10 +1861,10 @@ logons</strong></a>.
 <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="smb.conf.5.html#allowhosts"><strong>'allow hosts'</strong></a>
+<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
 are permitted to access a service.
-<p><br>If specified in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section then it will
+<p><br>If specified in the <a href="../yodldocs/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
@@ -1888,10 +1898,10 @@ host access to see if it does what you expect.
 <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="smb.conf.5.html#hostsallow"><strong>'hosts allow'</strong></a> - hosts listed
+<p><br>The opposite of <a href="../yodldocs/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="smb.conf.5.html#hostsallow"><strong>'allow'</strong></a> list takes precedence.
+conflict, the <a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>'allow'</strong></a> list takes precedence.
 <p><br><strong>Default:</strong>
 <code>	none (i.e., no hosts specifically excluded)</code>
 <p><br><strong>Example:</strong>
@@ -1901,7 +1911,7 @@ conflict, the <a href="smb.conf.5.html#hostsallow"><strong>'allow'</strong></a>
 <p><br>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="smb.conf.5.html#hostsallow"><strong>hosts allow</strong></a> which
+<p><br>This is not be confused with <a href="../yodldocs/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.
@@ -1919,8 +1929,35 @@ kids. And only if you <em>really</em> trust them :-).
 <li><strong><strong>include (G)</strong></strong>
 <p><br>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="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><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>
+but the boolean inherit permissions parameter overrides this.
+<p><br>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.
+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
+(the code explicitly prohibits this).
+<p><br>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>
+<code>   inherit permissions = no</code>
+<p><br><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
@@ -1934,10 +1971,10 @@ any of the following forms:
 <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"
-if() a IP address. In this case the netmask is determined
+<li > an IP address. In this case the netmask is determined
      from the list of interfaces obtained from the kernel
-if() a IP/mask pair. 
-if() a broadcast/mask pair. 
+<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
 class network) or a full netmask in dotted decmal form.
@@ -1949,7 +1986,7 @@ hostname resolution mechanisms.
 <p><br>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="smb.conf.5.html#bindinterfacesonly"><strong>"bind interfaces only"</strong></a>.
+<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
@@ -1968,9 +2005,9 @@ netgroup database, and the value <code>"&amp;+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="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>
+<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="smb.conf.5.html#validusers"><strong>"valid users"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#validusers"><strong>"valid users"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	No invalid users</code>
 <p><br><strong>Example:</strong>
@@ -1982,7 +2019,7 @@ seconds between <strong>'keepalive'</strong> packets. If this parameter is zero,
 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="smb.conf.5.html#socketoptions"><strong>"socket
+has the SO_KEEPALIVE attribute set on it (see <a href="../yodldocs/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>
@@ -1991,10 +2028,10 @@ if you strike difficulties.
 <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="smb.conf.5.html#oplocks"><strong>oplocks</strong></a>
+<p><br>For UNIXs that support kernel based <a href="../yodldocs/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="smb.conf.5.html#oplocks"><strong>oplocks</strong></a> to be
+<p><br>Kernel oplocks support allows Samba <a href="../yodldocs/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
@@ -2002,7 +2039,7 @@ data consistency between SMB/CIFS, NFS and local file access (and is a
 <p><br>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="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#level2oplocks"><strong>"level2 oplocks"</strong></a>
+<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>
 parameters.
 <p><br><a name="ldapfilter"></a>
 <li><strong><strong>ldap filter (G)</strong></strong>
@@ -2012,7 +2049,7 @@ 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
 user name in the LDAP database. It must contain the string
-<a href="smb.conf.5.html#percentU"><strong>%u</strong></a> which will be replaced with the user being
+<a href="../yodldocs/smb.conf.5.html#percentU"><strong>%u</strong></a> which will be replaced with the user being
 searched for.
 <p><br><strong>Default:</strong>
 <code>	empty string.</code>
@@ -2035,7 +2072,7 @@ the <strong>--with-ldap</strong> option.
 <p><br>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="smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#ldaprootpasswd"><strong>ldap root passwd</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	empty string (no user defined)</code>
 <p><br><a name="ldaprootpasswd"></a>
@@ -2050,7 +2087,7 @@ 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
 in the <strong>smb.conf</strong> file and will be removed once a correct
 storage place is found.
-<p><br>See also <a href="smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#ldaproot"><strong>ldap root</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	empty string.</code>
 <p><br><a name="ldapserver"></a>
@@ -2077,7 +2114,7 @@ for an entry in the LDAP password database.
 <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
-level2 (read-only) oplocks on a share. In Samba 2.0.4 this parameter
+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
@@ -2095,12 +2132,12 @@ read-ahead caches.
 <p><br>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="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> are supported
+<p><br>Currently, if <a href="../yodldocs/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="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> parameter must
+to <code>"true"</code>). Note also, the <a href="../yodldocs/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="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a> and <a href="smb.conf.5.html#kerneloplocks"><strong>"kernel oplocks"</strong></a> parameters.
+<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>
 <code> level2 oplocks = False</code>
 <p><br><strong>Example:</strong>
@@ -2113,12 +2150,12 @@ 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="smb.conf.5.html#lminterval"><strong>"lm
+announce broadcasts at a frequency set by the parameter <a href="../yodldocs/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="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></a>.
-<p><br>See also <a href="smb.conf.5.html#lminterval"><strong>"lm interval"</strong></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>
 <code>	lm announce = auto</code>
 <p><br><strong>Example:</strong>
@@ -2126,12 +2163,12 @@ frequency set by the parameter <a href="smb.conf.5.html#lminterval"><strong>"lm
 <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="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>
+<strong>OS/2</strong> clients (see the <a href="../yodldocs/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="smb.conf.5.html#lmannounce"><strong>"lm
+announcements will be made despite the setting of the <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>"lm
 announce"</strong></a> parameter.
-<p><br>See also <a href="smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#lmannounce"><strong>"lm announce"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	lm interval = 60</code>
 <p><br><strong>Example:</strong>
@@ -2140,7 +2177,7 @@ announce"</strong></a> parameter.
 <li><strong><strong>load printers (G)</strong></strong>
 <p><br>A boolean variable that controls whether all printers in the printcap
 will be loaded for browsing by default. See the
-<a href="smb.conf.5.html#printers"><strong>"printers"</strong></a> section for more details.
+<a href="../yodldocs/smb.conf.5.html#printers"><strong>"printers"</strong></a> section for more details.
 <p><br><strong>Default:</strong>
 <code>	load printers = yes</code>
 <p><br><strong>Example:</strong>
@@ -2161,11 +2198,11 @@ elections for local master browser.
 <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="smb.conf.5.html#lockdirectory"><strong>"lock directory"</strong></a>.
+<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="smb.conf.5.html#maxconnections"><strong>"max
+The lock files are used to implement the <a href="../yodldocs/smb.conf.5.html#maxconnections"><strong>"max
 connections"</strong></a> option.
 <p><br><strong>Default:</strong>
 <code>	lock directory = /tmp/samba</code>
@@ -2199,14 +2236,14 @@ separate log files for each user or machine.
 <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="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a>.
+<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="smb.conf.5.html#logonhome"><strong>"logon home"</strong></a>) and is only
+will be connected (see <a href="../yodldocs/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="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
+<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
 <p><br><strong>Example:</strong>
 <code>	logon drive = h:</code>
 <p><br><a name="logonhome"></a>
@@ -2217,8 +2254,20 @@ NT Workstation logs into a Samba PDC.  It allows you to do
 <p><br>from a command prompt, for example.
 <p><br>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
+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
+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
+<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="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
+<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
 <p><br><strong>Example:</strong>
 <code>	logon home = "\\remote_smb_server\%U"</code>
 <p><br><strong>Default:</strong>
@@ -2226,21 +2275,24 @@ separate logon scripts for each user or machine.
 <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
-(USER.DAT / USER.MAN files for Windows 95/98) are stored.
+(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
 separate logon scripts for each user or machine.  It also specifies
-the directory from which the <code>"desktop"</code>, <code>"start menu"</code>,
-<code>"network neighborhood"</code> and <code>"programs"</code> folders, and their
-contents, are loaded and displayed on your Windows 95/98 client.
+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
-preferences and directories to be loaded onto the Windows 95/98
+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 95/98 client can create the user.dat
+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
-made read-only.  It is not advisable that the USER.DAT file be made
-read-only - rename it to USER.MAN to achieve the desired effect (a
-<em>MAN</em>datory profile).
+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]
 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
@@ -2249,7 +2301,7 @@ problems).
 <p><br>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="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
+<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
 <p><br><strong>Default:</strong>
 <code> 	logon path = \\%N\%U\profile</code>
 <p><br><strong>Example:</strong>
@@ -2261,7 +2313,7 @@ separate logon scripts for each user or machine.
 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="smb.conf.5.html#path"><strong>path</strong></a> of
+the <code>[netlogon]</code> service specifies a <a href="../yodldocs/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>
@@ -2277,7 +2329,7 @@ files to be arbitrarily modified and security to be breached.
 <p><br>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="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
+<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
 <p><br><strong>Example:</strong>
 <code>	logon script = scripts\%U.bat</code>
 <p><br><a name="lppausecommand"></a>
@@ -2290,20 +2342,20 @@ 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
 <code>"%j"</code> is replaced with the job number (an integer).  On HPUX (see
-<a href="smb.conf.5.html#printing"><strong>printing=hpux</strong></a>), if the <code>"-p%p"</code> option is added
+<a href="../yodldocs/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
 lppause command as the PATH may not be available to the server.
-<p><br>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
 <p><br><strong>Default:</strong>
         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
+value of the <a href="../yodldocs/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="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</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>,
 then the default is:
 <p><br><code>	qstat -s -j%j -h</code>
 <p><br><strong>Example for HPUX:</strong>
@@ -2322,7 +2374,7 @@ previous identical <strong>lpq</strong> command will be used if the cached data
 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="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	lpq cache time = 10</code>
 <p><br><strong>Example:</strong>
@@ -2336,7 +2388,7 @@ as its only parameter and outputs printer status information.
 <p><br>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="smb.conf.5.html#printing"><strong>"printing ="</strong></a> option.
+<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
 the connection number for the printer they are requesting status
 information about. To get around this, the server reports on the first
@@ -2346,7 +2398,7 @@ connection number sent is invalid.
 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
 command</strong> as the PATH may not be available to the server.
-<p><br>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>        depends on the setting of printing =</code>
 <p><br><strong>Example:</strong>
@@ -2357,19 +2409,19 @@ command</strong> as the PATH may not be available to the server.
 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="smb.conf.5.html#lppausecommand"><strong>"lppause
+and job number to resume the print job. See also the <a href="../yodldocs/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
 <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
 command</strong> as the PATH may not be available to the server.
-<p><br>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
+<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="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>SYSV</code>, in
+value of the <a href="../yodldocs/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="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter is <code>softq</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>,
 then the default is:
 <p><br><code>	qstat -s -j%j -r</code>
 <p><br><strong>Example for HPUX:</strong>
@@ -2384,7 +2436,7 @@ and job number, and deletes the print job.
 <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>lprm command</strong> as the PATH may not be available to the server.
-<p><br>See also the <a href="smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	depends on the setting of "printing ="</code>
 <p><br><strong>Example 1:</strong>
@@ -2394,26 +2446,26 @@ and job number, and deletes the print job.
 <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="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter) then
+<a href="../yodldocs/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>&lt;Domain&gt;.&lt;Machine&gt;.mac</code> where <code>&lt;Domain&gt;</code> is the name of the
 Domain we are a member of and <code>&lt;Machine&gt;</code> is the primary
-<a href="smb.conf.5.html#netbiosname"><strong>"NetBIOS name"</strong></a> of the machine
+<a href="../yodldocs/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="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter.
+<a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>) parameter.
 <p><br><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="smb.conf.5.html#magicscript"><strong>"magic
+created by a magic script (see the <a href="../yodldocs/smb.conf.5.html#magicscript"><strong>"magic
 script"</strong></a> parameter below).
-<p><br>Warning: If two clients use the same <a href="smb.conf.5.html#magicscript"><strong>"magic
+<p><br>Warning: If two clients use the same <a href="../yodldocs/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>
@@ -2429,7 +2481,7 @@ connected user.
 <p><br>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="smb.conf.5.html#magicoutput"><strong>"magic output"</strong></a> parameter (see
+specified by the <a href="../yodldocs/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
 carriage-return-linefeed instead of linefeed as the end-of-line
@@ -2443,7 +2495,7 @@ end.
 <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="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a>.
+<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
@@ -2471,7 +2523,7 @@ this use a map of (*;1 *).
 <p><br>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="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for details
+<p><br>See the section on <a href="../yodldocs/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>
@@ -2485,14 +2537,14 @@ 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="smb.conf.5.html#manglingchar"><strong>"mangling char"</strong></a> option, if you don't like
+<a href="../yodldocs/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
 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="smb.conf.5.html#hidefiles"><strong>"hidden files"</strong></a> - see below).
+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
 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
@@ -2515,7 +2567,7 @@ change between sessions.
 <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="smb.conf.5.html#manglednames"><strong>name mangling</strong></a>. The default is a <code>'~'</code> but
+<a href="../yodldocs/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>
@@ -2547,9 +2599,9 @@ 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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
+<p><br>Note that this requires the <a href="../yodldocs/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="smb.conf.5.html#createmask"><strong>"create
+(i.e. it must include 100). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create
 mask"</strong></a> for details.
 <p><br><strong>Default:</strong>
 <code>      map archive = yes</code>
@@ -2559,9 +2611,9 @@ mask"</strong></a> for details.
 <li><strong><strong>map hidden (S)</strong></strong>
 <p><br>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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be
+<p><br>Note that this requires the <a href="../yodldocs/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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
+include 001). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
 for details.
 <p><br><strong>Default:</strong>
 <code> 	map hidden = no</code>
@@ -2571,9 +2623,9 @@ for details.
 <li><strong><strong>map system (S)</strong></strong>
 <p><br>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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a> to be
+<p><br>Note that this requires the <a href="../yodldocs/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="smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
+include 010). See the parameter <a href="../yodldocs/smb.conf.5.html#createmask"><strong>"create mask"</strong></a>
 for details.
 <p><br><strong>Default:</strong>
 <code> 	map system = no</code>
@@ -2581,8 +2633,8 @@ for details.
 <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="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,
+<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,
 server, and domain.
 <p><br>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
@@ -2593,11 +2645,11 @@ don't match a valid UNIX user in some way.
 are rejected. This is the default.
 <p><br><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="smb.conf.5.html#guestaccount"><strong>"guest
+treated as a guest login and mapped into the <a href="../yodldocs/smb.conf.5.html#guestaccount"><strong>"guest
 account"</strong></a>.
 <p><br><li > <strong>"Bad Password"</strong> - Means user logins with an invalid
 password are treated as a guest login and mapped into the
-<a href="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>. Note that this can
+<a href="../yodldocs/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
@@ -2607,7 +2659,7 @@ that they got their password wrong. Helpdesk services will
 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="smb.conf.5.html#security"><strong>security</strong></a> modes other than
+services when using <a href="../yodldocs/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
@@ -2628,7 +2680,7 @@ 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="smb.conf.5.html#lockdirectory"><strong>"lock
+will be stored in the directory specified by the <a href="../yodldocs/smb.conf.5.html#lockdirectory"><strong>"lock
 directory"</strong></a> option.
 <p><br><strong>Default:</strong>
 <code>	max connections = 0</code>
@@ -2682,7 +2734,7 @@ so you should never need to touch this parameter.
 <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 name="<strong>"packetsize"</strong>"></a>(packetsize).
+<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
@@ -2695,11 +2747,11 @@ change this parameter. The default is 3 days.
 <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="smb.conf.5.html#winssupport"><strong>(wins support =true)</strong></a> what the maximum
+server <a href="../yodldocs/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="smb.conf.5.html#minwinsttl"><strong>"min wins ttl"</strong></a> parameter.
+<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>
 <code>        max wins ttl = 518400</code>
 <p><br><a name="maxxmit"></a>
@@ -2726,8 +2778,8 @@ IMMEDIATELY</em>. That's why I have the <code>'&amp;'</code> on the end. If it d
 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="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).
+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
 particular:
 <p><br><ul>
@@ -2756,24 +2808,27 @@ on regardless, saying that the message was delivered.
 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="smb.conf.5.html#printing"><strong>printing</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#printing"><strong>printing</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	min print space = 0</code>
 <p><br><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
 than smbd will accept when performing UNIX password changing.
-<p><br>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
+<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
 debug"</strong></a>.
 <p><br><strong>Default:</strong>
-<code>	min passwd length = 5</code>
+<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="smb.conf.5.html#winssupport"><strong>(wins support = true)</strong></a> what the minimum
+server <a href="../yodldocs/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).
@@ -2799,10 +2854,10 @@ 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="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter. If no WINS server has
+<a href="../yodldocs/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="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter. This is the
+listed in the <a href="../yodldocs/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>
@@ -2817,11 +2872,11 @@ by a broadcast attempt, followed by a normal system hostname lookup.
 <p><br>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="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
+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
 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="smb.conf.5.html#netbiosname"><strong>"netbios name"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#netbiosname"><strong>"netbios name"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	empty string (no additional names)</code>
 <p><br><strong>Example:</strong>
@@ -2830,15 +2885,19 @@ name of the machine will be advertised with these capabilities.
 <li><strong><strong>netbios name (G)</strong></strong>
 <p><br>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="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
+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
 of the hosts DNS name) will be the name that these services are
 advertised under.
-<p><br>See also <a href="smb.conf.5.html#netbiosaliases"><strong>"netbios aliases"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#netbiosaliases"><strong>"netbios aliases"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	Machine DNS name.</code>
 <p><br><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
+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
@@ -2855,11 +2914,11 @@ 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="smb.conf.5.html#homedirmap"><strong>"homedir map"</strong></a> and return the server listed
+<a href="../yodldocs/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
 system and the Samba server with this option must also be a
-<a href="smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
+<a href="../yodldocs/smb.conf.5.html#domainlogons"><strong>logon server</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	nis homedir = false</code>
 <p><br><strong>Example:</strong>
@@ -2917,20 +2976,20 @@ correctly.
 <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="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a>.
+<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="smb.conf.5.html#user"><strong>user=</strong></a> list will be allowed. By
+usernames not in the <a href="../yodldocs/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="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
+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
 will be just the service name, which for home directories is the name
 of the user.
-<p><br>See also the <a href="smb.conf.5.html#user"><strong>user</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#user"><strong>user</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	only user = False</code>
 <p><br><strong>Example:</strong>
@@ -2948,10 +3007,10 @@ more information see the file Speed.txt in the Samba docs/ directory.
 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="smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> parameter
+UNIX process. See the <a href="../yodldocs/smb.conf.5.html#kerneloplocks"><strong>kernel oplocks</strong></a> parameter
 for details.
-<p><br>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><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>
 <code>	oplocks = True</code>
 <p><br><strong>Example:</strong>
@@ -2985,7 +3044,7 @@ OPLOCK CODE</em>.
 <p><br>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="smb.conf.5.html#workgroup"><strong>WORKGROUP</strong></a> in the local broadcast
+browser for the <a href="../yodldocs/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.
@@ -2995,7 +3054,7 @@ docs/ directory for details.
 <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 how no effect on the current
+<p><br>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>
@@ -3012,7 +3071,7 @@ attention to the fact that a problem occurred.
 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="smb.conf.5.html#passwdprogram"><strong>passwd</strong></a> program
+determine what to send to the <a href="../yodldocs/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
@@ -3028,13 +3087,13 @@ a single string.
 <p><br>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="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>
+<p><br>Note that if the <a href="../yodldocs/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="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
+<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
 debug"</strong></a>.
 <p><br><strong>Example:</strong> 
 <pre>
@@ -3052,13 +3111,13 @@ debug"</strong></a>.
 <p><br>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="smb.conf.5.html#debuglevel"><strong>"debug level"</strong></a> of 100. This is a dangerous
+a <a href="../yodldocs/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="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
+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
 after this has been done. This parameter is off by default.
-<p><br>See also <a href="smb.conf.5.html#passwdchat"><strong>"passwd chat"</strong></a>, <a href="smb.conf.5.html#passwdprogram"><strong>"passwd
+<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
 program"</strong></a>.
 <p><br><strong>Example:</strong>
 <code>     passwd chat debug = True</code>
@@ -3067,25 +3126,25 @@ program"</strong></a>.
 <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="smb.conf.5.html#percentu"><strong>%u</strong></a> will be replaced with the
+Any occurrences of <a href="../yodldocs/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>
 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="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>
+<p><br><em>Note</em> that if the <a href="../yodldocs/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="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> parameter is
+<p><br>If the <a href="../yodldocs/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="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> is set to
+default <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a> is set to
 <code>"False"</code>.
-<p><br>See also <a href="smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#unixpasswordsync"><strong>"unix password sync"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	passwd program = /bin/passwd</code>
 <p><br><strong>Example:</strong>
@@ -3121,15 +3180,15 @@ as is and the password in all-lower case.
 <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="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
+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
 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
 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="smb.conf.5.html#nameresolveorder"><strong>"name resolve order="</strong></a> and so may resolved
+<a href="../yodldocs/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"
 or the "LM NT 0.12" protocol, and it must be in user level security
@@ -3140,17 +3199,17 @@ SERVER THAT YOU DON'T COMPLETELY TRUST</em>.
 <p><br>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="smb.conf.5.html#percentm"><strong>%m</strong></a>, which means
+probably the only useful one is <a href="../yodldocs/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="smb.conf.5.html#security"><strong>"security"</strong></a> parameter is set to
+<p><br>If the <a href="../yodldocs/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="smb.conf.5.html#workgroup"><strong>Domain</strong></a> or the character <code>*</code>, as the Samba server is cryptographicly
+<a href="../yodldocs/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="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a> is that if you list
+<a href="../yodldocs/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.
@@ -3158,10 +3217,10 @@ that responds. This is useful in case your primary server goes down.
 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&lt;1C&gt;</code>
 and then contacting each server returned in the list of IP addresses
-from the <a href="smb.conf.5.html#nameresolveorder"><strong>name resolution</strong></a> source.
-<p><br>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>
+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>
 doesn't suffer from:
 <p><br><ul>
 <p><br><li > You may list several password servers in the <strong>"password server"</strong>
@@ -3169,16 +3228,16 @@ parameter, however if an <a href="smbd.8.html"><strong>smbd</strong></a> makes a
 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="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode
+protocol when in <a href="../yodldocs/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
 you will have to ensure that your users are able to login from the
 Samba server, as when in
-<a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> mode the network
+<a href="../yodldocs/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="smb.conf.5.html#security"><strong>"security"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#security"><strong>"security"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	password server = &lt;empty string&gt;</code>
 <p><br><strong>Example:</strong>
@@ -3195,13 +3254,13 @@ printing.
 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="smb.conf.5.html#percentu"><strong>%u</strong></a> in the path will be replaced
+<p><br>Any occurrences of <a href="../yodldocs/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="smb.conf.5.html#percentm"><strong>%m</strong></a> will be replaced
+connection. Any occurrences of <a href="../yodldocs/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="smb.conf.5.html#rootdir"><strong>"root dir"</strong></a> if
+<p><br>Note that this path will be based on <a href="../yodldocs/smb.conf.5.html#rootdir"><strong>"root dir"</strong></a> if
 one was specified.
 <p><br><strong>Default:</strong>
 <code>	none</code>
@@ -3214,7 +3273,7 @@ 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="smb.conf.5.html#preexec"><strong>preexec</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#preexec"><strong>preexec</strong></a>.
 <p><br><strong>Default:</strong>
 <code>      none (no command executed)</code>
 <p><br><strong>Example:</strong>
@@ -3243,7 +3302,7 @@ time they log in. Maybe a message of the day? Here is an example:
 </pre>
 
 <p><br>Of course, this could get annoying after a while :-)
-<p><br>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><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>
 <code>	none (no command executed)</code>
 <p><br><strong>Example:</strong>
@@ -3251,7 +3310,7 @@ time they log in. Maybe a message of the day? Here is an example:
 <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="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> should close the service being connected to.
+<a href="../yodldocs/smb.conf.5.html#preexec"><strong>"preexec"</strong></a> should close the service being connected to.
 <p><br><strong>Default:</strong>
 <code> 	preexec close = no</code>
 <p><br><strong>Example:</strong>
@@ -3263,7 +3322,7 @@ 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
 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="smb.conf.5.html#domainmaster"><strong>"domain master = yes"</strong></a>, so
+conjunction with <a href="../yodldocs/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
@@ -3272,25 +3331,25 @@ 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="smb.conf.5.html#oslevel"><strong>os level</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#oslevel"><strong>os level</strong></a>.
 <p><br><strong>Default:</strong>
 <code> 	preferred master = no</code>
 <p><br><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="smb.conf.5.html#preferredmaster"><strong>"preferred master"</strong></a> for people
+<p><br>Synonym for <a href="../yodldocs/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="smb.conf.5.html#autoservices"><strong>"auto services"</strong></a>.
+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
 client passes, or if they are forced to be the <code>"default"</code> case.
 <p><br><strong>Default:</strong>
 <code>       preserve case = yes</code>
-<p><br>See the section on <a href="smb.conf.5.html#NAMEMANGLING"><strong>"NAME MANGLING"</strong></a> for a
+<p><br>See the section on <a href="../yodldocs/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>
@@ -3302,20 +3361,16 @@ 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,
-with two exceptions: All occurrences of <code>"%s"</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 full path name will be used for the filename if <code>"%s"</code> is not
-preceded by a <code>'/'</code>. If you don't like this (it can stuff up some
-lpq output) then use <code>"%f"</code> instead. Any occurrences of <code>"%f"</code> get
-replaced by the spool filename without the full path at the front.
+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>
 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="smb.conf.5.html#global"><strong>"[global]"</strong></a> section, the print
+<p><br>If specified in the <a href="../yodldocs/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
@@ -3323,8 +3378,8 @@ 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>
 account. If this happens then create an alternative guest account that
-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.
+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
 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
@@ -3332,27 +3387,27 @@ separator for command in shell scripts.
 <p><br><code>print command = echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</code>
 <p><br>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="smb.conf.5.html#printing"><strong>"printing="</strong></a>
+varies depending on the setting of the <a href="../yodldocs/smb.conf.5.html#printing"><strong>"printing="</strong></a>
 parameter.
 <p><br><strong>Default:</strong>
-	For <a href="smb.conf.5.html#printing"><strong>"printing="</strong></a> BSD, AIX, QNX, LPRNG or PLP :
+	For <a href="../yodldocs/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="smb.conf.5.html#printing"><strong>"printing="</strong></a> SYS or HPUX :
+<p><br>For <a href="../yodldocs/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="smb.conf.5.html#printing"><strong>"printing="</strong></a> SOFTQ :
+<p><br>For <a href="../yodldocs/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>
 <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="smb.conf.5.html#printable"><strong>printable</strong></a>.
+<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
 submit spool files on the directory specified for the service.
 <p><br>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="smb.conf.5.html#readonly"><strong>"read only"</strong></a> parameter controls only non-printing
+<a href="../yodldocs/smb.conf.5.html#writeable"><strong>"writeable"</strong></a> parameter controls only non-printing
 access to the resource.
 <p><br><strong>Default:</strong>
 <code> 	printable = no</code>
@@ -3360,12 +3415,12 @@ access to the resource.
 <code> 	printable = yes</code>
 <p><br><a name="printcap"></a>
 <li><strong><strong>printcap (G)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#printcapname"><strong>printcapname</strong></a>.
+<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
 printcap name used by the server (usually /etc/printcap). See the
-discussion of the <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a> section above for
+discussion of the <a href="../yodldocs/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
 can use <code>"printcap name = lpstat"</code> to automatically obtain lists of
@@ -3399,7 +3454,7 @@ format if the string <code>"/qconfig"</code> appears in the printcap filename.
 <li><strong><strong>printer (S)</strong></strong>
 <p><br>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="smb.conf.5.html#global"><strong>[global]</strong></a> section, the printer
+<p><br>If specified in the <a href="../yodldocs/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>
@@ -3418,7 +3473,7 @@ 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="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>.
+<p><br>See also <a href="../yodldocs/smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>.
 <p><br><strong>Example:</strong>
 	printer driver = HP LaserJet 4L
 <p><br><a name="printerdriverfile"></a>
@@ -3435,14 +3490,14 @@ in the docs/ directory, PRINTER_DRIVER.txt.
 <code>	None (set in compile).</code>
 <p><br><strong>Example:</strong>
 <code>	printer driver file = /usr/local/samba/printers/drivers.def</code>
-<p><br>See also <a href="smb.conf.5.html#printerdriverlocation"><strong>"printer driver location"</strong></a>.
+<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
 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\aPRINTER$</code>
+<p><br><code>\\MACHINE\PRINTER$</code>
 <p><br>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/
@@ -3451,27 +3506,28 @@ directory, PRINTER_DRIVER.txt.
 <code>	None</code>
 <p><br><strong>Example:</strong>
 <code>	printer driver location = \\MACHINE\PRINTER$</code>
-<p><br>See also <a href="smb.conf.5.html#printerdriverfile"><strong>"printer driver file"</strong></a>.
+<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="smb.conf.5.html#printer"><strong>printer</strong></a>.
+<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
-on your system, and also affects the default values for the
-<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>.
+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>
+section.
 <p><br>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> and
-<strong>"printing=SOFTQ"</strong>.
+<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
-these three options use the <a href="testparm.1.html"><strong>"testparm"</strong></a> program.
+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="smb.conf.5.html#printers"><strong>[printers]</strong></a> section.
+<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
@@ -3495,7 +3551,7 @@ protocol.
 <code>	protocol = LANMAN1</code>
 <p><br><a name="public"></a>
 <li><strong><strong>public (S)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#guestok"><strong>"guest ok"</strong></a>.
+<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
@@ -3518,7 +3574,7 @@ command as the PATH may not be available to the server.
 <p><br>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="smb.conf.5.html#queuepausecommand"><strong>"queuepause command</strong></a>).
+(<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
 as its only parameter and resumes the printerqueue, such that queued
 jobs are resubmitted to the printer.
@@ -3543,11 +3599,11 @@ and defaults to off. You should never need to set this parameter.
 <li><strong><strong>read list (S)</strong></strong>
 <p><br>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="smb.conf.5.html#readonly"><strong>"read only"</strong></a>
+given write access, no matter what the <a href="../yodldocs/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="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a> parameter.
-<p><br>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.
+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>
 <code>	read list = &lt;empty string&gt;</code>
 <p><br><strong>Example:</strong>
@@ -3555,9 +3611,7 @@ the <a href="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>
 <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="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> and <a href="smb.conf.5.html#writeok"><strong>"write ok"</strong></a>.
-<p><br>See also <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> and <a href="smb.conf.5.html#writeok"><strong>"write
-ok"</strong></a>.
+<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
@@ -3579,7 +3633,7 @@ typically provides a major performance benefit.
 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="smb.conf.5.html#writeraw"><strong>"write raw"</strong></a>.
+severely alone. See also <a href="../yodldocs/smb.conf.5.html#writeraw"><strong>"write raw"</strong></a>.
 <p><br><strong>Default:</strong>
 <code> 	read raw = yes</code>
 <p><br><a name="readsize"></a>
@@ -3617,7 +3671,7 @@ packets to.
 <p><br>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="smb.conf.5.html#workgroup"><strong>"workgroup"</strong></a> parameter is used instead.
+<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
 of the remote networks, but can also be the IP addresses of known
 browse masters if your network config is that stable.
@@ -3682,7 +3736,7 @@ as a different user".
 <p><br><a name="revalidate"></a>
 <li><strong><strong>revalidate (S)</strong></strong>
 <p><br>Note that this option only works with
-<a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> and will be ignored if
+<a href="../yodldocs/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
 username/password pair to be used to attach to a share. Thus if you
@@ -3697,10 +3751,10 @@ automatic access as the same username.
 <code>	revalidate = True</code>
 <p><br><a name="root"></a>
 <li><strong><strong>root (G)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>.
+<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="smb.conf.5.html#rootdirectory"><strong>"root directory"</strong></a>.
+<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
@@ -3709,7 +3763,7 @@ 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="smb.conf.5.html#widelinks"><strong>"wide links"</strong></a> parameter).
+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
 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
@@ -3726,22 +3780,22 @@ operating system dependent.
 <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="smb.conf.5.html#postexec"><strong>"postexec"</strong></a> parameter
+<p><br>This is the same as the <a href="../yodldocs/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="smb.conf.5.html#postexec"><strong>"postexec"</strong></a>.
+<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="smb.conf.5.html#preexec"><strong>"preexec"</strong></a> parameter except
+<p><br>This is the same as the <a href="../yodldocs/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="smb.conf.5.html#preexec"><strong>"preexec"</strong></a>
-and <a href="smb.conf.5.html#rootpreexecclose"><strong>"root preexec close"</strong></a>.
+<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="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a> parameter
+<p><br>This is the same as the <a href="../yodldocs/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="smb.conf.5.html#preexec"><strong>"preexec"</strong></a>, <a href="smb.conf.5.html#preexecclose"><strong>"preexec close"</strong></a>.
+<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
@@ -3750,16 +3804,16 @@ important settings in the <strong>smb.conf</strong> file.
 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="smb.conf.5.html#securityequaluser">"security=user"</a>, as this is
+<p><br>The default is <a href="../yodldocs/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="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><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
 PREVIOUS VERSIONS OF SAMBA *******</em>.
 <p><br>In previous versions of Samba the default was
-<a href="smb.conf.5.html#securityequalshare"><strong>"security=share"</strong></a> mainly because that was
+<a href="../yodldocs/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
 user or server level security a WfWg client will totally ignore the
@@ -3770,17 +3824,17 @@ anyone except the user that you are logged into WfWg as.
 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="smb.conf.5.html#securityequalshare"><strong>security=share</strong></a> if
+<p><br>You should also use <a href="../yodldocs/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="smb.conf.5.html#securityequaluser"><strong>security=user</strong></a>, see the <a href="smb.conf.5.html#maptoguest"><strong>"map to
+<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
 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
 mode"</em> where it is offers both user and share level security under
-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.
+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>
@@ -3802,11 +3856,11 @@ of the client.
 <p><br>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="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
+<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
 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="smb.conf.5.html#usernamemap"><strong>"username
+this username (after mapping - see <a href="../yodldocs/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
 SessionSetup SMB call) then the username sent in this SMB
@@ -3815,29 +3869,29 @@ will be added as a potential username.
 as a potential username.
 <p><br><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="smb.conf.5.html#user"><strong>"user"</strong></a> list are added
+<p><br><li > Any users on the <a href="../yodldocs/smb.conf.5.html#user"><strong>"user"</strong></a> list are added
 as potential usernames.
 <p><br></ul>
-<p><br>If the <a href="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is not set, then
+<p><br>If the <a href="../yodldocs/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="smb.conf.5.html#guestonly"><strong>"guest only"</strong></a> parameter is set, or no
+<p><br>If the <a href="../yodldocs/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="smb.conf.5.html#guestaccount"><strong>"guest account"</strong></a>, then this guest user will
+the <a href="../yodldocs/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
 which UNIX username will eventually be used in granting access.
-<p><br>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
+<p><br>See also the section <a href="../yodldocs/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
 security a client must first <code>"log-on"</code> with a valid username and
-password (which can be mapped using the <a href="smb.conf.5.html#usernamemap"><strong>"username
+password (which can be mapped using the <a href="../yodldocs/smb.conf.5.html#usernamemap"><strong>"username
 map"</strong></a> parameter). Encrypted passwords (see the
-<a href="smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter) can also
+<a href="../yodldocs/smb.conf.5.html#encryptpasswords"><strong>"encrypted passwords"</strong></a> parameter) can also
 be used in this security mode. Parameters such as
-<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
+<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
 are then applied and may change the UNIX user to use on this
 connection, but only after the user has been successfully
 authenticated.
@@ -3845,10 +3899,10 @@ authenticated.
 <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="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
+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
 doing this.
-<p><br>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
+<p><br>See also the section <a href="../yodldocs/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>
@@ -3860,25 +3914,25 @@ 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="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only
+the same as <a href="../yodldocs/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
 <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="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
+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
 doing this.
-<p><br>See also the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
+<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
 VALIDATION"</strong></a>.
-<p><br>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><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
 <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="smb.conf.5.html#encryptpasswords"><strong>"encrypted
+into a Windows NT Domain. It expects the <a href="../yodldocs/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
@@ -3887,15 +3941,15 @@ same way that a Windows NT Server would do.
 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="smb.conf.5.html#securityequaluser"><strong>"security=user"</strong></a>. It only
+the same as <a href="../yodldocs/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
 <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="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
+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
 doing this.
 <p><br><em>BUG:</em> There is currently a bug in the implementation of
 <strong>"security=domain</strong> with respect to multi-byte character
@@ -3904,10 +3958,10 @@ 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="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
+<p><br>See also the section <a href="../yodldocs/smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
 VALIDATION"</strong></a>.
-<p><br>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><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>
 <code> 	security = USER</code>
@@ -3923,16 +3977,16 @@ 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="smb.conf.5.html#createmask"><strong>create mask</strong></a> parameter. To allow a user to
+<a href="../yodldocs/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
 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="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
+<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
 mode</strong></a> parameters.
 <p><br><strong>Default:</strong>
 <code>	security mask = &lt;same as create mask&gt;</code>
@@ -3993,14 +4047,14 @@ smaller size, reducing by a factor of 0.8 until the OS accepts it.
 <p><br><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 (G)</strong></strong>
+<li><strong><strong>short preserve case (S)</strong></strong>
 <p><br>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="smb.conf.5.html#preservecaseoption"><strong>"preserve case
+option can be use with <a href="../yodldocs/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="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>.
+<p><br>See the section on <a href="../yodldocs/smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	short preserve case = yes</code>
 <p><br><a name="smbpasswdfile"></a>
@@ -4046,7 +4100,7 @@ appropriate documentation for your operating system first (perhaps
 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-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
+<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
 like, as long as your OS allows it.
 <p><br>This is the list of socket options currently settable using this
@@ -4081,6 +4135,25 @@ completely. Use these options with caution!
 <code>	socket options = TCP_NODELAY</code>
 <p><br><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
+content of the file named.
+<p><br>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
+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
+as the output of the standard Unix env(1) command. This is of the form :
+<p><br>Example environment entry:
+<code> SAMBA_NETBIOS_NAME=myhostname </code>
+<p><br><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
@@ -4090,8 +4163,8 @@ option <code>"--with-ssl"</code> was given at configure time.
 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
 "no", the SSL enabled samba behaves exactly like the non-SSL samba. If
-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>
+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>
 whether an SSL connection will be required.
 <p><br><strong>Default:</strong>
 <code>	ssl=no</code>
@@ -4178,7 +4251,7 @@ than SSLeay exist.
 <code>	ssl compatibility = no</code>
 <p><br><a name="sslhosts"></a>
 <li><strong><strong>ssl hosts (G)</strong></strong>
-<p><br>See <a href="smb.conf.5.html#sslhostsresign"><strong>"ssl hosts resign"</strong></a>.
+<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
@@ -4188,15 +4261,15 @@ option <code>"--with-ssl"</code> was given at configure time.
 enabled by default in any current binary version of Samba.
 <p><br>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="smb.conf.5.html#sslhosts"><strong>"ssl hosts"</strong></a> variable lists
+connections. If the <a href="../yodldocs/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="smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="smb.conf.5.html#hostsdeny"><strong>"hosts
+<a href="../yodldocs/smb.conf.5.html#hostsallow"><strong>"hosts allow"</strong></a> and <a href="../yodldocs/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="smb.conf.5.html#allowhosts"><strong>"allow hosts"</strong></a> parameter for
+used or not. See the <a href="../yodldocs/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>
@@ -4213,8 +4286,8 @@ option <code>"--with-ssl"</code> was given at configure time.
 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
 connections from clients that don't have a valid certificate. 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
+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
 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
@@ -4234,7 +4307,7 @@ option <code>"--with-ssl"</code> was given at configure time.
 enabled by default in any current binary version of Samba.
 <p><br>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="smb.conf.5.html#sslrequireclientcert"><strong>"ssl require
+the server. Same as <a href="../yodldocs/smb.conf.5.html#sslrequireclientcert"><strong>"ssl require
 clientcert"</strong></a> for the server.
 <p><br><strong>Default:</strong>
 <code>	ssl require servercert = no</code>
@@ -4286,7 +4359,7 @@ never need to change this parameter.
 <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="smb.conf.5.html#statcache"><strong>stat
+<p><br>This parameter determines the number of entries in the <a href="../yodldocs/smb.conf.5.html#statcache"><strong>stat
 cache</strong></a>.  You should never need to change this parameter.
 <p><br><strong>Default:</strong>
 <code>	stat cache size = 50</code>
@@ -4328,7 +4401,7 @@ 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="smb.conf.5.html#syncalways"><strong>"sync always"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#syncalways"><strong>"sync always"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	strict sync = no</code>
 <p><br><strong>Example:</strong>
@@ -4350,9 +4423,9 @@ 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="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter must be
+Note that the <a href="../yodldocs/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="smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#strictsync"><strong>"strict sync"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	sync always = no</code>
 <p><br><strong>Example:</strong>
@@ -4375,6 +4448,24 @@ to syslog.
 system syslog only, and not to the debug log files.
 <p><br><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
+<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>
+<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
+<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>
+<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
@@ -4394,24 +4485,18 @@ itself as a time server to Windows clients. The default is False.
 <code>	time server = True</code>
 <p><br><a name="timestamplogs"></a>
 <li><strong><strong>timestamp logs (G)</strong></strong>
-<p><br>Samba2.0 will a timestamps to all log entries by default. This
-can be distracting if you are attempting to debug a problem. This
-parameter allows the timestamping to be turned off.
-<p><br><strong>Default:</strong>
-<code>	timestamp logs = True</code>
-<p><br><strong>Example:</strong>
-<code>	timestamp logs = False</code>
+<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
 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="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>
+program specified in the <a href="../yodldocs/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="smb.conf.5.html#passwdprogram"><strong>"passwd program"</strong></a>, <a href="smb.conf.5.html#passwdchat"><strong>"passwd
+<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
 chat"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	unix password sync = False</code>
@@ -4441,7 +4526,7 @@ 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="smb.conf.5.html#encryptpasswords"><strong>"encrypt
+<p><br>In order for this parameter to work correctly the <a href="../yodldocs/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
@@ -4468,10 +4553,10 @@ doing.
 <code>	use rhosts = yes</code>
 <p><br><a name="user"></a>
 <li><strong><strong>user (S)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#username"><strong>"username"</strong></a>.
+<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="smb.conf.5.html#username"><strong>"username"</strong></a>.
+<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
@@ -4495,7 +4580,7 @@ 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="smb.conf.5.html#validusers"><strong>"valid users="</strong></a> parameter.
+<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
 looked up first in the yp netgroups list (if Samba is compiled with
 netgroup support), followed by a lookup in the UNIX groups database
@@ -4509,7 +4594,7 @@ 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,
 and some clients may time out during the search.
-<p><br>See the section <a href="smb.conf.5.html#NOTEABOUTUSERNAMEPASSWORDVALIDATION"><strong>"NOTE ABOUT USERNAME/PASSWORD
+<p><br>See the section <a href="../yodldocs/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>
@@ -4594,7 +4679,7 @@ usernames. Thus if you connect to <code>"\\server\fred"</code> and <code>"fred"<
 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="smb.conf.5.html#passwordserver"><strong>"password server"</strong></a> (if you have
+passed to the <a href="../yodldocs/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
@@ -4605,8 +4690,62 @@ print job.
 <code>	no username map</code>
 <p><br><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 
+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>
+<code>utmp = False</code>
+<p><br><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
+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>
+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>
+<code>no utmp directory</code>
+<p><br><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
+<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>
+<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
+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>
+<code>     winbind gid = &lt;empty string&gt;</code>
+<p><br><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
+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>
+<code>     winbind uid = &lt;empty string&gt;</code>
+<p><br><strong>Example:</strong>
+<code>     winbind uid = 10000-20000</code>
 <p><br><a name="validchars"></a>
-<li><strong><strong>valid chars (S)</strong></strong>
+<li><strong><strong>valid chars (G)</strong></strong>
 <p><br>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.
@@ -4630,12 +4769,12 @@ the following
 
 <p><br>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="smb.conf.5.html#clientcodepage"><strong>"client
+<p><br>Note that you MUST specify this parameter after the <a href="../yodldocs/smb.conf.5.html#clientcodepage"><strong>"client
 code page"</strong></a> parameter if you have both set. If
-<a href="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> is set after the
+<a href="../yodldocs/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="smb.conf.5.html#clientcodepage"><strong>"client code page"</strong></a> parameter.
+<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>
 <pre>
 
@@ -4658,15 +4797,15 @@ of your Samba source code distribution for this package.
 <li><strong><strong>valid users (S)</strong></strong>
 <p><br>This is a list of users that should be allowed to login to this
 service. Names starting with <code>'@'</code>, <code>'+'</code> and <code>'&amp;'</code> are
-interpreted using the same rules as described in the <a href="smb.conf.5.html#invalidusers"><strong>"invalid
+interpreted using the same rules as described in the <a href="../yodldocs/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="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>
+is in both this list and the <a href="../yodldocs/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="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="smb.conf.5.html#invalidusers"><strong>"invalid users"</strong></a>.
+<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>
 <code>	No valid users list. (anyone can login)</code>
 <p><br><strong>Example:</strong>
@@ -4680,7 +4819,7 @@ 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 
 unix directory separator <code>'/'</code>.
-<p><br>Note that the <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a> option is
+<p><br>Note that the <a href="../yodldocs/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
 aware of, is that if a directory contains nothing but files that match
@@ -4691,7 +4830,7 @@ to do so.
 <p><br>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="smb.conf.5.html#hidefiles"><strong>"hide files"</strong></a> and <a href="smb.conf.5.html#casesensitive"><strong>"case
+<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
 sensitive"</strong></a>.
 <p><br><strong>Default:</strong>
 <code>	No files or directories are vetoed.</code>
@@ -4720,11 +4859,11 @@ sensitive"</strong></a>.
 
 <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="smb.conf.5.html#oplocks"><strong>"oplocks"</strong></a>
+<p><br>This parameter is only valid when the <a href="../yodldocs/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="smb.conf.5.html#vetofiles"><strong>"veto files"</strong></a> parameter.
+<a href="../yodldocs/smb.conf.5.html#vetofiles"><strong>"veto files"</strong></a> parameter.
 <p><br><strong>Default:</strong>
 <code>	No files are vetoed for oplock grants.</code>
 <p><br><strong>Examples:</strong>
@@ -4732,7 +4871,7 @@ match a wildcarded list, similar to the wildcarded list used in the
 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="smb.conf.5.html#global"><strong>[global]</strong></a>
+files you would use the line (either in the <a href="../yodldocs/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>
@@ -4818,7 +4957,7 @@ network.
 <li><strong><strong>workgroup (G)</strong></strong>
 <p><br>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="smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>
+name used with the <a href="../yodldocs/smb.conf.5.html#securityequaldomain"><strong>"security=domain"</strong></a>
 setting.
 <p><br><strong>Default:</strong>
 <code> 	set at compile time to WORKGROUP</code>
@@ -4826,24 +4965,44 @@ setting.
  	workgroup = MYGROUP
 <p><br><a name="writable"></a>
 <li><strong><strong>writable (S)</strong></strong>
-<p><br>Synonym for <a href="smb.conf.5.html#writeable"><strong>"writeable"</strong></a> for people who can't spell :-).
+<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
 service. If the connecting user is in this list then they will be
-given write access, no matter what the <a href="smb.conf.5.html#readonly"><strong>"read only"</strong></a>
+given write access, no matter what the <a href="../yodldocs/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
 they will be given write access.
-<p><br>See also the <a href="smb.conf.5.html#readlist"><strong>"read list"</strong></a> option.
+<p><br>See also the <a href="../yodldocs/smb.conf.5.html#readlist"><strong>"read list"</strong></a> option.
 <p><br><strong>Default:</strong>
 <code>     write list = &lt;empty string&gt;</code>
 <p><br><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
+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
+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)
+in bytes.
+<p><br><strong>Default:</strong>
+<code>     write cache size = 0</code>
+<p><br><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="smb.conf.5.html#writeable"><strong>writeable</strong></a>.
+<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
@@ -4853,10 +5012,10 @@ need to change this parameter.
 <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="smb.conf.5.html#readonly"><strong>"read only"</strong></a>.
+<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
 or modify files in the service's directory.
-<p><br>Note that a printable service <a href="smb.conf.5.html#printable"><strong>("printable = yes")</strong></a>
+<p><br>Note that a printable service <a href="../yodldocs/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>
@@ -4883,7 +5042,7 @@ service names to eight characters. <a href="smbd.8.html"><strong>Smbd</strong></
 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="smb.conf.5.html#homes"><strong>[homes]</strong></a> and <a href="smb.conf.5.html#printers"><strong>[printers]</strong></a>
+<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>
 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
@@ -4904,7 +5063,7 @@ permissions on spool directories are correct.
 <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
+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
@@ -4912,7 +5071,7 @@ 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>.
 <p><br>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.
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index da87331769..ac227d9182 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -111,7 +111,7 @@ as the default guest user (specified elsewhere):
 
  	[aprinter]
  		path = /usr/spool/public
- 		read only = true
+ 		writeable = false
  		printable = true
  		guest ok = true
 
@@ -201,7 +201,7 @@ make any auto home directories visible\&.
 .IP 
 This section works like \fB[homes]\fP, but for printers\&.
 .IP 
-If a [printers] section occurs in the configuration file, users are
+If a \fB[printers]\fP section occurs in the configuration file, users are
 able to connect to any printer specified in the local host\'s printcap
 file\&.
 .IP 
@@ -211,7 +211,7 @@ scanned\&. If a match is found, it is used\&. If no match is found, but a
 above\&. Otherwise, the requested section name is treated as a printer
 name and the appropriate printcap file is scanned to see if the
 requested section name is a valid printer share name\&. If a match is
-found, a new printer share is created by cloning the [printers]
+found, a new printer share is created by cloning the \fB[printers]\fP
 section\&.
 .IP 
 A few modifications are then made to the newly created share:
@@ -229,11 +229,11 @@ If the share does not permit guest access and no username was
 given, the username is set to the located printer name\&.
 .IP 
 .IP 
-Note that the [printers] service MUST be printable - if you specify
+Note that the \fB[printers]\fP service MUST be printable - if you specify
 otherwise, the server will refuse to load the configuration file\&.
 .IP 
 Typically the path specified would be that of a world-writeable spool
-directory with the sticky bit set on it\&. A typical [printers] entry
+directory with the sticky bit set on it\&. A typical \fB[printers]\fP entry
 would look like this:
 .IP 
 
@@ -242,7 +242,6 @@ would look like this:
 
  	[printers]
  		path = /usr/spool/public
- 		writeable = no
  		guest ok = yes
  		printable = yes 
 
@@ -378,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-bugs@samba\&.org\fP
+then sending a level 3 log to \fIsamba@samba\&.org\fP
 should allow it to be fixed\&.
 .IP 
 .IP o 
@@ -542,7 +541,7 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBdebug uid\fP
 .IP 
 .IP o 
-\fBdebuglevel\fP
+\fBdebug level\fP
 .IP 
 .IP o 
 \fBdefault\fP
@@ -566,9 +565,6 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBdomain admin users\fP
 .IP 
 .IP o 
-\fBdomain controller\fP
-.IP 
-.IP o 
 \fBdomain groups\fP
 .IP 
 .IP o 
@@ -701,6 +697,9 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBmin passwd length\fP
 .IP 
 .IP o 
+\fBmin password length\fP
+.IP 
+.IP o 
 \fBmin wins ttl\fP
 .IP 
 .IP o 
@@ -713,6 +712,9 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBnetbios name\fP
 .IP 
 .IP o 
+\fBnetbios scope\fP
+.IP 
+.IP o 
 \fBnis homedir\fP
 .IP 
 .IP o 
@@ -830,6 +832,9 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBsocket options\fP
 .IP 
 .IP o 
+\fBsource environment\fP
+.IP 
+.IP o 
 \fBssl\fP
 .IP 
 .IP o 
@@ -887,6 +892,12 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBsyslog only\fP
 .IP 
 .IP o 
+\fBtemplate homedir\fP
+.IP 
+.IP o 
+\fBtemplate shell\fP
+.IP 
+.IP o 
 \fBtime offset\fP
 .IP 
 .IP o 
@@ -914,18 +925,30 @@ parameter for details\&.  Note that some are synonyms\&.
 \fBusername map\fP
 .IP 
 .IP o 
+\fButmp directory\fP
+.IP 
+.IP o 
 \fBvalid chars\fP
 .IP 
 .IP o 
-\fBwins proxy\fP
+\fBwinbind cache time\fP
 .IP 
 .IP o 
-\fBwins server\fP
+\fBwinbind gid\fP
+.IP 
+.IP o 
+\fBwinbind uid\fP
 .IP 
 .IP o 
 \fBwins hook\fP
 .IP 
 .IP o 
+\fBwins proxy\fP
+.IP 
+.IP o 
+\fBwins server\fP
+.IP 
+.IP o 
 \fBwins support\fP
 .IP 
 .IP o 
@@ -1074,6 +1097,9 @@ parameter for details\&. Note that some are synonyms\&.
 \fBinclude\fP
 .IP 
 .IP o 
+\fBinherit permissions\fP
+.IP 
+.IP o 
 \fBinvalid users\fP
 .IP 
 .IP o 
@@ -1137,10 +1163,10 @@ parameter for details\&. Note that some are synonyms\&.
 \fBonly user\fP
 .IP 
 .IP o 
-\fBoplocks\fP
+\fBoplock contention limit\fP
 .IP 
 .IP o 
-\fBoplock contention limit\fP
+\fBoplocks\fP
 .IP 
 .IP o 
 \fBpath\fP
@@ -1209,10 +1235,10 @@ parameter for details\&. Note that some are synonyms\&.
 \fBroot preexec\fP
 .IP 
 .IP o 
-\fBsecurity mask\fP
+\fBroot preexec close\fP
 .IP 
 .IP o 
-\fBroot preexec close\fP
+\fBsecurity mask\fP
 .IP 
 .IP o 
 \fBset directory\fP
@@ -1245,6 +1271,9 @@ parameter for details\&. Note that some are synonyms\&.
 \fBusers\fP
 .IP 
 .IP o 
+\fButmp\fP
+.IP 
+.IP o 
 \fBvalid users\fP
 .IP 
 .IP o 
@@ -1263,6 +1292,9 @@ parameter for details\&. Note that some are synonyms\&.
 \fBwritable\fP
 .IP 
 .IP o 
+\fBwrite cache size\fP
+.IP 
+.IP o 
 \fBwrite list\fP
 .IP 
 .IP o 
@@ -1545,11 +1577,11 @@ shares in a net view and in the browse list\&.
 \fBExample:\fP
 \f(CW	browseable = No\fP
 .IP 
-.IP "\fBcase sensitive (G)\fP" 
+.IP "\fBcase sensitive (S)\fP" 
 .IP 
 See the discussion in the section \fBNAME MANGLING\fP\&.
 .IP 
-.IP "\fBcasesignames (G)\fP" 
+.IP "\fBcasesignames (S)\fP" 
 .IP 
 Synonym for \fB"case sensitive"\fP\&.
 .IP 
@@ -1820,6 +1852,7 @@ See also the \fB"force create mode"\fP parameter
 for forcing particular mode bits to be set on created files\&. See also
 the \fB"directory mode"\fP parameter for masking
 mode bits on created directories\&.
+See also the \fB"inherit permissions"\fP parameter\&.
 .IP 
 \fBDefault:\fP
 \f(CW	create mask = 0744\fP
@@ -1875,7 +1908,7 @@ must be on for this to have an effect\&.
 .IP 
 Samba2\&.0 debug log messages are timestamped by default\&. If you are
 running at a high \fB"debug level"\fP these timestamps
-can be distracting\&. This boolean parameter allows them to be turned
+can be distracting\&. This boolean parameter allows timestamping to be turned
 off\&.
 .IP 
 \fBDefault:\fP
@@ -2163,6 +2196,8 @@ See also the \fB"create mode"\fP parameter for masking
 mode bits on created files, and the \fB"directory security mask"\fP
 parameter\&.
 .IP 
+See also the \fB"inherit permissions"\fP parameter\&.
+.IP 
 \fBDefault:\fP
 \f(CW	directory mask = 0755\fP
 .IP 
@@ -2243,12 +2278,6 @@ Samba NT Domain Controller functionality please subscribe to the
 mailing list \fBSamba-ntdom\fP available by sending email to
 \fIlistproc@samba\&.org\fP
 .IP 
-.IP "\fBdomain controller (G)\fP" 
-.IP 
-This is a \fBDEPRECATED\fP parameter\&. It is currently not used within
-the Samba source and should be removed from all current smb\&.conf
-files\&. It is left behind for compatibility reasons\&.
-.IP 
 .IP "\fBdomain groups (G)\fP" 
 .IP 
 This is an \fBEXPERIMENTAL\fP parameter that is part of the unfinished
@@ -2474,14 +2503,17 @@ symbolic links) by default\&.
 .IP "\fBforce create mode (S)\fP" 
 .IP 
 This parameter specifies a set of UNIX mode bit permissions that will
-\fI*always*\fP be set on a file created by Samba\&. This is done by
-bitwise \'OR\'ing these bits onto the mode bits of a file that is being
-created\&. 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 \fB"create mask"\fP parameter is applied\&.
+\fI*always*\fP 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 \fB"create
+mask"\fP parameter is applied\&.
 .IP 
 See also the parameter \fB"create mask"\fP for details
-on masking mode bits on created files\&.
+on masking mode bits on files\&.
+.IP 
+See also the \fB"inherit permissions"\fP parameter\&.
 .IP 
 \fBDefault:\fP
 \f(CW	force create mode = 000\fP
@@ -2506,6 +2538,8 @@ operation is done after the mode mask in the parameter
 See also the parameter \fB"directory mask"\fP for
 details on masking mode bits on created directories\&.
 .IP 
+See also the \fB"inherit permissions"\fP parameter\&.
+.IP 
 \fBDefault:\fP
 \f(CW	force directory mode = 000\fP
 .IP 
@@ -2906,6 +2940,41 @@ is included literally, as though typed in place\&.
 It takes the standard substitutions, except \fB%u\fP,
 \fB%P\fP and \fB%S\fP\&.
 .IP 
+.IP "\fBinherit permissions (S)\fP" 
+.IP 
+The permissions on new files and directories are normally governed by
+\fB"create mask"\fP,
+\fB"directory mask"\fP,
+\fB"force create mode"\fP and
+\fB"force directory mode"\fP
+but the boolean inherit permissions parameter overrides this\&.
+.IP 
+New directories inherit the mode of the parent directory,
+including bits such as setgid\&.
+.IP 
+New files inherit their read/write bits from the parent directory\&.
+Their execute bits continue to be determined by
+\fB"map archive"\fP,
+\fB"map hidden"\fP and
+\fB"map system"\fP as usual\&.
+.IP 
+Note that the setuid bit is *never* set via inheritance
+(the code explicitly prohibits this)\&.
+.IP 
+This can be particularly useful on large systems with many users,
+perhaps several thousand,
+to allow a single \fB[homes]\fP share to be used flexibly by each user\&.
+.IP 
+See also \fB"create mask"\fP, \fB"directory mask"\fP,
+\fB"force create mode"\fP and
+\fB"force directory mode"\fP\&.
+.IP 
+\fBDefault\fP
+\f(CW   inherit permissions = no\fP
+.IP 
+\fBExample\fP
+\f(CW   inherit permissions = yes\fP
+.IP 
 .IP "\fBinterfaces (G)\fP" 
 .IP 
 This option allows you to override the default network interfaces list
@@ -2921,10 +2990,13 @@ any of the following forms:
 a network interface name (such as eth0)\&. This may include
 shell-like wildcards so eth* will match any interface starting
 with the substring "eth"
-if() a IP address\&. In this case the netmask is determined
+.IP o 
+an IP address\&. In this case the netmask is determined
 from the list of interfaces obtained from the kernel
-if() a IP/mask pair\&. 
-if() a broadcast/mask pair\&. 
+.IP o 
+an IP/mask pair\&. 
+.IP o 
+a broadcast/mask pair\&. 
 .IP 
 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\&.
@@ -3106,7 +3178,7 @@ for an entry in the LDAP password database\&.
 .IP "\fBlevel2 oplocks (S)\fP" 
 .IP 
 This parameter (new in Samba 2\&.0\&.5) controls whether Samba supports
-level2 (read-only) oplocks on a share\&. In Samba 2\&.0\&.4 this parameter
+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\&.
 .IP 
@@ -3291,6 +3363,22 @@ from a command prompt, for example\&.
 This option takes the standard substitutions, allowing you to have
 separate logon scripts for each user or machine\&.
 .IP 
+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:
+.IP 
+\f(CW"     logon home = \e\e%L\e%U\eprofile"\fP
+.IP 
+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 \e\eserver\eshare when a user does \f(CW"net use /home"\fP,
+but use the whole string when dealing with profiles\&.
+.IP 
+Note that in prior versions of Samba, the \f(CW"logon path"\fP was returned rather than
+\f(CW"logon home"\fP\&.  This broke \f(CW"net use /home"\fP but allowed profiles outside the 
+home directory\&.  The current implementation is correct, and can be used for profiles
+if you use the above trick\&.
+.IP 
 Note that this option is only useful if Samba is set up as a
 \fBlogon server\fP\&.
 .IP 
@@ -3303,24 +3391,27 @@ Note that this option is only useful if Samba is set up as a
 .IP "\fBlogon path (G)\fP" 
 .IP 
 This parameter specifies the home directory where roaming profiles
-(USER\&.DAT / USER\&.MAN files for Windows 95/98) are stored\&.
+(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 \f(CW"logon home"\fP parameter\&.
 .IP 
 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 \f(CW"desktop"\fP, \f(CW"start menu"\fP,
-\f(CW"network neighborhood"\fP and \f(CW"programs"\fP folders, and their
-contents, are loaded and displayed on your Windows 95/98 client\&.
+the directory from which the \f(CW"application data"\fP, (\f(CW"desktop"\fP, \f(CW"start menu"\fP,
+\f(CW"network neighborhood"\fP, \f(CW"programs"\fP and other folders, and their
+contents, are loaded and displayed on your Windows NT client\&.
 .IP 
 The share and the path must be readable by the user for the
-preferences and directories to be loaded onto the Windows 95/98
+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 95/98 client can create the user\&.dat
+time, in order that the Windows NT client can create the NTuser\&.dat
 and other directories\&.
 .IP 
 Thereafter, the directories and any of the contents can, if required, be
-made read-only\&.  It is not advisable that the USER\&.DAT file be made
-read-only - rename it to USER\&.MAN to achieve the desired effect (a
-\fIMAN\fPdatory profile)\&.
+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
+\fIMAN\fPdatory profile)\&. 
 .IP 
 Windows clients can sometimes maintain a connection to the [homes]
 share, even though there is no user logged in\&.  Therefore, it is vital
@@ -3912,7 +4003,7 @@ so you should never need to touch this parameter\&.
 .IP 
 .IP "\fBmax packet (G)\fP" 
 .IP 
-Synonym for (packetsize)\&.
+Synonym for \fB"packet size"\fP\&.
 .IP 
 .IP "\fBmax ttl (G)\fP" 
 .IP 
@@ -4027,6 +4118,10 @@ See also the \fBprinting\fP parameter\&.
 .IP 
 .IP "\fBmin passwd length (G)\fP" 
 .IP 
+Synonym for \fB"min password length"\fP\&.
+.IP 
+.IP "\fBmin password length (G)\fP" 
+.IP 
 This option sets the minimum length in characters of a plaintext password
 than smbd will accept when performing UNIX password changing\&.
 .IP 
@@ -4035,7 +4130,7 @@ See also \fB"unix password sync"\fP,
 debug"\fP\&.
 .IP 
 \fBDefault:\fP
-\f(CW	min passwd length = 5\fP
+\f(CW	min password length = 5\fP
 .IP 
 .IP "\fBmin wins ttl (G)\fP" 
 .IP 
@@ -4129,6 +4224,11 @@ See also \fB"netbios aliases"\fP\&.
 \fBExample:\fP
 \f(CW	netbios name = MYNAME\fP
 .IP 
+.IP "\fBnetbios scope (G)\fP" 
+.IP 
+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\&.
+.IP 
 .IP "\fBnis homedir (G)\fP" 
 .IP 
 Get the home share server from a NIS map\&. For UNIX systems that use an
@@ -4326,7 +4426,7 @@ docs/ directory for details\&.
 .IP 
 .IP "\fBpacket size (G)\fP" 
 .IP 
-This is a deprecated parameter that how no effect on the current
+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 \fBsmb\&.conf\fP files\&.
 .IP 
@@ -4732,16 +4832,11 @@ command you specify should remove the spool file when it has been
 processed, otherwise you will need to manually remove old spool files\&.
 .IP 
 The print command is simply a text string\&. It will be used verbatim,
-with two exceptions: All occurrences of \f(CW"%s"\fP will be replaced by
-the appropriate spool file name, and all occurrences of \f(CW"%p"\fP will
-be replaced by the appropriate printer name\&. The spool file name is
-generated automatically by the server, the printer name is discussed
-below\&.
-.IP 
-The full path name will be used for the filename if \f(CW"%s"\fP is not
-preceded by a \f(CW\'/\'\fP\&. If you don\'t like this (it can stuff up some
-lpq output) then use \f(CW"%f"\fP instead\&. Any occurrences of \f(CW"%f"\fP get
-replaced by the spool filename without the full path at the front\&.
+with two exceptions: All occurrences of \f(CW"%s"\fP and \f(CW"%f"\fP will be
+replaced by the appropriate spool file name, and all occurrences of
+\f(CW"%p"\fP will be replaced by the appropriate printer name\&. The spool
+file name is generated automatically by the server, the printer name
+is discussed below\&.
 .IP 
 The print command \fIMUST\fP contain at least one occurrence of \f(CW"%s"\fP
 or \f(CW"%f"\fP - the \f(CW"%p"\fP is optional\&. At the time a job is
@@ -4797,7 +4892,7 @@ submit spool files on the directory specified for the service\&.
 .IP 
 Note that a printable service will ALWAYS allow writing to the service
 path (user privileges permitting) via the spooling of print data\&. The
-\fB"read only"\fP parameter controls only non-printing
+\fB"writeable"\fP parameter controls only non-printing
 access to the resource\&.
 .IP 
 \fBDefault:\fP
@@ -4917,7 +5012,7 @@ 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
 .IP 
-\f(CW\e\eMACHINE\eaPRINTER$\fP
+\f(CW\e\eMACHINE\ePRINTER$\fP
 .IP 
 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
@@ -4939,20 +5034,21 @@ Synonym for \fBprinter\fP\&.
 .IP "\fBprinting (S)\fP" 
 .IP 
 This parameters controls how printer status information is interpreted
-on your system, and also affects the default values for the
+on your system\&. It also affects the default values for the
 \fB"print command"\fP, \fB"lpq
 command"\fP \fB"lppause command"\fP,
 \fB"lpresume command"\fP, and \fB"lprm
-command"\fP\&.
+command"\fP if specified in the \fB[global]\fP
+section\&.
 .IP 
 Currently eight printing styles are supported\&. They are
-\fB"printing=BSD"\fP, \fB"printing=AIX"\fP, \fB"printing=LPRNG"\fP,
-\fB"printing=PLP"\fP,
-\fB"printing=SYSV"\fP,\fB"printing="HPUX"\fP,\fB"printing=QNX"\fP and
-\fB"printing=SOFTQ"\fP\&.
+\fB"printing=BSD"\fP, \fB"printing=AIX"\fP, 
+\fB"printing=LPRNG"\fP, \fB"printing=PLP"\fP, \fB"printing=SYSV"\fP, 
+\fB"printing="HPUX"\fP, \fB"printing=QNX"\fP, \fB"printing=SOFTQ"\fP,
+and \fB"printing=CUPS"\fP\&.
 .IP 
 To see what the defaults are for the other print commands when using
-these three options use the \fB"testparm"\fP program\&.
+the various options use the \fB"testparm"\fP program\&.
 .IP 
 This option can be set on a per printer basis
 .IP 
@@ -5061,7 +5157,7 @@ read bmpx = No
 .IP 
 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 \fB"read only"\fP
+given write access, no matter what the \fB"writeable"\fP
 option is set to\&. The list can include group names using the syntax
 described in the \fB"invalid users"\fP parameter\&.
 .IP 
@@ -5077,10 +5173,7 @@ the \fB"invalid users"\fP parameter\&.
 .IP "\fBread only (S)\fP" 
 .IP 
 Note that this is an inverted synonym for
-\fB"writeable"\fP and \fB"write ok"\fP\&.
-.IP 
-See also \fB"writeable"\fP and \fB"write
-ok"\fP\&.
+\fB"writeable"\fP\&.
 .IP 
 .IP "\fBread prediction (G)\fP" 
 .IP 
@@ -5643,7 +5736,7 @@ smaller size, reducing by a factor of 0\&.8 until the OS accepts it\&.
 \fBExample:\fP
 \f(CW	shared mem size = 5242880 ; Set to 5mb for a large number of files\&.\fP
 .IP 
-.IP "\fBshort preserve case (G)\fP" 
+.IP "\fBshort preserve case (S)\fP" 
 .IP 
 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
@@ -5714,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-bugs@samba\&.org\fP\&.
+\fIsamba@samba\&.org\fP\&.
 .IP 
 Any of the supported socket options may be combined in any way you
 like, as long as your OS allows it\&.
@@ -5782,6 +5875,34 @@ completely\&. Use these options with caution!
 \fBExample:\fP
 \f(CW	socket options = IPTOS_LOWDELAY\fP
 .IP 
+.IP "\fBsource environment (G)\fP" 
+.IP 
+This parameter causes Samba to set environment variables as per the
+content of the file named\&.
+.IP 
+The file \fBmust\fP be owned by root and not world writable in order
+to be read (this is a security check)\&.
+.IP 
+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\&.
+.IP 
+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 :
+.IP 
+Example environment entry:
+\f(CW SAMBA_NETBIOS_NAME=myhostname \fP
+.IP 
+\fBDefault:\fP
+\f(CWNo default value\fP
+.IP 
+\fBExamples:\fP
+.IP 
+\f(CW	source environment = |/etc/smb\&.conf\&.sh\fP
+.IP 
+\f(CW	source environment = /usr/local/smb_env_vars\fP
+.IP 
 .IP "\fBssl (G)\fP" 
 .IP 
 This variable is part of SSL-enabled Samba\&. This is only available if
@@ -6157,6 +6278,30 @@ system syslog only, and not to the debug log files\&.
 \fBDefault:\fP
 \f(CW	syslog only = no\fP
 .IP 
+.IP "\fBtemplate homedir (G)\fP" 
+.IP 
+NOTE: this parameter is only available in Samba 3\&.0\&.
+.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\&.
+.IP 
+\fBDefault:\fP
+\f(CW     template homedir = /home/%D/%U\fP
+.IP 
+.IP "\fBtemplate shell (G)\fP" 
+.IP 
+NOTE: this parameter is only available in Samba 3\&.0\&.
+.IP 
+When filling out the user information for a Windows NT user, the
+\fBwinbindd\fP daemon uses this parameter to fill in
+the login shell for that user\&.
+.IP 
+\fBDefault:\fP
+\f(CW     template shell = /bin/false\fP
+.IP 
 .IP "\fBtime offset (G)\fP" 
 .IP 
 This parameter is a setting in minutes to add to the normal GMT to
@@ -6183,15 +6328,7 @@ itself as a time server to Windows clients\&. The default is False\&.
 .IP 
 .IP "\fBtimestamp logs (G)\fP" 
 .IP 
-Samba2\&.0 will a timestamps to all log entries by default\&. This
-can be distracting if you are attempting to debug a problem\&. This
-parameter allows the timestamping to be turned off\&.
-.IP 
-\fBDefault:\fP
-\f(CW	timestamp logs = True\fP
-.IP 
-\fBExample:\fP
-\f(CW	timestamp logs = False\fP
+Synonym for \fB"debug timestamp"\fP\&.
 .IP 
 .IP "\fBunix password sync (G)\fP" 
 .IP 
@@ -6457,7 +6594,79 @@ print job\&.
 \fBExample:\fP
 \f(CW	username map = /usr/local/samba/lib/users\&.map\fP
 .IP 
-.IP "\fBvalid chars (S)\fP" 
+.IP "\fButmp (S)\fP" 
+.IP 
+This boolean parameter is only available if Samba has been configured and compiled 
+with the option \f(CW--with-utmp\fP\&. 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\&.
+.IP 
+See also the \fB"utmp directory"\fP parameter\&.
+.IP 
+\fBDefault:\fP
+\f(CWutmp = False\fP
+.IP 
+\fBExample:\fP
+\f(CWutmp = True\fP
+.IP 
+.IP "\fButmp directory(G)\fP" 
+.IP 
+This parameter is only available if Samba has been configured and compiled
+with the option \f(CW--with-utmp\fP\&. 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 \fB"utmp"\fP
+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)\&.
+.IP 
+\fBDefault:\fP
+\f(CWno utmp directory\fP
+.IP 
+\fBExample:\fP
+\f(CWutmp directory = /var/adm/\fP
+.IP 
+.IP "winbind cache time" 
+.IP 
+NOTE: this parameter is only available in Samba 3\&.0\&.
+.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\&.
+.IP 
+\fBDefault:\fP
+\f(CW     winbind cache type = 15\fP
+.IP 
+.IP "winbind gid" 
+.IP 
+NOTE: this parameter is only available in Samba 3\&.0\&.
+.IP 
+The winbind gid parameter specifies the range of group ids that are
+allocated by the \fBwinbindd\fP daemon\&.  This range of
+group ids should have no existing local or nis groups within it as strange
+conflicts can occur otherwise\&.
+.IP 
+\fBDefault:\fP
+\f(CW     winbind gid = <empty string>\fP
+.IP 
+\fBExample:\fP
+\f(CW     winbind gid = 10000-20000\fP
+.IP 
+.IP "winbind uid" 
+.IP 
+NOTE: this parameter is only available in Samba 3\&.0\&.
+.IP 
+The winbind uid parameter specifies the range of user ids that are
+allocated by the \fBwinbindd\fP daemon\&.  This range of
+ids should have no existing local or nis users within it as strange
+conflicts can occur otherwise\&.
+.IP 
+\fBDefault:\fP
+\f(CW     winbind uid = <empty string>\fP
+.IP 
+\fBExample:\fP
+\f(CW     winbind uid = 10000-20000\fP
+.IP 
+.IP "\fBvalid chars (G)\fP" 
 .IP 
 The option allows you to specify additional characters that should be
 considered valid by the server in filenames\&. This is particularly
@@ -6759,7 +6968,7 @@ Synonym for \fB"writeable"\fP for people who can\'t spell :-)\&.
 .IP 
 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 \fB"read only"\fP
+given write access, no matter what the \fB"writeable"\fP
 option is set to\&. The list can include group names using the @group
 syntax\&.
 .IP 
@@ -6774,6 +6983,31 @@ See also the \fB"read list"\fP option\&.
 \fBExample:\fP
 \f(CW	write list = admin, root, @staff\fP
 .IP 
+.IP "\fBwrite cache size (S)\fP" 
+.IP 
+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 \fBnot\fP 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\&.
+.IP 
+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\&.
+.IP 
+The integer parameter specifies the size of this cache (per oplocked file)
+in bytes\&.
+.IP 
+\fBDefault:\fP
+\f(CW     write cache size = 0\fP
+.IP 
+\fBExample:\fP
+\f(CW	     write cache size = 262144\fP
+for a 256k cache size per file\&.
+.IP 
 .IP "\fBwrite ok (S)\fP" 
 .IP 
 Synonym for \fBwriteable\fP\&.
@@ -6849,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-bugs@samba\&.org\fP\&. Samba is now developed
+Andrew Tridgell \fIsamba@samba\&.org\fP\&. Samba is now developed
 by the Samba Team as an Open Source project similar to the way the
 Linux kernel is developed\&.
 .PP 
@@ -6858,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-bugs@samba\&.org\fP\&.
+\fIsamba@samba\&.org\fP\&.
 .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/yodldocs/smb.conf.5.yo b/docs/yodldocs/smb.conf.5.yo
index 8983c26880..dc26764d8f 100644
--- a/docs/yodldocs/smb.conf.5.yo
+++ b/docs/yodldocs/smb.conf.5.yo
@@ -4880,10 +4880,10 @@ command"))(lprmcommand) if specified in the link(bf([global]))(global)
 section.
 
 Currently eight printing styles are supported. They are
-bf("printing=BSD"), bf("printing=AIX"), bf("printing=LPRNG"),
-bf("printing=PLP"),
-bf("printing=SYSV"),bf("printing="HPUX"),bf("printing=QNX") and
-bf("printing=SOFTQ").
+bf("printing=BSD"), bf("printing=AIX"), 
+bf("printing=LPRNG"), bf("printing=PLP"), bf("printing=SYSV"), 
+bf("printing="HPUX"), bf("printing=QNX"), bf("printing=SOFTQ"),
+and bf("printing=CUPS").
 
 To see what the defaults are for the other print commands when using
 the various options use the url(bf("testparm"))(testparm.1.html) program.
author	Gerald Carter <jerry@samba.org>	2000-05-12 13:05:24 +0000
committer	Gerald Carter <jerry@samba.org>	2000-05-12 13:05:24 +0000
commit	30129251f26a4b2b59817eb984cc76251e89691d (patch)
tree	42006fe63c790141f49c73bae3a4d7ee1d1e75f3 /docs
parent	75ebfc6f7a7692d772b729b2d83038a9054b4f90 (diff)
download	samba-30129251f26a4b2b59817eb984cc76251e89691d.tar.gz samba-30129251f26a4b2b59817eb984cc76251e89691d.tar.bz2 samba-30129251f26a4b2b59817eb984cc76251e89691d.zip