From e11106238fa997452f8e7ae9304a50fc38761322 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Thu, 24 Apr 2008 11:23:36 +0200 Subject: manpages: update the section about registry configuration in smb.conf.5 Michael (This used to be commit 27bc3ac03f8be222814ff7b77cb3e50b3167a1ef) --- docs-xml/manpages-3/smb.conf.5.xml | 69 ++++++++++++++++++++++++-------------- 1 file changed, 43 insertions(+), 26 deletions(-) (limited to 'docs-xml') diff --git a/docs-xml/manpages-3/smb.conf.5.xml b/docs-xml/manpages-3/smb.conf.5.xml index ff94ab696e..b6d27f4ce7 100644 --- a/docs-xml/manpages-3/smb.conf.5.xml +++ b/docs-xml/manpages-3/smb.conf.5.xml @@ -725,44 +725,61 @@ chmod 1770 /usr/local/samba/lib/usershares Starting with Samba version 3.2.0, the capability to store Samba configuration in the registry is available. + The configuration is stored in the registry key + HKLM\Software\Samba\smbconf. There are two levels of registry configuration: Share definitions stored in registry are used. This is triggered by setting the global - parameter registry shares to yes - in smb.conf. + parameter registry shares + to yes in smb.conf. - Note: Shares defined in smb.conf - always take priority over - shares of the same name defined in registry. - - - Global smb.conf options stored in - registry are used. This is triggered by the - parameter registry in - the [global] section of smb.conf. - This removes everything that has been read from config files + The registry shares are loaded not at startup but + on demand at runtime by smbd. + Shares defined in smb.conf take + priority over shares of the same name defined in + registry. + + + Global smb.conf + options stored in registry are used. This can be activated + in two different ways: + + Firstly, a registry only configuration is triggered + by setting + registry + in the [global] section of smb.conf. + This resets everything that has been read from config files to this point and reads the content of the global configuration section from the registry. - Activation of global registry options automatically - activates registry shares. In this case, no share definitions - from smb.conf are read: This is a registry only configuration - with the advantage that share definitions are not read - in a bulk at startup time but on demand when a share is - accessed. - + This is the recommended method of using registry based + configuration. + + Secondly, a mixed configuration can be activated + by a special new meaning of the parameter + registry + in the [global] section of smb.conf. + This reads the global options from registry with the same + priorities as for an include of a text file. + This may be especially useful in cases where an initial + configuration is needed to access the registry. + + Activation of global registry options automatically + activates registry shares. So in the registry only case, + shares are loaded on demand only. + - Caveat: To make registry-based configurations foolproof at least to a - certain extent, the use - of lock directory, - config backend, and - include inside the registry - configuration has been disabled. Especially, by changing the + Note: To make registry-based configurations foolproof + at least to a certain extent, the use + of lock directory and + config backend + inside the registry configuration has been disabled: + Especially by changing the lock directory inside the registry configuration, one would create a broken setup where the daemons do not see the configuration they loaded once it is active. @@ -770,7 +787,7 @@ chmod 1770 /usr/local/samba/lib/usershares The registry configuration can be accessed with - tools like regedit or net rpc + tools like regedit or net (rpc) registry in the key HKLM\Software\Samba\smbconf. -- cgit