svn commit: samba-docs r735 - in trunk/Samba3-HOWTO: .
jht at samba.org
jht at samba.org
Fri Jul 1 15:35:19 GMT 2005
Author: jht
Date: 2005-07-01 15:35:19 +0000 (Fri, 01 Jul 2005)
New Revision: 735
WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=735
Log:
Add index entries, fix lingo.
Modified:
trunk/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml
trunk/Samba3-HOWTO/index.xml
Changeset:
Modified: trunk/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml
===================================================================
--- trunk/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml 2005-07-01 09:25:51 UTC (rev 734)
+++ trunk/Samba3-HOWTO/TOSHARG-ConfigSmarts.xml 2005-07-01 15:35:19 UTC (rev 735)
@@ -8,30 +8,42 @@
<title>Advanced Configuration Techniques</title>
<para>
+<indexterm><primary>configuration techniques</primary></indexterm>
+<indexterm><primary>include</primary></indexterm>
Since the release of the first edition of this book there have been repeated requests to better document
configuration techniques that may help a network administrator to get more out of Samba. Some users have asked
for documentation regarding the use of the <smbconfoption name="include">file-name</smbconfoption> parameter.
</para>
<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>multiple server personalities</primary></indexterm>
Commencing around mid-2004 there has been increasing interest in the ability to host multiple Samba servers on
one machine. There has also been an interest in the hosting of multiple Samba server personalities on one
server.
</para>
<para>
-Feedback from technical reviewers made the inclusion of this chapter a necessity. So finally, here is an attempt
-to answer the questions that have to date not been adequately addressed. Additional user input is welcome as
+<indexterm><primary>technical reviewers</primary></indexterm>
+<indexterm><primary>reviewers</primary></indexterm>
+Feedback from technical reviewers made the inclusion of this chapter a necessity. So, here is an
+answer the questions that have to date not been adequately addressed. Additional user input is welcome as
it will help this chapter to mature. What is presented here is just a small beginning.
</para>
<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>multiple hosting</primary></indexterm>
+<indexterm><primary>domain controllers</primary></indexterm>
There are a number of ways in which multiple servers can be hosted on a single Samba server. Multiple server
hosting makes it possible to host multiple domain controllers on one machine. Each such machine is
independent, and each can be stopped or started without affecting another.
</para>
<para>
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>DMS</primary></indexterm>
+<indexterm><primary>anonymous server</primary></indexterm>
Sometimes it is desirable to host multiple servers, each with its own security mode. For example, a single
UNIX/Linux host may be a domain member server (DMS) as well as a generic anonymous print server. In this case,
only domain member machines and domain users can access the DMS, but even guest users can access the generic
@@ -40,8 +52,11 @@
</para>
<para>
+<indexterm><primary>separate servers</primary></indexterm>
+<indexterm><primary></primary></indexterm>
Some environments dictate the need to have separate servers, each with their own resources, each of which are
-accessible only by certain users or groups. This is one of the simple, but highly effective, capabilities
+accessible only by certain users or groups. This is one of the simple, but highly effective, ways that Samba
+can replace many physical Windows servers in one Samba installation.
</para>
<sect1>
@@ -54,6 +69,13 @@
<title>Multiple Server Hosting</title>
<para>
+<indexterm><primary>multiple server hosting</primary></indexterm>
+<indexterm><primary>separate instances</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>winbindd</primary></indexterm>
+<indexterm><primary>recompiling</primary></indexterm>
+<indexterm><primary>TDB</primary></indexterm>
The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own
configuration file. This method is complicated by the fact that each instance of &nmbd;, &smbd; and &winbindd;
must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by
@@ -63,6 +85,10 @@
</para>
<para>
+<indexterm><primary>independent</primary></indexterm>
+<indexterm><primary>listen own socket</primary></indexterm>
+<indexterm><primary>socket</primary></indexterm>
+<indexterm><primary>SID</primary></indexterm>
Each instance should operate on its own IP address (that independent IP address can be an IP Alias).
Each instance of &nmbd;, &smbd; and &winbindd; should listen only on its own IP socket. This can be secured
using the <smbconfoption name="socket address"/> parameter. Each instance of the Samba server will have its
@@ -70,6 +96,15 @@
</para>
<para>
+<indexterm><primary>multiple server hosting</primary></indexterm>
+<indexterm><primary>private dir</primary></indexterm>
+<indexterm><primary>pid directory</primary></indexterm>
+<indexterm><primary>lock directory</primary></indexterm>
+<indexterm><primary>interfaces</primary></indexterm>
+<indexterm><primary>bind interfaces only</primary></indexterm>
+<indexterm><primary>netbios name</primary></indexterm>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>socket address</primary></indexterm>
The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of
process management and start up. The &smb.conf; parameters that must be carefully configured includes:
<smbconfoption name="private dir"/>, <smbconfoption name="pid directory"/>,<smbconfoption name="lock
@@ -78,7 +113,10 @@
</para>
<para>
-Those who elect to use this method of creating multiple Samba servers must have the ability to read and follow
+<indexterm><primary>multiple servers</primary></indexterm>
+<indexterm><primary>contribute</primary></indexterm>
+<indexterm><primary>comprehensive documentation</primary></indexterm>
+Those who elect to create multiple Samba servers should have the ability to read and follow
the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of
this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and
if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting
@@ -91,6 +129,9 @@
<title>Multiple Virtual Server Personalities</title>
<para>
+<indexterm><primary>multiple virtual servers</primary></indexterm>
+<indexterm><primary>netbios alias</primary></indexterm>
+<indexterm><primary>meta-services</primary></indexterm>
Samba has the ability to host multiple virtual servers, each of which have their own personality. This is
achieved by configuring an &smb.conf; file that is common to all personalities hosted. Each server
personality is hosted using its own <smbconfoption name="netbios alias"/> name, and each has its own distinct
@@ -98,13 +139,22 @@
</para>
<para>
+<indexterm><primary>workgroup</primary></indexterm>
+<indexterm><primary>security</primary></indexterm>
+<indexterm><primary>netbios aliases</primary></indexterm>
When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup.
Only the primary server can be a domain member or a domain controller. The personality is defined by the
combination of the <smbconfoption name="security"/> mode it is operating in, the <smbconfoption name="netbios
-alias"/> it has, and the <smbconfoption name="workgroup"/> that is defined for it.
+aliases"/> it has, and the <smbconfoption name="workgroup"/> that is defined for it.
</para>
<para>
+<indexterm><primary>NetBIOS name</primary></indexterm>
+<indexterm><primary>NetBIOS-less SMB</primary></indexterm>
+<indexterm><primary>smb ports</primary></indexterm>
+<indexterm><primary>TCP port 139</primary></indexterm>
+<indexterm><primary>TCP port 445</primary></indexterm>
+<indexterm><primary>%L</primary></indexterm>
This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services.
If run using NetBIOS mode (the most common method) it is important that the parameter <smbconfoption name="smb
ports">139</smbconfoption> should be specified in the primary &smb.conf; file. Failure to do this will result
@@ -112,13 +162,17 @@
the functionality that is specified in the primary &smb.conf; file. The use of NetBIOS over TCP/IP using only
TCP port 139 means that the use of the <literal>%L</literal> macro is fully enabled. If the <smbconfoption
name="smb ports">139</smbconfoption> is not specified (the default is <parameter>445 139</parameter>, or if
-the value of this parameter is set at <parameter>139 445</parameter> then the <literal>%L</literal> parameter
+the value of this parameter is set at <parameter>139 445</parameter> then the <literal>%L</literal> macro
is not serviceable.
</para>
<para>
+<indexterm><primary>host multiple servers</primary></indexterm>
+<indexterm><primary>multiple personality</primary></indexterm>
+<indexterm><primary>NetBIOS-less</primary></indexterm>
+<indexterm><primary>%i macro</primary></indexterm>
It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB
-port), in which case the <literal>%i</literal> parameter can be used to provide separate server identities (by
+port), in which case the <literal>%i</literal> macro can be used to provide separate server identities (by
IP Address). Each can have its own <smbconfoption name="security"/> mode. It will be necessary to use the
<smbconfoption name="interfaces"/>, <smbconfoption name="bind interfaces only"/> and IP aliases in addition to
the <smbconfoption name="netbios name"/> parameters to create the virtual servers. This method is considerably
@@ -126,6 +180,7 @@
</para>
<para>
+<indexterm><primary>anonymous file server</primary></indexterm>
Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only
Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it
is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here
@@ -139,6 +194,10 @@
</para>
<para>
+<indexterm><primary>/etc/samba</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>smb.conf</primary></indexterm>
The &smb.conf; file for the master server is shown in <link linkend="elastic">Elastic smb.conf File</link>.
This file is placed in the <filename>/etc/samba</filename> directory. Only the &nmbd; and the &smbd; daemons
are needed. When started the server will appear in Windows Network Neighborhood as the machine
@@ -185,6 +244,7 @@
</example>
<para>
+<indexterm><primary>smb-cdserver.conf</primary></indexterm>
The configuration file for the CDROM server is listed in <link linkend="cdserver">CDROM Server
smb-cdserver.conf file</link>. This file is called <filename>smb-cdserver.conf</filename> and it should be
located in the <filename>/etc/samba</filename> directory. Machines that are in the workgroup
@@ -210,6 +270,10 @@
</example>
<para>
+<indexterm><primary>different resources</primary></indexterm>
+<indexterm><primary>separate workgroups</primary></indexterm>
+<indexterm><primary>read-only access</primary></indexterm>
+<indexterm><primary>nobody account</primary></indexterm>
The two servers have different resources and are in separate workgroups. The server <literal>ELASTIC</literal>
can only be accessed by uses who have an appropriate account on the host server. All users will be able to
access the CDROM data that is stored in the <filename>/export/cddata</filename> directory. File system
@@ -223,6 +287,9 @@
<title>Multiple Virtual Server Hosting</title>
<para>
+<indexterm><primary>primary domain controller</primary></indexterm>
+<indexterm><primary>extra machine</primary></indexterm>
+<indexterm><primary>same domain/workgroup</primary></indexterm>
In this example, the requirement is for a primary domain controller for the domain called
<literal>MIDEARTH</literal>. The PDC will be called <literal>MERLIN</literal>. An extra machine called
<literal>SAURON</literal> is required. Each machine will have only its own shares. Both machines belong to the
@@ -230,6 +297,9 @@
</para>
<para>
+<indexterm><primary>master smb.conf</primary></indexterm>
+<indexterm><primary>/etc/samba</primary></indexterm>
+<indexterm><primary></primary></indexterm>
The master &smb.conf; file is shown in <link linkend="mastersmbc">the Master smb.conf File Global Section</link>.
The two files that specify the share information for each server are shown in <link linkend="merlinsmbc">the
smb-merlin.conf File Share Section</link>, and <link linkend="sauronsmbc">the smb-sauron.conf File Share
Modified: trunk/Samba3-HOWTO/index.xml
===================================================================
--- trunk/Samba3-HOWTO/index.xml 2005-07-01 09:25:51 UTC (rev 734)
+++ trunk/Samba3-HOWTO/index.xml 2005-07-01 15:35:19 UTC (rev 735)
@@ -164,7 +164,7 @@
<!-- Comment out the following line to include the manpages.
*Please* do not commit with the line below enabled! -->
<!-- <xi:include href="manpages.xml"/> -->
- <xi:include href="manpages.xml"/>
+ <!-- <xi:include href="manpages.xml"/> -->
<xi:include href="http://www.gnu.org/licenses/gpl.xml"/>
<xi:include href="TOSHARG-glossary.xml"/>
More information about the samba-cvs
mailing list