~zulcss/samba/server-dailies-3.4

<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�34.�Advanced Configuration Techniques</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="largefile.html" title="Chapter�33.�Handling Large Directories"><link rel="next" href="migration.html" title="Part�IV.�Migration and Updating"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�34.�Advanced Configuration Techniques</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="cfgsmarts"></a>Chapter�34.�Advanced Configuration Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">June 30, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="cfgsmarts.html#id2673899">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="cfgsmarts.html#id2673908">Multiple Server Hosting</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2674305">Multiple Virtual Server Personalities</a></span></dt><dt><span class="sect2"><a href="cfgsmarts.html#id2675319">Multiple Virtual Server Hosting</a></span></dt></dl></dd></dl></div><p>

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 <a class="link" href="smb.conf.5.html#INCLUDE" target="_top">include = file-name</a> parameter.

</p><p>

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.

</p><p>

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.

</p><p>

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.

</p><p>

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

print server. Another example of a situation where it may be beneficial to host a generic (anonymous) server

is to host a CDROM server.

</p><p>

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, ways that Samba

can replace many physical Windows servers in one Samba installation.

</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2673899"></a>Implementation</h2></div></div></div><p>

</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2673908"></a>Multiple Server Hosting</h3></div></div></div><p>

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 <span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span>

must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by

<span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span> can be enabled either by recompiling Samba for each server hosted so each has its

own default TDB directories, or by configuring these in the <code class="filename">smb.conf</code> file, in which case each instance of

<span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span> must be told to start up with its own <code class="filename">smb.conf</code> configuration file.

</p><p>

Each instance should operate on its own IP address (that independent IP address can be an IP Alias).

Each instance of <span class="application">nmbd</span>, <span class="application">smbd</span> and <span class="application">winbindd</span> should listen only on its own IP socket. This can be secured

using the <a class="link" href="smb.conf.5.html#SOCKETADDRESS" target="_top">socket address</a> parameter. Each instance of the Samba server will have its

own SID also, this means that the servers are discrete and independent of each other.

</p><p>

The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of

process management and start up. The <code class="filename">smb.conf</code> parameters that must be carefully configured includes:

<a class="link" href="smb.conf.5.html#PRIVATEDIR" target="_top">private dir</a>, <a class="link" href="smb.conf.5.html#PIDDIRECTORY" target="_top">pid directory</a>,<a class="link" href="smb.conf.5.html#LOCKDIRECTORY" target="_top">lock directory</a>, <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a>, <a class="link" href="smb.conf.5.html#BINDINTERFACESONLY" target="_top">bind interfaces only</a>, <a class="link" href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a>, <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a>, <a class="link" href="smb.conf.5.html#SOCKETADDRESS" target="_top">socket address</a>.

</p><p>

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

of multiple samba servers on a single host is considered not supported for Samba-3 by the Samba Team.

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2674305"></a>Multiple Virtual Server Personalities</h3></div></div></div><p>

Samba has the ability to host multiple virtual servers, each of which have their own personality. This is

achieved by configuring an <code class="filename">smb.conf</code> file that is common to all personalities hosted. Each server

personality is hosted using its own <a class="link" href="smb.conf.5.html#NETBIOSALIAS" target="_top">netbios alias</a> name, and each has its own distinct

<a class="link" href="smb.conf.5.html#%5BGLOBAL%5D" target="_top">[global]</a> section. Each server may have its own stanzas for services and meta-services.

</p><p>

When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup.

100

Only the primary server can be a domain member or a domain controller. The personality is defined by the

101

combination of the <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> mode it is operating in, the <a class="link" href="smb.conf.5.html#NETBIOSALIASES" target="_top">netbios aliases</a> it has, and the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> that is defined for it.

102

</p><p>

103

104

105

106

107

108

109

This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services.

110

If run using NetBIOS mode (the most common method) it is important that the parameter <a class="link" href="smb.conf.5.html#SMBPORTS" target="_top">smb ports = 139</a> should be specified in the primary <code class="filename">smb.conf</code> file. Failure to do this will result

111

in Samba operating over TCP port 445 and problematic operation at best, and at worst only being able to obtain

112

the functionality that is specified in the primary <code class="filename">smb.conf</code> file. The use of NetBIOS over TCP/IP using only

113

TCP port 139 means that the use of the <code class="literal">%L</code> macro is fully enabled. If the <a class="link" href="smb.conf.5.html#SMBPORTS" target="_top">smb ports = 139</a> is not specified (the default is <em class="parameter"><code>445 139</code></em>, or if

114

the value of this parameter is set at <em class="parameter"><code>139 445</code></em> then the <code class="literal">%L</code> macro

115

is not serviceable.

116

</p><p>

117

118

119

120

121

It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB

122

port), in which case the <code class="literal">%i</code> macro can be used to provide separate server identities (by

123

IP Address). Each can have its own <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> mode. It will be necessary to use the

124

<a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a>, <a class="link" href="smb.conf.5.html#BINDINTERFACESONLY" target="_top">bind interfaces only</a> and IP aliases in addition to

125

the <a class="link" href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a> parameters to create the virtual servers. This method is considerably

126

more complex than that using NetBIOS names only using TCP port 139.

127

</p><p>

128

129

Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only

130

Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it

131

is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here

132

are some parameters:

133

</p><p>

134

The Samba server is called <code class="literal">ELASTIC</code>, its workgroup name is <code class="literal">ROBINSNEST</code>.

135

The CDROM server is called <code class="literal">CDSERVER</code> and its workgroup is <code class="literal">ARTSDEPT</code>. A

136

possible implementation is shown here:

137

</p><p>

138

139

140

141

142

The <code class="filename">smb.conf</code> file for the master server is shown in <a class="link" href="cfgsmarts.html#elastic" title="Example�34.1.�Elastic smb.conf File">Elastic smb.conf File</a>.

143

This file is placed in the <code class="filename">/etc/samba</code> directory. Only the <span class="application">nmbd</span> and the <span class="application">smbd</span> daemons

144

are needed. When started the server will appear in Windows Network Neighborhood as the machine

145

<code class="literal">ELASTIC</code> under the workgroup <code class="literal">ROBINSNEST</code>. It is helpful if the Windows

146

clients that must access this server are also in the workgroup <code class="literal">ROBINSNEST</code> as this will make

147

browsing much more reliable.

148

</p><div class="example"><a name="elastic"></a><p class="title"><b>Example�34.1.�Elastic smb.conf File</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2674793"></a><em class="parameter"><code>workgroup = ROBINSNEST</code></em></td></tr><tr><td><a class="indexterm" name="id2674805"></a><em class="parameter"><code>netbios name = ELASTIC</code></em></td></tr><tr><td><a class="indexterm" name="id2674817"></a><em class="parameter"><code>netbios aliases = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2674829"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2674840"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674852"></a><em class="parameter"><code>disable spoolss = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2674864"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674876"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2674888"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2674908"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2674920"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2674932"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2674943"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2674964"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2674976"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2674987"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2675008"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2675019"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2675031"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id2675043"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675054"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675066"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675078"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><p>

149

150

The configuration file for the CDROM server is listed in <a class="link" href="cfgsmarts.html#cdserver" title="Example�34.2.�CDROM Server smb-cdserver.conf file">CDROM Server

151

smb-cdserver.conf file</a>. This file is called <code class="filename">smb-cdserver.conf</code> and it should be

152

located in the <code class="filename">/etc/samba</code> directory. Machines that are in the workgroup

153

<code class="literal">ARTSDEPT</code> will be able to browse this server freely.

154

</p><div class="example"><a name="cdserver"></a><p class="title"><b>Example�34.2.�CDROM Server smb-cdserver.conf file</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675158"></a><em class="parameter"><code>workgroup = ARTSDEPT</code></em></td></tr><tr><td><a class="indexterm" name="id2675170"></a><em class="parameter"><code>netbios name = CDSERVER</code></em></td></tr><tr><td><a class="indexterm" name="id2675182"></a><em class="parameter"><code>map to guest = Bad User</code></em></td></tr><tr><td><a class="indexterm" name="id2675194"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[carousel]</code></em></td></tr><tr><td><a class="indexterm" name="id2675214"></a><em class="parameter"><code>comment = CDROM Share</code></em></td></tr><tr><td><a class="indexterm" name="id2675226"></a><em class="parameter"><code>path = /export/cddata</code></em></td></tr><tr><td><a class="indexterm" name="id2675238"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675249"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>

155

156

157

158

159

The two servers have different resources and are in separate workgroups. The server <code class="literal">ELASTIC</code>

160

can only be accessed by uses who have an appropriate account on the host server. All users will be able to

161

access the CDROM data that is stored in the <code class="filename">/export/cddata</code> directory. File system

162

permissions should set so that the <code class="literal">others</code> user has read-only access to the directory and its

163

contents. The files can be owned by root (any user other than the nobody account).

164

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2675319"></a>Multiple Virtual Server Hosting</h3></div></div></div><p>

165

166

167

168

In this example, the requirement is for a primary domain controller for the domain called

169

<code class="literal">MIDEARTH</code>. The PDC will be called <code class="literal">MERLIN</code>. An extra machine called

170

<code class="literal">SAURON</code> is required. Each machine will have only its own shares. Both machines belong to the

171

same domain/workgroup.

172

</p><p>

173

174

175

176

The master <code class="filename">smb.conf</code> file is shown in <a class="link" href="cfgsmarts.html#mastersmbc" title="Example�34.3.�Master smb.conf File Global Section">the Master smb.conf File Global Section</a>.

177

The two files that specify the share information for each server are shown in <a class="link" href="cfgsmarts.html#merlinsmbc" title="Example�34.4.�MERLIN smb-merlin.conf File Share Section">the

178

smb-merlin.conf File Share Section</a>, and <a class="link" href="cfgsmarts.html#sauronsmbc" title="Example�34.5.�SAURON smb-sauron.conf File Share Section">the smb-sauron.conf File Share

179

Section</a>. All three files are locate in the <code class="filename">/etc/samba</code> directory.

180

</p><div class="example"><a name="mastersmbc"></a><p class="title"><b>Example�34.3.�Master smb.conf File Global Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675462"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675474"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td><a class="indexterm" name="id2675486"></a><em class="parameter"><code>netbios aliases = SAURON</code></em></td></tr><tr><td><a class="indexterm" name="id2675498"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id2675510"></a><em class="parameter"><code>smb ports = 139</code></em></td></tr><tr><td><a class="indexterm" name="id2675521"></a><em class="parameter"><code>syslog = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2675533"></a><em class="parameter"><code>printcap name = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675545"></a><em class="parameter"><code>show add printer wizard = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675557"></a><em class="parameter"><code>add user script = /usr/sbin/useradd -m '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675569"></a><em class="parameter"><code>delete user script = /usr/sbin/userdel -r '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675581"></a><em class="parameter"><code>add group script = /usr/sbin/groupadd '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675593"></a><em class="parameter"><code>delete group script = /usr/sbin/groupdel '%g'</code></em></td></tr><tr><td><a class="indexterm" name="id2675606"></a><em class="parameter"><code>add user to group script = /usr/sbin/usermod -G '%g' '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675618"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</code></em></td></tr><tr><td><a class="indexterm" name="id2675631"></a><em class="parameter"><code>logon script = scripts\login.bat</code></em></td></tr><tr><td><a class="indexterm" name="id2675643"></a><em class="parameter"><code>logon path = </code></em></td></tr><tr><td><a class="indexterm" name="id2675654"></a><em class="parameter"><code>logon drive = X:</code></em></td></tr><tr><td><a class="indexterm" name="id2675666"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675678"></a><em class="parameter"><code>preferred master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675690"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675701"></a><em class="parameter"><code>printing = CUPS</code></em></td></tr><tr><td><a class="indexterm" name="id2675713"></a><em class="parameter"><code>include = /etc/samba/smb-%L.conf</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="merlinsmbc"></a><p class="title"><b>Example�34.4.�MERLIN smb-merlin.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2675754"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2675765"></a><em class="parameter"><code>netbios name = MERLIN</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[homes]</code></em></td></tr><tr><td><a class="indexterm" name="id2675786"></a><em class="parameter"><code>comment = Home Directories</code></em></td></tr><tr><td><a class="indexterm" name="id2675798"></a><em class="parameter"><code>valid users = %S</code></em></td></tr><tr><td><a class="indexterm" name="id2675810"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td><a class="indexterm" name="id2675821"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[office]</code></em></td></tr><tr><td><a class="indexterm" name="id2675842"></a><em class="parameter"><code>comment = Data</code></em></td></tr><tr><td><a class="indexterm" name="id2675853"></a><em class="parameter"><code>path = /data</code></em></td></tr><tr><td><a class="indexterm" name="id2675865"></a><em class="parameter"><code>read only = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id2675885"></a><em class="parameter"><code>comment = NETLOGON</code></em></td></tr><tr><td><a class="indexterm" name="id2675897"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id2675909"></a><em class="parameter"><code>read only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675920"></a><em class="parameter"><code>browseable = No</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2675941"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2675953"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2675964"></a><em class="parameter"><code>printable = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675976"></a><em class="parameter"><code>use client driver = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id2675988"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"><div class="example"><a name="sauronsmbc"></a><p class="title"><b>Example�34.5.�SAURON smb-sauron.conf File Share Section</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2676028"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id2676040"></a><em class="parameter"><code>netbios name = SAURON</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[www]</code></em></td></tr><tr><td><a class="indexterm" name="id2676061"></a><em class="parameter"><code>comment = Web Pages</code></em></td></tr><tr><td><a class="indexterm" name="id2676072"></a><em class="parameter"><code>path = /srv/www/htdocs</code></em></td></tr><tr><td><a class="indexterm" name="id2676084"></a><em class="parameter"><code>read only = No</code></em></td></tr></table></div></div><br class="example-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="largefile.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�33.�Handling Large Directories�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�IV.�Migration and Updating</td></tr></table></div></body></html>