summaryrefslogtreecommitdiff
path: root/docs/manpages-3
diff options
context:
space:
mode:
authorMichael Adam <obnox@samba.org>2007-06-22 22:44:13 +0000
committerGerald W. Carter <jerry@samba.org>2008-04-23 08:47:33 -0500
commit31e61423b9f7b708dcb79b7932b9c3d582988d5f (patch)
tree7824d001df4e748ed515bf147af1adee70f01b4e /docs/manpages-3
parent1846e7c767fd20e904f30c7eb719c7d56f56553e (diff)
downloadsamba-31e61423b9f7b708dcb79b7932b9c3d582988d5f.tar.gz
samba-31e61423b9f7b708dcb79b7932b9c3d582988d5f.tar.bz2
samba-31e61423b9f7b708dcb79b7932b9c3d582988d5f.zip
Add an initial amount of documentation of registry based
configuration to smb.conf(5). This explains registry shares and registry global options and mentions "net conf". This will be in 3.0.26, but Jerry told me to commit this anyways. The plan is to branch the doc for 3.0.25b from r1126 (say). I could not check the result since I could not get the manpages built correctly on any system I tried. So the output needs to be checked - sorry, I will fix my environment later... Michael (This used to be commit 2195dc476f4946ff062b62cf29d1b330263507bc)
Diffstat (limited to 'docs/manpages-3')
-rw-r--r--docs/manpages-3/smb.conf.5.xml78
1 files changed, 78 insertions, 0 deletions
diff --git a/docs/manpages-3/smb.conf.5.xml b/docs/manpages-3/smb.conf.5.xml
index 83fff41f80..ff527c1f53 100644
--- a/docs/manpages-3/smb.conf.5.xml
+++ b/docs/manpages-3/smb.conf.5.xml
@@ -712,6 +712,84 @@ chmod 1770 /usr/local/samba/lib/usershares
</refsect1>
<refsect1>
+ <title>REGISTRY-BASED CONFIGURATION</title>
+
+ <para>
+ Starting with Samba version 3.0.26, the capability to
+ store Samba configuration in the registry is available.
+ There are two levels of registry configuration.
+ </para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore" numeration="arabic">
+ <listitem><para>Share definitions stored in registry are used.
+ This is triggered by setting the global parameter
+ <parameter>registry shares</parameter> to
+ <term>yes</term> in <term>smb.conf</term>.
+ </para>
+ <para>Note: Shares defined in <term>smb.conf</term> always take priority over
+ shares of the same name defined in registry.
+ </para></listitem>
+
+ <listitem><para>Global <term>smb.conf</term> options stored in
+ registry are used. This
+ is triggered by a new special meaning of the
+ parameter <parameter>include = registry</parameter> in
+ the [global] section of <term>smb.conf</term>.
+ This reads the content of
+ the global configuration section from the regsitry
+ and includes the result with the same priorities as
+ an include of a text file. Activation of global
+ registry options automatically activates registry
+ shares.
+ </para></listitem>
+ </orderedlist>
+
+ <para>
+ Even when global registry options are used, the initial source of
+ configuration is still the <term>smb.conf</term> file.
+ It is this possible though, to produce a registry-only configuration
+ with a minimal configuration file like this:
+<programlisting>
+ <smbconfsection name="[global]"/>
+ <smbconfoption name="include">registry</smbconfoption>
+</programlisting>
+ This is also currently the only supported configuration with global
+ registry options activated. More precisely, it is only supported to
+ specify options in <term>smb.conf</term> <emph>before</emph> the
+ occurrence of <parameter>include = registry</parameter>.
+ </para>
+
+ <para>
+ Caveat: To make registry-based configurations foolprof at least to a
+ certain extent, the use of <parameter>lock directory</parameter>
+ and <parameter>include</parameter> inside the registry
+ configuration has been disabled. Especially, by changing the
+ <parameter>lock directory</parameter> inside the registry
+ configuration, one would create a broken setup where the daemons
+ do not see the configuration they loaded once it is active. This
+ phenomenon can of course also be triggered by specifying
+ <parameter>lock directory</parameter> after the
+ <parameter>include = registry</parameter> directive. This is why
+ this type of configuration is classified "unsupported" above.
+ </para>
+
+ <para>
+ The registry configuration can be accessed with
+ tools like <term>regedit</term> or <term>net rpc
+ registry</term> in the key
+ <term>HKLM\Software\Samba\smbconf</term>.
+
+ More conveniently, the <term>conf</term> subcommand of the
+ <citerefentry><refentrytitle>net</refentrytitle>
+ <manvolnum>7</manvolnum></citerefentry> utility
+ offers a dedicated interface to read and write the
+ registry based configuration locally, i.e. directly
+ on the server.
+ </para>
+
+</refsect1>
+
+<refsect1>
<title>EXPLANATION OF EACH PARAMETER</title>
<samba:parameterlist>