source: vendor/3.5.9/docs/htmldocs/Samba3-HOWTO/SWAT.html

Last change on this file was 597, checked in by Herwig Bauernfeind, 14 years ago

Samba 3.5: Update vendor to version 3.5.9
File size: 29.1 KB
Line 
1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 37. SWAT: The Samba Web Administration Tool</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part IV. Migration and Updating"><link rel="prev" href="NT4Migration.html" title="Chapter 36. Migration from NT4 PDC to Samba-3 PDC"><link rel="next" href="troubleshooting.html" title="Part V. Troubleshooting"></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 37. SWAT: The Samba Web Administration Tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a> </td><th width="60%" align="center">Part IV. Migration and Updating</th><td width="20%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 37. SWAT: The Samba Web Administration Tool"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter 37. SWAT: The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SWAT.html#id443276">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id443388">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id443406">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id443979">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444125">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id444311">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id444322">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444375">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444471">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444523">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444575">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444631">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444670">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id444687">The Password Change Page</a></span></dt></dl></dd></dl></div><p>
2<a class="indexterm" name="id443244"></a>
3<a class="indexterm" name="id443251"></a>
4<a class="indexterm" name="id443258"></a>
5There are many and varied opinions regarding the usefulness of SWAT. No matter how hard one tries to produce
6the perfect configuration tool, it remains an object of personal taste. SWAT is a tool that allows Web-based
7configuration of Samba. It has a wizard that may help to get Samba configured quickly, it has
8context-sensitive help on each <code class="filename">smb.conf</code> parameter, it provides for monitoring of current state of connection
9information, and it allows networkwide MS Windows network password management.
10</p><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id443276"></a>Features and Benefits</h2></div></div></div><p>
11<a class="indexterm" name="id443283"></a>
12SWAT is a facility that is part of the Samba suite. The main executable is called
13<code class="literal">swat</code> and is invoked by the internetworking super daemon.
14See <a class="link" href="SWAT.html#xinetd" title="Enabling SWAT for Use">appropriate section</a> for details.
15</p><p>
16<a class="indexterm" name="id443309"></a>
17SWAT uses integral Samba components to locate parameters supported by the particular
18version of Samba. Unlike tools and utilities that are external to Samba, SWAT is always
19up to date as known Samba parameters change. SWAT provides context-sensitive help for each
20configuration parameter, directly from <code class="literal">man</code> page entries.
21</p><p>
22<a class="indexterm" name="id443328"></a>
23<a class="indexterm" name="id443334"></a>
24<a class="indexterm" name="id443341"></a>
25Some network administrators believe that it is a good idea to write systems
26documentation inside configuration files, and for them SWAT will always be a nasty tool. SWAT
27does not store the configuration file in any intermediate form; rather, it stores only the
28parameter settings, so when SWAT writes the <code class="filename">smb.conf</code> file to disk, it writes only
29those parameters that are at other than the default settings. The result is that all comments,
30as well as parameters that are no longer supported, will be lost from the <code class="filename">smb.conf</code> file.
31Additionally, the parameters will be written back in internal ordering.
32</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
33<a class="indexterm" name="id443369"></a>
34Before using SWAT, please be warned SWAT will completely replace your <code class="filename">smb.conf</code> with
35a fully optimized file that has been stripped of all comments you might have placed there
36and only nondefault settings will be written to the file.
37</p></div></div><div class="sect1" title="Guidelines and Technical Tips"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id443388"></a>Guidelines and Technical Tips</h2></div></div></div><p>
38<a class="indexterm" name="id443396"></a>
39This section aims to unlock the dark secrets behind how SWAT may be made to work,
40how it can be made more secure, and how to solve internationalization support problems.
41</p><div class="sect2" title="Validate SWAT Installation"><div class="titlepage"><div><div><h3 class="title"><a name="id443406"></a>Validate SWAT Installation</h3></div></div></div><p>
42<a class="indexterm" name="id443414"></a>
43The very first step that should be taken before attempting to configure a host
44system for SWAT operation is to check that it is installed. This may seem a trivial
45point to some, but several Linux distributions do not install SWAT by default,
46even though they do ship an installable binary support package containing SWAT
47on the distribution media.
48</p><p>
49<a class="indexterm" name="id443427"></a>
50When you have confirmed that SWAT is installed, it is necessary to validate
51that the installation includes the binary <code class="literal">swat</code> file as well
52as all the supporting text and Web files. A number of operating system distributions
53in the past have failed to include the necessary support files, even though the
54<code class="literal">swat</code> binary executable file was installed.
55</p><p>
56<a class="indexterm" name="id443451"></a>
57<a class="indexterm" name="id443458"></a>
58Finally, when you are sure that SWAT has been fully installed, please check that SWAT
59is enabled in the control file for the internetworking super-daemon (inetd or xinetd)
60that is used on your operating system platform.
61</p><div class="sect3" title="Locating the SWAT File"><div class="titlepage"><div><div><h4 class="title"><a name="id443468"></a>Locating the <code class="literal">SWAT</code> File</h4></div></div></div><p>
62<a class="indexterm" name="id443482"></a>
63<a class="indexterm" name="id443488"></a>
64<a class="indexterm" name="id443495"></a>
65To validate that SWAT is installed, first locate the <code class="literal">swat</code> binary
66file on the system. It may be found under the following directories:</p><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">/usr/local/samba/bin</code> the default Samba location</td></tr><tr><td><code class="filename">/usr/sbin</code> the default location on most Linux systems</td></tr><tr><td><code class="filename">/opt/samba/bin</code></td></tr></table><p>
67</p><p>
68The actual location is much dependent on the choice of the operating system vendor or as determined
69by the administrator who compiled and installed Samba.
70</p><p>
71There are a number of methods that may be used to locate the <code class="literal">swat</code> binary file.
72The following methods may be helpful.
73</p><p>
74<a class="indexterm" name="id443563"></a>
75<a class="indexterm" name="id443570"></a>
76<a class="indexterm" name="id443577"></a>
77If <code class="literal">swat</code> is in your current operating system search path, it will be easy to
78find it. You can ask what are the command-line options for <code class="literal">swat</code> as shown here:
79</p><pre class="screen">
80frodo:~ # swat -?
81Usage: swat [OPTION...]
82 -a, --disable-authentication Disable authentication (demo mode)
83
84Help options:
85 -?, --help Show this help message
86 --usage Display brief usage message
87
88Common samba options:
89 -d, --debuglevel=DEBUGLEVEL Set debug level
90 -s, --configfile=CONFIGFILE Use alternative configuration file
91 -l, --log-basename=LOGFILEBASE Basename for log/debug files
92 -V, --version Print version
93</pre><p>
94</p></div><div class="sect3" title="Locating the SWAT Support Files"><div class="titlepage"><div><div><h4 class="title"><a name="id443609"></a>Locating the SWAT Support Files</h4></div></div></div><p>
95Now that you have found that <code class="literal">swat</code> is in the search path, it is easy
96to identify where the file is located. Here is another simple way this may be done:
97</p><pre class="screen">
98frodo:~ # whereis swat
99swat: /usr/sbin/swat /usr/share/man/man8/swat.8.gz
100</pre><p>
101</p><p>
102If the above measures fail to locate the <code class="literal">swat</code> binary, another approach
103is needed. The following may be used:
104</p><pre class="screen">
105frodo:/ # find / -name swat -print
106/etc/xinetd.d/swat
107/usr/sbin/swat
108/usr/share/samba/swat
109frodo:/ #
110</pre><p>
111</p><p>
112This list shows that there is a control file for <code class="literal">xinetd</code>, the internetwork
113super-daemon that is installed on this server. The location of the SWAT binary file is
114<code class="filename">/usr/sbin/swat</code>, and the support files for it are located under the
115directory <code class="filename">/usr/share/samba/swat</code>.
116</p><p>
117We must now check where <code class="literal">swat</code> expects to find its support files. This can
118be done as follows:
119</p><pre class="screen">
120frodo:/ # strings /usr/sbin/swat | grep "/swat"
121/swat/
122...
123/usr/share/samba/swat
124frodo:/ #
125</pre><p>
126</p><p>
127The <code class="filename">/usr/share/samba/swat/</code> entry shown in this listing is the location of the
128support files. You should verify that the support files exist under this directory. A sample
129list is as shown:
130</p><pre class="screen">
131jht@frodo:/&gt; find /usr/share/samba/swat -print
132/usr/share/samba/swat
133/usr/share/samba/swat/help
134/usr/share/samba/swat/lang
135/usr/share/samba/swat/lang/ja
136/usr/share/samba/swat/lang/ja/help
137/usr/share/samba/swat/lang/ja/help/welcome.html
138/usr/share/samba/swat/lang/ja/images
139/usr/share/samba/swat/lang/ja/images/home.gif
140...
141/usr/share/samba/swat/lang/ja/include
142/usr/share/samba/swat/lang/ja/include/header.nocss.html
143...
144/usr/share/samba/swat/lang/tr
145/usr/share/samba/swat/lang/tr/help
146/usr/share/samba/swat/lang/tr/help/welcome.html
147/usr/share/samba/swat/lang/tr/images
148/usr/share/samba/swat/lang/tr/images/home.gif
149...
150/usr/share/samba/swat/lang/tr/include
151/usr/share/samba/swat/lang/tr/include/header.html
152/usr/share/samba/swat/using_samba
153...
154/usr/share/samba/swat/images
155/usr/share/samba/swat/images/home.gif
156...
157/usr/share/samba/swat/include
158/usr/share/samba/swat/include/footer.html
159/usr/share/samba/swat/include/header.html
160jht@frodo:/&gt;
161</pre><p>
162</p><p>
163If the files needed are not available, it is necessary to obtain and install them
164before SWAT can be used.
165</p></div></div><div class="sect2" title="Enabling SWAT for Use"><div class="titlepage"><div><div><h3 class="title"><a name="xinetd"></a>Enabling SWAT for Use</h3></div></div></div><p>
166SWAT should be installed to run via the network super-daemon. Depending on which system
167your UNIX/Linux system has, you will have either an <code class="literal">inetd</code>- or
168<code class="literal">xinetd</code>-based system.
169</p><p>
170The nature and location of the network super-daemon varies with the operating system
171implementation. The control file (or files) can be located in the file
172<code class="filename">/etc/inetd.conf</code> or in the directory <code class="filename">/etc/[x]inet[d].d</code>
173or in a similar location.
174</p><p>
175The control entry for the older style file might be:
176<a class="indexterm" name="id443771"></a>
177</p><pre class="programlisting">
178 # swat is the Samba Web Administration Tool
179 swat stream tcp nowait.400 root /usr/sbin/swat swat
180</pre><p>
181A control file for the newer style xinetd could be:
182</p><p>
183</p><pre class="programlisting">
184# default: off
185# description: SWAT is the Samba Web Admin Tool. Use swat \
186# to configure your Samba server. To use SWAT, \
187# connect to port 901 with your favorite web browser.
188service swat
189{
190 port = 901
191 socket_type = stream
192 wait = no
193 only_from = localhost
194 user = root
195 server = /usr/sbin/swat
196 log_on_failure += USERID
197 disable = no
198}
199</pre><p>
200In the above, the default setting for <em class="parameter"><code>disable</code></em> is <code class="constant">yes</code>.
201This means that SWAT is disabled. To enable use of SWAT, set this parameter to <code class="constant">no</code>
202as shown.
203</p><p>
204<a class="indexterm" name="id443820"></a>
205<a class="indexterm" name="id443827"></a>
206<a class="indexterm" name="id443834"></a>
207<a class="indexterm" name="id443841"></a>
208Both of the previous examples assume that the <code class="literal">swat</code> binary has been
209located in the <code class="filename">/usr/sbin</code> directory. In addition to the above,
210SWAT will use a directory access point from which it will load its Help files
211as well as other control information. The default location for this on most Linux
212systems is in the directory <code class="filename">/usr/share/samba/swat</code>. The default
213location using Samba defaults will be <code class="filename">/usr/local/samba/swat</code>.
214</p><p>
215<a class="indexterm" name="id443877"></a>
216<a class="indexterm" name="id443884"></a>
217Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user,
218the only permission allowed is to view certain aspects of configuration as well as
219access to the password change facility. The buttons that will be exposed to the non-root
220user are <span class="guibutton">HOME</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, and
221<span class="guibutton">PASSWORD</span>. The only page that allows
222change capability in this case is <span class="guibutton">PASSWORD</span>.
223</p><p>
224As long as you log onto SWAT as the user <span class="emphasis"><em>root</em></span>, you should obtain
225full change and commit ability. The buttons that will be exposed include
226<span class="guibutton">HOME</span>, <span class="guibutton">GLOBALS</span>, <span class="guibutton">SHARES</span>, <span class="guibutton">PRINTERS</span>,
227<span class="guibutton">WIZARD</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, and <span class="guibutton">PASSWORD</span>.
228</p></div><div class="sect2" title="Securing SWAT through SSL"><div class="titlepage"><div><div><h3 class="title"><a name="id443979"></a>Securing SWAT through SSL</h3></div></div></div><p>
229<a class="indexterm" name="id443987"></a>
230<a class="indexterm" name="id443994"></a>
231Many people have asked about how to set up SWAT with SSL to allow for secure remote
232administration of Samba. Here is a method that works, courtesy of Markus Krieger.
233</p><p>
234Modifications to the SWAT setup are as follows:
235</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
236<a class="indexterm" name="id444017"></a>
237 Install OpenSSL.
238 </p></li><li class="step" title="Step 2"><p>
239<a class="indexterm" name="id444031"></a>
240<a class="indexterm" name="id444038"></a>
241 Generate certificate and private key.
242<a class="indexterm" name="id444045"></a>
243</p><pre class="screen">
244<code class="prompt">root# </code><strong class="userinput"><code>/usr/bin/openssl req -new -x509 -days 365 -nodes -config \
245 /usr/share/doc/packages/stunnel/stunnel.cnf \
246 -out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem</code></strong>
247</pre></li><li class="step" title="Step 3"><p>
248 Remove SWAT entry from [x]inetd.
249 </p></li><li class="step" title="Step 4"><p>
250<a class="indexterm" name="id444081"></a>
251 Start <code class="literal">stunnel</code>.
252
253</p><pre class="screen">
254<code class="prompt">root# </code><strong class="userinput"><code>stunnel -p /etc/stunnel/stunnel.pem -d 901 \
255 -l /usr/local/samba/bin/swat swat </code></strong>
256</pre></li></ol></div><p>
257Afterward, simply connect to SWAT by using the URL <a class="ulink" href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate, and the SSL connection is up.
258</p></div><div class="sect2" title="Enabling SWAT Internationalization Support"><div class="titlepage"><div><div><h3 class="title"><a name="id444125"></a>Enabling SWAT Internationalization Support</h3></div></div></div><p>
259SWAT can be configured to display its messages to match the settings of
260the language configurations of your Web browser. It will be passed to SWAT
261in the Accept-Language header of the HTTP request.
262</p><p>
263To enable this feature:
264</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
265 Install the proper <code class="literal">msg</code> files from the Samba
266 <code class="filename">source/po</code> directory into $LIBDIR.
267 </p></li><li class="listitem"><p>
268 Set your browsers language setting.
269 </p></li></ul></div><p>
270<a class="indexterm" name="id444166"></a>
271<a class="indexterm" name="id444172"></a>
272<a class="indexterm" name="id444179"></a>
273<a class="indexterm" name="id444186"></a>
274The name of the <code class="literal">msg</code> file is the same as the language ID sent by the browser. For
275example, <span class="emphasis"><em>en</em></span> means English, <span class="emphasis"><em>ja</em></span> means Japanese, <span class="emphasis"><em>fr</em></span> means French.
276</p><p>
277<a class="indexterm" name="id444214"></a>
278If you do not like some of messages, or there are no <code class="literal">msg</code> files for
279your locale, you can create them simply by copying the <code class="literal">en.msg</code> files
280to the directory for <span class="quote">&#8220;<span class="quote">your language ID.msg</span>&#8221;</span> and filling in proper strings
281to each <span class="quote">&#8220;<span class="quote">msgstr</span>&#8221;</span>. For example, in <code class="filename">it.msg</code>, the
282<code class="literal">msg</code> file for the Italian locale, just set:
283</p><pre class="screen">
284msgid "Set Default"
285msgstr "Imposta Default"
286</pre><p>
287<a class="indexterm" name="id444259"></a>
288and so on. If you find a mistake or create a new <code class="literal">msg</code> file, please email it
289to us so we will consider it in the next release of Samba. The <code class="literal">msg</code> file should be encoded in UTF-8.
290</p><p>
291<a class="indexterm" name="id444281"></a>
292Note that if you enable this feature and the <a class="link" href="smb.conf.5.html#DISPLAYCHARSET" target="_top">display charset</a> is not
293matched to your browser's setting, the SWAT display may be corrupted. In a future version of
294Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set
295this <code class="filename">smb.conf</code> file parameter.
296</p></div></div><div class="sect1" title="Overview and Quick Tour"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id444311"></a>Overview and Quick Tour</h2></div></div></div><p>
297SWAT is a tool that may be used to configure Samba or just to obtain useful links
298to important reference materials such as the contents of this book as well as other
299documents that have been found useful for solving Windows networking problems.
300</p><div class="sect2" title="The SWAT Home Page"><div class="titlepage"><div><div><h3 class="title"><a name="id444322"></a>The SWAT Home Page</h3></div></div></div><p>
301The SWAT title page provides access to the latest Samba documentation. The manual page for
302each Samba component is accessible from this page, as are the Samba3-HOWTO (this
303document) as well as the O'Reilly book <span class="quote">&#8220;<span class="quote">Using Samba.</span>&#8221;</span>
304</p><p>
305Administrators who wish to validate their Samba configuration may obtain useful information
306from the man pages for the diagnostic utilities. These are available from the SWAT home page
307also. One diagnostic tool that is not mentioned on this page but that is particularly
308useful is <a class="ulink" href="http://www.ethereal.com/" target="_top"><code class="literal">ethereal</code></a>.
309</p><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
310SWAT can be configured to run in <span class="emphasis"><em>demo</em></span> mode. This is not recommended
311because it runs SWAT without authentication and with full administrative ability. It allows
312changes to <code class="filename">smb.conf</code> as well as general operation with root privileges. The option that
313creates this ability is the <code class="option">-a</code> flag to SWAT. <span class="emphasis"><em>Do not use this in a
314production environment.</em></span>
315</p></div></div><div class="sect2" title="Global Settings"><div class="titlepage"><div><div><h3 class="title"><a name="id444375"></a>Global Settings</h3></div></div></div><p>
316The <span class="guibutton">GLOBALS</span> button exposes a page that allows configuration of the global parameters
317in <code class="filename">smb.conf</code>. There are two levels of exposure of the parameters:
318</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
319 <span class="guibutton">Basic</span> exposes common configuration options.
320 </p></li><li class="listitem"><p>
321 <span class="guibutton">Advanced</span> exposes configuration options needed in more
322 complex environments.
323 </p></li></ul></div><p>
324To switch to other than <span class="guibutton">Basic</span> editing ability, click on <span class="guibutton">Advanced</span>.
325You may also do this by clicking on the radio button, then click on the <span class="guibutton">Commit Changes</span> button.
326</p><p>
327After making any changes to configuration parameters, make sure that
328you click on the
329<span class="guibutton">Commit Changes</span> button before moving to another area; otherwise,
330your changes will be lost.
331</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
332SWAT has context-sensitive help. To find out what each parameter is
333for, simply click on the
334<span class="guibutton">Help</span> link to the left of the configuration parameter.
335</p></div></div><div class="sect2" title="Share Settings"><div class="titlepage"><div><div><h3 class="title"><a name="id444471"></a>Share Settings</h3></div></div></div><p>
336To affect a currently configured share, simply click on the pull-down button between the
337<span class="guibutton">Choose Share</span> and the <span class="guibutton">Delete Share</span> buttons and
338select the share you wish to operate on. To edit the settings,
339click on the
340<span class="guibutton">Choose Share</span> button. To delete the share, simply press the
341<span class="guibutton">Delete Share</span> button.
342</p><p>
343To create a new share, next to the button labeled <span class="guibutton">Create Share</span>, enter
344into the text field the name of the share to be created, then click on the
345<span class="guibutton">Create Share</span> button.
346</p></div><div class="sect2" title="Printers Settings"><div class="titlepage"><div><div><h3 class="title"><a name="id444523"></a>Printers Settings</h3></div></div></div><p>
347To affect a currently configured printer, simply click on the pull-down button between the
348<span class="guibutton">Choose Printer</span> and the <span class="guibutton">Delete Printer</span> buttons and
349select the printer you wish to operate on. To edit the settings,
350click on the
351<span class="guibutton">Choose Printer</span> button. To delete the share, simply press the
352<span class="guibutton">Delete Printer</span> button.
353</p><p>
354To create a new printer, next to the button labeled <span class="guibutton">Create Printer</span>, enter
355into the text field the name of the share to be created, then click on the
356<span class="guibutton">Create Printer</span> button.
357</p></div><div class="sect2" title="The SWAT Wizard"><div class="titlepage"><div><div><h3 class="title"><a name="id444575"></a>The SWAT Wizard</h3></div></div></div><p>
358The purpose of the SWAT Wizard is to help the Microsoft-knowledgeable network administrator
359to configure Samba with a minimum of effort.
360</p><p>
361The Wizard page provides a tool for rewriting the <code class="filename">smb.conf</code> file in fully optimized format.
362This will also happen if you press the <span class="guibutton">Commit</span> button. The two differ
363because the <span class="guibutton">Rewrite</span> button ignores any changes that may have been made,
364while the <span class="guibutton">Commit</span> button causes all changes to be affected.
365</p><p>
366The <span class="guibutton">Edit</span> button permits the editing (setting) of the minimal set of
367options that may be necessary to create a working Samba server.
368</p><p>
369Finally, there are a limited set of options that determine what type of server Samba
370will be configured for, whether it will be a WINS server, participate as a WINS client, or
371operate with no WINS support. By clicking one button, you can elect to expose (or not) user
372home directories.
373</p></div><div class="sect2" title="The Status Page"><div class="titlepage"><div><div><h3 class="title"><a name="id444631"></a>The Status Page</h3></div></div></div><p>
374The status page serves a limited purpose. First, it allows control of the Samba daemons.
375The key daemons that create the Samba server environment are <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span>.
376</p><p>
377The daemons may be controlled individually or as a total group. Additionally, you may set
378an automatic screen refresh timing. As MS Windows clients interact with Samba, new smbd processes
379are continually spawned. The auto-refresh facility allows you to track the changing
380conditions with minimal effort.
381</p><p>
382Finally, the status page may be used to terminate specific smbd client connections in order to
383free files that may be locked.
384</p></div><div class="sect2" title="The View Page"><div class="titlepage"><div><div><h3 class="title"><a name="id444670"></a>The View Page</h3></div></div></div><p>
385The view page allows you to view the optimized <code class="filename">smb.conf</code> file and, if you are
386particularly masochistic, permits you also to see all possible global configuration
387parameters and their settings.
388</p></div><div class="sect2" title="The Password Change Page"><div class="titlepage"><div><div><h3 class="title"><a name="id444687"></a>The Password Change Page</h3></div></div></div><p>
389The password change page is a popular tool that allows the creation, deletion, deactivation,
390and reactivation of MS Windows networking users on the local machine. You can also use
391this tool to change a local password for a user account.
392</p><p>
393When logged in as a non-root account, the user must provide the old password as well as
394the new password (twice). When logged in as <span class="emphasis"><em>root</em></span>, only the new password is
395required.
396</p><p>
397One popular use for this tool is to change user passwords across a range of remote MS Windows
398servers.
399</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 36. Migration from NT4 PDC to Samba-3 PDC </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part V. Troubleshooting</td></tr></table></div></body></html>
Note: See TracBrowser for help on using the repository browser.