docs/htmldocs/SWAT.html

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