summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/misc
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2004-04-07 10:15:11 +0000
committerGerald W. Carter <jerry@samba.org>2008-04-23 08:45:43 -0500
commit992f1e6b8f86b346fddd266b04d29cde69585633 (patch)
tree878573999a6831aa14cd6b8072263eb5d5910aa4 /docs/smbdotconf/misc
parent65c0fd59203a3d9c4cb685e3a739f29f6f0c4fd6 (diff)
downloadsamba-992f1e6b8f86b346fddd266b04d29cde69585633.tar.gz
samba-992f1e6b8f86b346fddd266b04d29cde69585633.tar.bz2
samba-992f1e6b8f86b346fddd266b04d29cde69585633.zip
Add all the source files from the old CVS tree,
add the 5 missing chapters from the HOWTO and add jht's Samba by Example book. (This used to be commit 9fb5bcb93e57c5162b3ee6f9c7d777dc0269d100)
Diffstat (limited to 'docs/smbdotconf/misc')
-rw-r--r--docs/smbdotconf/misc/addsharecommand.xml59
-rw-r--r--docs/smbdotconf/misc/afsshare.xml16
-rw-r--r--docs/smbdotconf/misc/afsusernamemap.xml20
-rw-r--r--docs/smbdotconf/misc/available.xml14
-rw-r--r--docs/smbdotconf/misc/changesharecommand.xml58
-rw-r--r--docs/smbdotconf/misc/configfile.xml24
-rw-r--r--docs/smbdotconf/misc/copy.xml16
-rw-r--r--docs/smbdotconf/misc/defaultservice.xml32
-rw-r--r--docs/smbdotconf/misc/deletereadonly.xml14
-rw-r--r--docs/smbdotconf/misc/deletesharecommand.xml47
-rw-r--r--docs/smbdotconf/misc/dfreecommand.xml51
-rw-r--r--docs/smbdotconf/misc/dontdescend.xml20
-rw-r--r--docs/smbdotconf/misc/dosfilemode.xml18
-rw-r--r--docs/smbdotconf/misc/dosfiletimeresolution.xml25
-rw-r--r--docs/smbdotconf/misc/dosfiletimes.xml17
-rw-r--r--docs/smbdotconf/misc/fakedirectorycreatetimes.xml34
-rw-r--r--docs/smbdotconf/misc/followsymlinks.xml21
-rw-r--r--docs/smbdotconf/misc/fstype.xml17
-rw-r--r--docs/smbdotconf/misc/homedirmap.xml30
-rw-r--r--docs/smbdotconf/misc/include.xml18
-rw-r--r--docs/smbdotconf/misc/kernelchangenotify.xml17
-rw-r--r--docs/smbdotconf/misc/lockdirectory.xml16
-rw-r--r--docs/smbdotconf/misc/magicoutput.xml18
-rw-r--r--docs/smbdotconf/misc/magicscript.xml30
-rw-r--r--docs/smbdotconf/misc/messagecommand.xml72
-rw-r--r--docs/smbdotconf/misc/nishomedir.xml33
-rw-r--r--docs/smbdotconf/misc/panicaction.xml16
-rw-r--r--docs/smbdotconf/misc/piddirectory.xml13
-rw-r--r--docs/smbdotconf/misc/postexec.xml21
-rw-r--r--docs/smbdotconf/misc/preexec.xml26
-rw-r--r--docs/smbdotconf/misc/preexecclose.xml13
-rw-r--r--docs/smbdotconf/misc/preload.xml20
-rw-r--r--docs/smbdotconf/misc/remoteannounce.xml35
-rw-r--r--docs/smbdotconf/misc/remotebrowsesync.xml36
-rw-r--r--docs/smbdotconf/misc/rootpostexec.xml15
-rw-r--r--docs/smbdotconf/misc/rootpreexec.xml17
-rw-r--r--docs/smbdotconf/misc/rootpreexecclose.xml15
-rw-r--r--docs/smbdotconf/misc/setdirectory.xml16
-rw-r--r--docs/smbdotconf/misc/socketaddress.xml18
-rw-r--r--docs/smbdotconf/misc/timeoffset.xml15
-rw-r--r--docs/smbdotconf/misc/utmp.xml24
-rw-r--r--docs/smbdotconf/misc/utmpdirectory.xml21
-rw-r--r--docs/smbdotconf/misc/valid.xml18
-rw-r--r--docs/smbdotconf/misc/volume.xml12
-rw-r--r--docs/smbdotconf/misc/widelinks.xml18
-rw-r--r--docs/smbdotconf/misc/wtmpdirectory.xml25
46 files changed, 1131 insertions, 0 deletions
diff --git a/docs/smbdotconf/misc/addsharecommand.xml b/docs/smbdotconf/misc/addsharecommand.xml
new file mode 100644
index 0000000000..22e0ef28b7
--- /dev/null
+++ b/docs/smbdotconf/misc/addsharecommand.xml
@@ -0,0 +1,59 @@
+<samba:parameter name="add share command"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <parameter moreinfo="none">add share command</parameter> is used to define an
+ external program or script which will add a new service definition
+ to <filename moreinfo="none">smb.conf</filename>. In order to successfully
+ execute the <parameter moreinfo="none">add share command</parameter>, <command moreinfo="none">smbd</command>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </para>
+
+ <para>
+ When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+ <parameter moreinfo="none">add share command</parameter> with four parameters.
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><parameter moreinfo="none">configFile</parameter> - the location
+ of the global <filename moreinfo="none">smb.conf</filename> file.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">shareName</parameter> - the name of the new
+ share.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">pathName</parameter> - path to an **existing**
+ directory on disk.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">comment</parameter> - comment string to associate
+ with the new share.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ This parameter is only used for add file shares. To add printer shares,
+ see the <link linkend="ADDPRINTERCOMMAND"><parameter moreinfo="none">addprinter
+ command</parameter></link>.
+ </para>
+</description>
+
+<related>change share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/addshare</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/afsshare.xml b/docs/smbdotconf/misc/afsshare.xml
new file mode 100644
index 0000000000..d91b4a7cdb
--- /dev/null
+++ b/docs/smbdotconf/misc/afsshare.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="afs share"
+ context="S"
+ type="boolean"
+ advanced="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter controls whether special AFS features are enabled
+ for this share. If enabled, it assumes that the directory exported via
+ the <parameter>path</parameter> parameter is a local AFS import. The
+ special AFS features include the attempt to hand-craft an AFS token
+ if you enabled --with-fake-kaserver in configure.
+</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/afsusernamemap.xml b/docs/smbdotconf/misc/afsusernamemap.xml
new file mode 100644
index 0000000000..a404c14ad1
--- /dev/null
+++ b/docs/smbdotconf/misc/afsusernamemap.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="afs username map"
+ context="G"
+ type="string"
+ advanced="1"
+ xmlns:samba="http://samba.org/common">
+ <description>
+ <para>If you are using the fake kaserver AFS feature, you might
+ want to hand-craft the usernames you are creating tokens for.
+ For example this is necessary if you have users from several domain
+ in your AFS Protection Database. One possible scheme to code users
+ as DOMAIN+User as it is done by winbind with the + as a separator.
+ </para>
+
+ <para>The mapped user name must contain the cell name to log into,
+ so without setting this parameter there will be no token.</para>
+</description>
+
+<value type="default"/>
+<value type="example">%u@afs.samba.org</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/available.xml b/docs/smbdotconf/misc/available.xml
new file mode 100644
index 0000000000..4b358a9bef
--- /dev/null
+++ b/docs/smbdotconf/misc/available.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="available"
+ context="S"
+ basic="1" advanced="1" print="1"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter lets you &quot;turn off&quot; a service. If
+ <parameter moreinfo="none">available = no</parameter>, then <emphasis>ALL</emphasis>
+ attempts to connect to the service will fail. Such failures are
+ logged.</para>
+
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/changesharecommand.xml b/docs/smbdotconf/misc/changesharecommand.xml
new file mode 100644
index 0000000000..4b13afc04e
--- /dev/null
+++ b/docs/smbdotconf/misc/changesharecommand.xml
@@ -0,0 +1,58 @@
+<samba:parameter name="change share command"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <parameter moreinfo="none">change share command</parameter> is used to define an
+ external program or script which will modify an existing service definition
+ in <filename moreinfo="none">smb.conf</filename>. In order to successfully
+ execute the <parameter moreinfo="none">change share command</parameter>, <command moreinfo="none">smbd</command>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </para>
+
+ <para>
+ When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+ <parameter moreinfo="none">change share command</parameter> with four parameters.
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><parameter moreinfo="none">configFile</parameter> - the location
+ of the global <filename moreinfo="none">smb.conf</filename> file.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">shareName</parameter> - the name of the new
+ share.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">pathName</parameter> - path to an **existing**
+ directory on disk.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">comment</parameter> - comment string to associate
+ with the new share.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ This parameter is only used modify existing file shares definitions. To modify
+ printer shares, use the &quot;Printers...&quot; folder as seen when browsing the Samba host.
+ </para>
+</description>
+
+<related>add share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/addshare</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/configfile.xml b/docs/smbdotconf/misc/configfile.xml
new file mode 100644
index 0000000000..8c1128a934
--- /dev/null
+++ b/docs/smbdotconf/misc/configfile.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="config file"
+ context="G"
+ type="string"
+ hide="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This allows you to override the config file
+ to use, instead of the default (usually <filename moreinfo="none">smb.conf</filename>).
+ There is a chicken and egg problem here as this option is set
+ in the config file!</para>
+
+ <para>For this reason, if the name of the config file has changed
+ when the parameters are loaded then it will reload them from
+ the new config file.</para>
+
+ <para>This option takes the usual substitutions, which can
+ be very useful.</para>
+
+ <para>If the config file doesn't exist then it won't be loaded
+ (allowing you to special case the config files of just a few
+ clients).</para>
+</description>
+<value type="example">/usr/local/samba/lib/smb.conf.%m</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/copy.xml b/docs/smbdotconf/misc/copy.xml
new file mode 100644
index 0000000000..eba7e4c35c
--- /dev/null
+++ b/docs/smbdotconf/misc/copy.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="copy" context="S" hide="1" xmlns:samba="http://samba.org/common" type="string">
+<description>
+ <para>This parameter allows you to &quot;clone&quot; service
+ entries. The specified service is simply duplicated under the
+ current service's name. Any parameters specified in the current
+ section will override those in the section being copied.</para>
+
+ <para>This feature lets you set up a 'template' service and
+ create similar services easily. Note that the service being
+ copied must occur earlier in the configuration file than the
+ service doing the copying.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">otherservice</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/defaultservice.xml b/docs/smbdotconf/misc/defaultservice.xml
new file mode 100644
index 0000000000..66d9710f82
--- /dev/null
+++ b/docs/smbdotconf/misc/defaultservice.xml
@@ -0,0 +1,32 @@
+<samba:parameter name="default service"
+ context="G"
+ advanced="1" developer="1"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<synonym>default</synonym>
+<description>
+ <para>This parameter specifies the name of a service
+ which will be connected to if the service actually requested cannot
+ be found. Note that the square brackets are <emphasis>NOT</emphasis>
+ given in the parameter value (see example below).</para>
+
+ <para>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.</para>
+
+ <para>Typically the default service would be a <link linkend="GUESTOK">
+ <parameter moreinfo="none">guest ok</parameter></link>, <link linkend="READONLY">
+ <parameter moreinfo="none">read-only</parameter></link> service.</para>
+
+ <para>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 <parameter moreinfo="none">%S</parameter> to make
+ a wildcard service.</para>
+
+ <para>Note also that any &quot;_&quot; characters in the name of the service
+ used in the default service will get mapped to a &quot;/&quot;. This allows for
+ interesting things.</para>
+</description>
+<value type="default"></value>
+<value type="example">pub</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/deletereadonly.xml b/docs/smbdotconf/misc/deletereadonly.xml
new file mode 100644
index 0000000000..ed6daae925
--- /dev/null
+++ b/docs/smbdotconf/misc/deletereadonly.xml
@@ -0,0 +1,14 @@
+<samba:parameter name="delete readonly"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter allows readonly files to be deleted.
+ This is not normal DOS semantics, but is allowed by UNIX.</para>
+
+ <para>This option may be useful for running applications such
+ as rcs, where UNIX file ownership prevents changing file
+ permissions, and DOS semantics prevent deletion of a read only file.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/deletesharecommand.xml b/docs/smbdotconf/misc/deletesharecommand.xml
new file mode 100644
index 0000000000..d1b6a7ef29
--- /dev/null
+++ b/docs/smbdotconf/misc/deletesharecommand.xml
@@ -0,0 +1,47 @@
+<samba:parameter name="delete share command"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <parameter moreinfo="none">delete share command</parameter> is used to define an
+ external program or script which will remove an existing service
+ definition from <filename moreinfo="none">smb.conf</filename>. In order to successfully
+ execute the <parameter moreinfo="none">delete share command</parameter>, <command moreinfo="none">smbd</command>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </para>
+
+ <para>
+ When executed, <command moreinfo="none">smbd</command> will automatically invoke the
+ <parameter moreinfo="none">delete share command</parameter> with two parameters.
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para><parameter moreinfo="none">configFile</parameter> - the location
+ of the global <filename moreinfo="none">smb.conf</filename> file.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">shareName</parameter> - the name of
+ the existing service.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ This parameter is only used to remove file shares. To delete printer shares,
+ see the <link linkend="DELETEPRINTERCOMMAND"><parameter moreinfo="none">deleteprinter
+ command</parameter></link>.
+ </para>
+</description>
+
+<related>add share command</related>
+<related>delete share command</related>
+<value type="default"></value>
+<value type="example">/usr/local/bin/delshare</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/dfreecommand.xml b/docs/smbdotconf/misc/dfreecommand.xml
new file mode 100644
index 0000000000..7d51e3e2db
--- /dev/null
+++ b/docs/smbdotconf/misc/dfreecommand.xml
@@ -0,0 +1,51 @@
+<samba:parameter name="dfree command"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+
+ <para>The <parameter moreinfo="none">dfree command</parameter> setting
+ should only be used on systems where a problem occurs with the
+ internal disk space calculations. This has been known to happen
+ with Ultrix, but may occur with other operating systems. The
+ symptom that was seen was an error of &quot;Abort Retry
+ Ignore&quot; at the end of each directory listing.</para>
+
+ <para>This setting allows the replacement of the internal routines to
+ calculate the total disk space and amount available with an external
+ routine. The example below gives a possible script that might fulfill
+ this function.</para>
+
+ <para>The external program will be passed a single parameter indicating
+ a directory in the filesystem being queried. This will typically consist
+ of the string <filename moreinfo="none">./</filename>. The script should return two
+ integers in ASCII. The first should be the total disk space in blocks,
+ and the second should be the number of available blocks. An optional
+ third return value can give the block size in bytes. The default
+ blocksize is 1024 bytes.</para>
+
+ <para>Note: Your script should <emphasis>NOT</emphasis> be setuid or
+ setgid and should be owned by (and writeable only by) root!</para>
+
+ <para>Where the script dfree (which must be made executable) could be:</para>
+
+<para><programlisting format="linespecific">
+#!/bin/sh
+df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
+</programlisting></para>
+
+ <para>or perhaps (on Sys V based systems):</para>
+
+<para><programlisting format="linespecific">
+#!/bin/sh
+/usr/bin/df -k $1 | tail -1 | awk '{print $3&quot; &quot;$5}'
+</programlisting></para>
+
+ <para>Note that you may have to replace the command names with full path names on some systems.</para>
+
+</description>
+<value type="default"><comment>By default internal routines for
+ determining the disk capacity and remaining space will be used.</comment></value>
+<value type="example">/usr/local/samba/bin/dfree</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/dontdescend.xml b/docs/smbdotconf/misc/dontdescend.xml
new file mode 100644
index 0000000000..8cabd5ec01
--- /dev/null
+++ b/docs/smbdotconf/misc/dontdescend.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="dont descend"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>There are certain directories on some systems
+ (e.g., the <filename moreinfo="none">/proc</filename> tree under Linux) that are either not
+ of interest to clients or are infinitely deep (recursive). This
+ parameter allows you to specify a comma-delimited list of directories
+ that the server should always show as empty.</para>
+
+ <para>Note that Samba can be very fussy about the exact format
+ of the &quot;dont descend&quot; entries. For example you may need <filename moreinfo="none">
+ ./proc</filename> instead of just <filename moreinfo="none">/proc</filename>.
+ Experimentation is the best policy :-) </para>
+</description>
+
+<value type="default"></value>
+<value type="example">/proc,/dev</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/dosfilemode.xml b/docs/smbdotconf/misc/dosfilemode.xml
new file mode 100644
index 0000000000..7cf26eddc6
--- /dev/null
+++ b/docs/smbdotconf/misc/dosfilemode.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="dos filemode"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para> The default behavior in Samba is to provide
+ UNIX-like behavior where only the owner of a file/directory is
+ able to change the permissions on it. However, this behavior
+ is often confusing to DOS/Windows users. Enabling this parameter
+ allows a user who has write access to the file (by whatever
+ means) to modify the permissions on it. Note that a user
+ belonging to the group owning the file will not be allowed to
+ change permissions if the group is only granted read access.
+ Ownership of the file/directory is not changed, only the permissions
+ are modified.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/dosfiletimeresolution.xml b/docs/smbdotconf/misc/dosfiletimeresolution.xml
new file mode 100644
index 0000000000..a54db1940b
--- /dev/null
+++ b/docs/smbdotconf/misc/dosfiletimeresolution.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="dos filetime resolution"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Under the DOS and Windows FAT filesystem, the finest
+ granularity on time resolution is two seconds. Setting this parameter
+ for a share causes Samba to round the reported time down to the
+ nearest two second boundary when a query call that requires one second
+ resolution is made to <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry>.</para>
+
+ <para>This option is mainly used as a compatibility option for Visual
+ C++ when used against Samba shares. If oplocks are enabled on a
+ share, Visual C++ uses two different time reading calls to check if a
+ file has changed since it was last read. One of these calls uses a
+ one-second granularity, the other uses a two second granularity. As
+ the two second call rounds any odd second down, then if the file has a
+ timestamp of an odd number of seconds then the two timestamps will not
+ match and Visual C++ will keep reporting the file has changed. Setting
+ this option causes the two timestamps to match, and Visual C++ is
+ happy.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/dosfiletimes.xml b/docs/smbdotconf/misc/dosfiletimes.xml
new file mode 100644
index 0000000000..49891af439
--- /dev/null
+++ b/docs/smbdotconf/misc/dosfiletimes.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="dos filetimes"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Under DOS and Windows, if a user can write to a
+ file they can change the timestamp on it. Under POSIX semantics,
+ only the owner of the file or root may change the timestamp. By
+ default, Samba runs with POSIX semantics and refuses to change the
+ timestamp on a file if the user <command moreinfo="none">smbd</command> is acting
+ on behalf of is not the file owner. Setting this option to <constant>
+ yes</constant> allows DOS semantics and <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> will change the file
+timestamp as DOS requires.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/fakedirectorycreatetimes.xml b/docs/smbdotconf/misc/fakedirectorycreatetimes.xml
new file mode 100644
index 0000000000..0cff11c8c0
--- /dev/null
+++ b/docs/smbdotconf/misc/fakedirectorycreatetimes.xml
@@ -0,0 +1,34 @@
+<samba:parameter name="fake directory create times"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>NTFS and Windows VFAT file systems keep a create
+ time for all files and directories. This is not the same as the
+ ctime - status change time - that Unix keeps, so Samba by default
+ reports the earliest of the various times Unix does keep. Setting
+ this parameter for a share causes Samba to always report midnight
+ 1-1-1980 as the create time for directories.</para>
+
+ <para>This option is mainly used as a compatibility option for
+ Visual C++ when used against Samba shares. Visual C++ generated
+ makefiles have the object directory as a dependency for each object
+ file, and a make rule to create the directory. Also, when NMAKE
+ compares timestamps it uses the creation time when examining a
+ directory. Thus the object directory will be created if it does not
+ exist, but once it does exist it will always have an earlier
+ timestamp than the object files it contains.</para>
+
+ <para>However, Unix time semantics mean that the create time
+ reported by Samba will be updated whenever a file is created or
+ or deleted in the directory. NMAKE finds all object files in
+ the object directory. The timestamp of the last one built is then
+ compared to the timestamp of the object directory. If the
+ directory's timestamp if newer, then all object files
+ will be rebuilt. Enabling this option
+ ensures directories always predate their contents and an NMAKE build
+ will proceed as expected.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/followsymlinks.xml b/docs/smbdotconf/misc/followsymlinks.xml
new file mode 100644
index 0000000000..441a08d26c
--- /dev/null
+++ b/docs/smbdotconf/misc/followsymlinks.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="follow symlinks"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter allows the Samba administrator
+ to stop <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> from following symbolic
+ links in a particular share. Setting this
+ parameter to <constant>no</constant> prevents any file or directory
+ that is a symbolic link from being followed (the user will get an
+ error). This option is very useful to stop users from adding a
+ symbolic link to <filename moreinfo="none">/etc/passwd</filename> in their home
+ directory for instance. However it will slow filename lookups
+ down slightly.</para>
+
+ <para>This option is enabled (i.e. <command moreinfo="none">smbd</command> will
+ follow symbolic links) by default.</para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/fstype.xml b/docs/smbdotconf/misc/fstype.xml
new file mode 100644
index 0000000000..5a67a363a4
--- /dev/null
+++ b/docs/smbdotconf/misc/fstype.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="fstype"
+ context="S"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter allows the administrator to
+ configure the string that specifies the type of filesystem a share
+ is using that is reported by <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> when a client queries the filesystem type
+ for a share. The default type is <constant>NTFS</constant> for
+ compatibility with Windows NT but this can be changed to other
+ strings such as <constant>Samba</constant> or <constant>FAT
+ </constant> if required.</para>
+</description>
+<value type="default">NTFS</value>
+<value type="example">Samba</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/homedirmap.xml b/docs/smbdotconf/misc/homedirmap.xml
new file mode 100644
index 0000000000..1fbafaa5e4
--- /dev/null
+++ b/docs/smbdotconf/misc/homedirmap.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="homedir map"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+ <description>
+ <para>If<link linkend="NISHOMEDIR"><parameter moreinfo="none">nis homedir
+ </parameter></link> is <constant>yes</constant>, and <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> is also acting
+ as a Win95/98 <parameter moreinfo="none">logon server</parameter> then this parameter
+ specifies the NIS (or YP) map from which the server for the user's
+ home directory should be extracted. At present, only the Sun
+ auto.home map format is understood. The form of the map is:</para>
+
+ <para><command moreinfo="none">username server:/some/file/system</command></para>
+
+ <para>and the program will extract the servername from before
+ the first ':'. There should probably be a better parsing system
+ that copes with different map formats and also Amd (another
+ automounter) maps.</para>
+
+ <note><para>A working NIS client is required on
+ the system for this option to work.</para></note>
+</description>
+<related>nis homedir</related>
+<related>domain logons</related>
+
+<value type="default"></value>
+<value type="example">amd.homedir</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/include.xml b/docs/smbdotconf/misc/include.xml
new file mode 100644
index 0000000000..eac865ee01
--- /dev/null
+++ b/docs/smbdotconf/misc/include.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="include"
+ context="G"
+ type="string"
+ hide="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This allows you to include one config file
+ inside another. The file is included literally, as though typed
+ in place.</para>
+
+ <para>It takes the standard substitutions, except <parameter moreinfo="none">%u
+ </parameter>, <parameter moreinfo="none">%P</parameter> and <parameter moreinfo="none">%S</parameter>.
+</para>
+</description>
+
+<value type="default"></value>
+<value type="example">/usr/local/samba/lib/admin_smb.conf</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/kernelchangenotify.xml b/docs/smbdotconf/misc/kernelchangenotify.xml
new file mode 100644
index 0000000000..4f7e8f1419
--- /dev/null
+++ b/docs/smbdotconf/misc/kernelchangenotify.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="kernel change notify"
+ context="G"
+ type="boolean"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter specifies whether Samba should ask the
+ kernel for change notifications in directories so that
+ SMB clients can refresh whenever the data on the server changes.
+ </para>
+
+ <para>This parameter is only usd when your kernel supports
+ change notification to user programs, using the F_NOTIFY fcntl.
+ </para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/lockdirectory.xml b/docs/smbdotconf/misc/lockdirectory.xml
new file mode 100644
index 0000000000..0733778c5f
--- /dev/null
+++ b/docs/smbdotconf/misc/lockdirectory.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="lock directory"
+ context="G"
+ advanced="1" developer="1"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<synonym>lock dir</synonym>
+<description>
+ <para>This option specifies the directory where lock
+ files will be placed. The lock files are used to implement the
+ <link linkend="MAXCONNECTIONS"><parameter moreinfo="none">max connections</parameter>
+</link> option.</para>
+</description>
+
+<value type="default">${prefix}/var/locks</value>
+<value type="example">/var/run/samba/locks</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/magicoutput.xml b/docs/smbdotconf/misc/magicoutput.xml
new file mode 100644
index 0000000000..40f3a0e46d
--- /dev/null
+++ b/docs/smbdotconf/misc/magicoutput.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="magic output"
+ context="S"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter specifies the name of a file
+ which will contain output created by a magic script (see the
+ <link linkend="MAGICSCRIPT"><parameter moreinfo="none">magic script</parameter></link>
+ parameter below).</para>
+
+<warning><para>If two clients use the same <parameter moreinfo="none">magic script
+ </parameter> in the same directory the output file content
+ is undefined.</para></warning>
+</description>
+
+<value type="default">&lt;magic script name&gt;.out</value>
+<value type="example">myfile.txt</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/magicscript.xml b/docs/smbdotconf/misc/magicscript.xml
new file mode 100644
index 0000000000..ea06400a46
--- /dev/null
+++ b/docs/smbdotconf/misc/magicscript.xml
@@ -0,0 +1,30 @@
+<samba:parameter name="magic script"
+ context="S"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter specifies the name of a file which,
+ if opened, will be executed by the server when the file is closed.
+ This allows a UNIX script to be sent to the Samba host and
+ executed on behalf of the connected user.</para>
+
+ <para>Scripts executed in this way will be deleted upon
+ completion assuming that the user has the appropriate level
+ of privilege and the file permissions allow the deletion.</para>
+
+ <para>If the script generates output, output will be sent to
+ the file specified by the <link linkend="MAGICOUTPUT"><parameter moreinfo="none">
+ magic output</parameter></link> parameter (see above).</para>
+
+ <para>Note that some shells are unable to interpret scripts
+ containing CR/LF instead of CR as
+ the end-of-line marker. Magic scripts must be executable
+ <emphasis>as is</emphasis> on the host, which for some hosts and
+ some shells will require filtering at the DOS end.</para>
+
+ <para>Magic scripts are <emphasis>EXPERIMENTAL</emphasis> and
+ should <emphasis>NOT</emphasis> be relied upon.</para>
+</description>
+<value type="default"></value>
+<value type="example">user.csh</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/messagecommand.xml b/docs/smbdotconf/misc/messagecommand.xml
new file mode 100644
index 0000000000..36e52c8997
--- /dev/null
+++ b/docs/smbdotconf/misc/messagecommand.xml
@@ -0,0 +1,72 @@
+<samba:parameter name="message command"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This specifies what command to run when the
+ server receives a WinPopup style message.</para>
+
+ <para>This would normally be a command that would
+ deliver the message somehow. How this is to be done is
+ up to your imagination.</para>
+
+ <para>An example is:</para>
+
+ <para><command moreinfo="none">message command = csh -c 'xedit %s;rm %s' &amp;</command>
+ </para>
+
+ <para>This delivers the message using <command moreinfo="none">xedit</command>, then
+ removes it afterwards. <emphasis>NOTE THAT IT IS VERY IMPORTANT
+ THAT THIS COMMAND RETURN IMMEDIATELY</emphasis>. That's why I
+ have the '&amp;' on the end. If it doesn't return immediately then
+ your PCs may freeze when sending messages (they should recover
+ after 30 seconds, hopefully).</para>
+
+ <para>All messages are delivered as the global guest user.
+ The command takes the standard substitutions, although <parameter moreinfo="none">
+ %u</parameter> won't work (<parameter moreinfo="none">%U</parameter> may be better
+ in this case).</para>
+
+ <para>Apart from the standard substitutions, some additional
+ ones apply. In particular:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><parameter moreinfo="none">%s</parameter> = the filename containing
+ the message.</para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">%t</parameter> = the destination that
+ the message was sent to (probably the server name).</para>
+ </listitem>
+
+ <listitem>
+ <para><parameter moreinfo="none">%f</parameter> = who the message
+ is from.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>You could make this command send mail, or whatever else
+ takes your fancy. Please let us know of any really interesting
+ ideas you have.</para>
+
+ <para>Here's a way of sending the messages as mail to root:</para>
+
+ <para><command moreinfo="none">message command = /bin/mail -s 'message from %f on
+ %m' root &lt; %s; rm %s</command></para>
+
+ <para>If you don't have a message command then the message
+ won't be delivered and Samba will tell the sender there was
+ an error. Unfortunately WfWg totally ignores the error code
+ and carries on regardless, saying that the message was delivered.
+ </para>
+
+ <para>If you want to silently delete it then try:</para>
+
+ <para><command moreinfo="none">message command = rm %s</command></para>
+</description>
+<value type="default"></value>
+<value type="example">csh -c 'xedit %s; rm %s' &amp;</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/nishomedir.xml b/docs/smbdotconf/misc/nishomedir.xml
new file mode 100644
index 0000000000..84032a1b15
--- /dev/null
+++ b/docs/smbdotconf/misc/nishomedir.xml
@@ -0,0 +1,33 @@
+<samba:parameter name="nis homedir"
+ context="G"
+ type="boolean"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>Get the home share server from a NIS map. For
+ UNIX systems that use an automounter, the user's home directory
+ will often be mounted on a workstation on demand from a remote
+ server. </para>
+
+ <para>When the Samba logon server is not the actual home directory
+ server, but is mounting the home directories via NFS then two
+ network hops would be required to access the users home directory
+ if the logon server told the client to use itself as the SMB server
+ for home directories (one over SMB and one over NFS). This can
+ be very slow.</para>
+
+ <para>This option allows Samba to return the home share as
+ being on a different server to the logon server and as
+ long as a Samba daemon is running on the home directory server,
+ it will be mounted on the Samba client directly from the directory
+ server. When Samba is returning the home share to the client, it
+ will consult the NIS map specified in <link linkend="HOMEDIRMAP">
+ <parameter moreinfo="none">homedir map</parameter></link> and return the server
+ listed there.</para>
+
+ <para>Note that for this option to work there must be a working
+ NIS system and the Samba server with this option must also
+ be a logon server.</para>
+</description>
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/panicaction.xml b/docs/smbdotconf/misc/panicaction.xml
new file mode 100644
index 0000000000..9f55b550e7
--- /dev/null
+++ b/docs/smbdotconf/misc/panicaction.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="panic action"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This is a Samba developer option that allows a
+ system command to be called when either <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> or <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> crashes. This is usually used to
+draw attention to the fact that a problem occurred.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">&quot;/bin/sleep 90000&quot;</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/piddirectory.xml b/docs/smbdotconf/misc/piddirectory.xml
new file mode 100644
index 0000000000..ad13d2e598
--- /dev/null
+++ b/docs/smbdotconf/misc/piddirectory.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="pid directory"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This option specifies the directory where pid
+ files will be placed. </para>
+</description>
+
+<value type="default">${prefix}/var/locks</value>
+<value type="example">pid directory = /var/run/</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/postexec.xml b/docs/smbdotconf/misc/postexec.xml
new file mode 100644
index 0000000000..c32023c509
--- /dev/null
+++ b/docs/smbdotconf/misc/postexec.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="postexec"
+ context="S"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This option specifies a command to be run
+ whenever the service is disconnected. It takes the usual
+ substitutions. The command may be run as the root on some
+ systems.</para>
+
+ <para>An interesting example may be to unmount server
+ resources:</para>
+
+<para><command moreinfo="none">postexec = /etc/umount /cdrom</command></para>
+</description>
+<related>preexec</related>
+
+<value type="default"></value>
+<value type="example">echo \&quot;%u disconnected from %S from %m (%I)\&quot; &gt;&gt; /tmp/log</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/preexec.xml b/docs/smbdotconf/misc/preexec.xml
new file mode 100644
index 0000000000..905213aafa
--- /dev/null
+++ b/docs/smbdotconf/misc/preexec.xml
@@ -0,0 +1,26 @@
+<samba:parameter name="preexec"
+ context="S"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+ <synonym>exec</synonym>
+<description>
+ <para>This option specifies a command to be run whenever
+ the service is connected to. It takes the usual substitutions.</para>
+
+ <para>An interesting example is to send the users a welcome
+ message every time they log in. Maybe a message of the day? Here
+ is an example:</para>
+
+ <para><command moreinfo="none">preexec = csh -c 'echo \&quot;Welcome to %S!\&quot; | /usr/local/samba/bin/smbclient -M %m -I %I' &amp; </command></para>
+
+ <para>Of course, this could get annoying after a while :-)</para>
+
+ <para>See also <link linkend="PREEXECCLOSE"><parameter moreinfo="none">preexec close</parameter></link> and <link
+ linkend="POSTEXEC"><parameter moreinfo="none">postexec
+ </parameter></link>.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">echo \&quot;%u connected to %S from %m (%I)\&quot; &gt;&gt; /tmp/log</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/preexecclose.xml b/docs/smbdotconf/misc/preexecclose.xml
new file mode 100644
index 0000000000..9be5856e8b
--- /dev/null
+++ b/docs/smbdotconf/misc/preexecclose.xml
@@ -0,0 +1,13 @@
+<samba:parameter name="preexec close"
+ context="S"
+ type="boolean"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This boolean option controls whether a non-zero
+ return code from <link linkend="PREEXEC"><parameter moreinfo="none">preexec
+</parameter></link> should close the service being connected to.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/preload.xml b/docs/smbdotconf/misc/preload.xml
new file mode 100644
index 0000000000..53abba1f1b
--- /dev/null
+++ b/docs/smbdotconf/misc/preload.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="preload"
+ context="G"
+ advanced="1" developer="1"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<synonym>auto services</synonym>
+<description>
+ <para>This is a list of services that you want to be
+ automatically added to the browse lists. This is most useful
+ for homes and printers services that would otherwise not be
+ visible.</para>
+
+ <para>Note that if you just want all printers in your
+ printcap file loaded then the <link linkend="LOADPRINTERS">
+ <parameter moreinfo="none">load printers</parameter></link> option is easier.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">fred lp colorlp</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/remoteannounce.xml b/docs/smbdotconf/misc/remoteannounce.xml
new file mode 100644
index 0000000000..d573277d8c
--- /dev/null
+++ b/docs/smbdotconf/misc/remoteannounce.xml
@@ -0,0 +1,35 @@
+<samba:parameter name="remote announce"
+ context="G"
+ advanced="1" developer="1"
+ type="list"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry>to periodically announce itself
+ to arbitrary IP addresses with an arbitrary workgroup name.</para>
+
+ <para>This is useful if you want your Samba server to appear
+ in a remote workgroup for which the normal browse propagation
+ rules don't work. The remote workgroup can be anywhere that you
+ can send IP packets to.</para>
+
+ <para>For example:</para>
+
+ <para><command moreinfo="none">remote announce = 192.168.2.255/SERVERS
+ 192.168.4.255/STAFF</command></para>
+
+ <para>the above line would cause <command moreinfo="none">nmbd</command> 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 <link linkend="WORKGROUP"><parameter moreinfo="none">workgroup</parameter></link>
+ parameter is used instead.</para>
+
+ <para>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.</para>
+
+<para>See <link linkend="NetworkBrowsing"/>.</para>
+</description>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/remotebrowsesync.xml b/docs/smbdotconf/misc/remotebrowsesync.xml
new file mode 100644
index 0000000000..e3acd1c82d
--- /dev/null
+++ b/docs/smbdotconf/misc/remotebrowsesync.xml
@@ -0,0 +1,36 @@
+<samba:parameter name="remote browse sync"
+ context="G"
+ advanced="1" developer="1"
+ type="list"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This option allows you to setup <citerefentry><refentrytitle>nmbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> to periodically request
+ synchronization of browse lists with the master browser of a Samba
+ server that is on a remote segment. This option will allow you to
+ gain browse lists for multiple workgroups across routed networks. This
+ is done in a manner that does not work with any non-Samba servers.</para>
+
+ <para>This is useful if you want your Samba server and all local
+ clients to appear in a remote workgroup for which the normal browse
+ propagation rules don't work. The remote workgroup can be anywhere
+ that you can send IP packets to.</para>
+
+ <para>For example:</para>
+
+ <para><command moreinfo="none">remote browse sync = 192.168.2.255 192.168.4.255</command></para>
+
+ <para>the above line would cause <command moreinfo="none">nmbd</command> to request
+ the master browser on the specified subnets or addresses to
+ synchronize their browse lists with the local server.</para>
+
+ <para>The IP addresses you choose would normally be the broadcast
+ addresses of the remote networks, but can also be the IP addresses
+ of known browse masters if your network config is that stable. If
+ a machine IP address is given Samba makes NO attempt to validate
+ that the remote machine is available, is listening, nor that it
+ is in fact the browse master on its segment.</para>
+</description>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/rootpostexec.xml b/docs/smbdotconf/misc/rootpostexec.xml
new file mode 100644
index 0000000000..b60a6e9152
--- /dev/null
+++ b/docs/smbdotconf/misc/rootpostexec.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="root postexec"
+ context="S"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This is the same as the <parameter moreinfo="none">postexec</parameter>
+ parameter except that the command is run as root. This
+ is useful for unmounting filesystems
+ (such as CDROMs) after a connection is closed.</para>
+</description>
+
+<related>postexec</related>
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/rootpreexec.xml b/docs/smbdotconf/misc/rootpreexec.xml
new file mode 100644
index 0000000000..5c1267c22f
--- /dev/null
+++ b/docs/smbdotconf/misc/rootpreexec.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="root preexec"
+ context="S"
+ type="string"
+ advanced="1" wizard="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This is the same as the <parameter moreinfo="none">preexec</parameter>
+ parameter except that the command is run as root. This
+ is useful for mounting filesystems (such as CDROMs) when a
+ connection is opened.</para>
+</description>
+
+<related>preexec</related>
+<related>preexec close</related>
+
+<value type="default"></value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/rootpreexecclose.xml b/docs/smbdotconf/misc/rootpreexecclose.xml
new file mode 100644
index 0000000000..66808dfcf0
--- /dev/null
+++ b/docs/smbdotconf/misc/rootpreexecclose.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="root preexec close"
+ context="S"
+ type="boolean"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This is the same as the <parameter moreinfo="none">preexec close
+ </parameter> parameter except that the command is run as root.</para>
+</description>
+
+<related>preexec</related>
+<related>preexec close</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/setdirectory.xml b/docs/smbdotconf/misc/setdirectory.xml
new file mode 100644
index 0000000000..435c77fd03
--- /dev/null
+++ b/docs/smbdotconf/misc/setdirectory.xml
@@ -0,0 +1,16 @@
+<samba:parameter name="set directory"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>If <command moreinfo="none">set directory = no</command>, then
+ users of the service may not use the setdir command to change
+ directory.</para>
+
+ <para>The <command moreinfo="none">setdir</command> command is only implemented
+ in the Digital Pathworks client. See the Pathworks documentation
+ for details.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/socketaddress.xml b/docs/smbdotconf/misc/socketaddress.xml
new file mode 100644
index 0000000000..803288c820
--- /dev/null
+++ b/docs/smbdotconf/misc/socketaddress.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="socket address"
+ context="G"
+ type="string"
+ developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This option allows you to control what
+ address Samba will listen for connections on. This is used to
+ support multiple virtual interfaces on the one server, each
+ with a different configuration.</para>
+
+ <para>By default Samba will accept connections on any
+ address.</para>
+</description>
+
+<value type="default"></value>
+<value type="example">192.168.2.20</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/timeoffset.xml b/docs/smbdotconf/misc/timeoffset.xml
new file mode 100644
index 0000000000..908ffeb55c
--- /dev/null
+++ b/docs/smbdotconf/misc/timeoffset.xml
@@ -0,0 +1,15 @@
+<samba:parameter name="time offset"
+ context="G"
+ type="integer"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter is a setting in minutes to add
+ to the normal GMT to local time conversion. This is useful if
+ you are serving a lot of PCs that have incorrect daylight
+ saving time handling.</para>
+</description>
+
+<value type="default">0</value>
+<value type="example">60</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/utmp.xml b/docs/smbdotconf/misc/utmp.xml
new file mode 100644
index 0000000000..3bc54893f6
--- /dev/null
+++ b/docs/smbdotconf/misc/utmp.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="utmp"
+ context="G"
+ type="boolean"
+ developer="1"
+ xmlns:samba="http://samba.org/common">
+ <description>
+ <para>This boolean parameter is only available if
+ Samba has been configured and compiled with the option <command moreinfo="none">
+ --with-utmp</command>. If set to <constant>yes</constant> 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.</para>
+
+ <para>Due to the requirements of the utmp record, we
+ are required to create a unique identifier for the
+ incoming user. Enabling this option creates an n^2
+ algorithm to find this number. This may impede
+ performance on large installations. </para>
+</description>
+
+<related>utmp directory</related>
+
+<value type="default">no</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/utmpdirectory.xml b/docs/smbdotconf/misc/utmpdirectory.xml
new file mode 100644
index 0000000000..bf515d9883
--- /dev/null
+++ b/docs/smbdotconf/misc/utmpdirectory.xml
@@ -0,0 +1,21 @@
+<samba:parameter name="utmp directory"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter is only available if Samba has
+ been configured and compiled with the option <command moreinfo="none">
+ --with-utmp</command>. 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. By default this is
+ not set, meaning the system will use whatever utmp file the
+ native system is set to use (usually
+ <filename moreinfo="none">/var/run/utmp</filename> on Linux).</para>
+</description>
+
+<related>utmp</related>
+
+<value type="default"><comment>Determined automatically</comment></value>
+<value type="example">/var/run/utmp</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/valid.xml b/docs/smbdotconf/misc/valid.xml
new file mode 100644
index 0000000000..7c3806ef02
--- /dev/null
+++ b/docs/smbdotconf/misc/valid.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="-valid"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para> This parameter indicates whether a share is
+ valid and thus can be used. When this parameter is set to false,
+ the share will be in no way visible nor accessible.
+ </para>
+
+ <para>
+ This option should not be
+ used by regular users but might be of help to developers.
+ Samba uses this option internally to mark shares as deleted.
+ </para>
+</description>
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/volume.xml b/docs/smbdotconf/misc/volume.xml
new file mode 100644
index 0000000000..4f5ac705fa
--- /dev/null
+++ b/docs/smbdotconf/misc/volume.xml
@@ -0,0 +1,12 @@
+<samba:parameter name="volume"
+ context="S"
+ type="string"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This allows you to override the volume label
+ returned for a share. Useful for CDROMs with installation programs
+ that insist on a particular volume label.</para>
+</description>
+
+<value type="default"><comment>the name of the share</comment></value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/widelinks.xml b/docs/smbdotconf/misc/widelinks.xml
new file mode 100644
index 0000000000..2f664b9059
--- /dev/null
+++ b/docs/smbdotconf/misc/widelinks.xml
@@ -0,0 +1,18 @@
+<samba:parameter name="wide links"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter controls whether or not links
+ in the UNIX file system may be followed by the server. Links
+ that point to areas within the directory tree exported by the
+ server are always allowed; this parameter controls access only
+ to areas that are outside the directory tree being exported.</para>
+
+ <para>Note that setting this parameter can have a negative
+ effect on your server performance due to the extra system calls
+ that Samba has to do in order to perform the link checks.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>
diff --git a/docs/smbdotconf/misc/wtmpdirectory.xml b/docs/smbdotconf/misc/wtmpdirectory.xml
new file mode 100644
index 0000000000..22948f504c
--- /dev/null
+++ b/docs/smbdotconf/misc/wtmpdirectory.xml
@@ -0,0 +1,25 @@
+<samba:parameter name="wtmp directory"
+ context="G"
+ type="string"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter is only available if Samba has
+ been configured and compiled with the option <command moreinfo="none">
+ --with-utmp</command>. It specifies a directory pathname that is
+ used to store the wtmp or wtmpx files (depending on the UNIX system) that
+ record user connections to a Samba server. The difference with
+ the utmp directory is the fact that user info is kept after a user
+ has logged out.</para>
+
+<para>
+ By default this is
+ not set, meaning the system will use whatever utmp file the
+ native system is set to use (usually
+ <filename moreinfo="none">/var/run/wtmp</filename> on Linux).</para>
+</description>
+
+<related>utmp</related>
+<value type="default"/>
+<value type="example">/var/log/wtmp</value>
+</samba:parameter>