diff options
author | Andrew Tridgell <tridge@samba.org> | 2000-05-12 13:05:25 +0000 |
---|---|---|
committer | Andrew Tridgell <tridge@samba.org> | 2000-05-12 13:05:25 +0000 |
commit | 69a26b387b2b1906637d6ef1ab29ddd874a553dc (patch) | |
tree | b9d3a3b4f3d1ffb9ba77dd1bb9a15e7d43004567 /docs/htmldocs/swat.8.html | |
parent | 30129251f26a4b2b59817eb984cc76251e89691d (diff) | |
download | samba-69a26b387b2b1906637d6ef1ab29ddd874a553dc.tar.gz samba-69a26b387b2b1906637d6ef1ab29ddd874a553dc.tar.bz2 samba-69a26b387b2b1906637d6ef1ab29ddd874a553dc.zip |
- added example config section to winbindd man page
- reran yodldocs with newer version of yodl
(This used to be commit faa3f49430775fd1bd327237f369f7b5df6fc0c6)
Diffstat (limited to 'docs/htmldocs/swat.8.html')
-rw-r--r-- | docs/htmldocs/swat.8.html | 108 |
1 files changed, 54 insertions, 54 deletions
diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 3a29f17ab5..12d83247fd 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -3,9 +3,10 @@ + <html><head><title>swat (8)</title> -<link rev="made" href="mailto:samba-bugs@samba.org"> +<link rev="made" href="mailto:samba@samba.org"> </head> <body> @@ -15,53 +16,52 @@ <h2>Samba</h2> <h2>23 Oct 1998</h2> - -<p><br><a name="NAME"></a> +<p><a name="NAME"></a> <h2>NAME</h2> swat - Samba Web Administration Tool -<p><br><a name="SYNOPSIS"></a> +<p><a name="SYNOPSIS"></a> <h2>SYNOPSIS</h2> -<p><br><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>] -<p><br><a name="DESCRIPTION"></a> +<p><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>] +<p><a name="DESCRIPTION"></a> <h2>DESCRIPTION</h2> -<p><br>This program is part of the <strong>Samba</strong> suite. -<p><br><strong>swat</strong> allows a Samba administrator to configure the complex +<p>This program is part of the <strong>Samba</strong> suite. +<p><strong>swat</strong> allows a Samba administrator to configure the complex <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file via a Web browser. In addition, a swat configuration page has help links to all the configurable options in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file allowing an administrator to easily look up the effects of any change. -<p><br><strong>swat</strong> is run from <strong>inetd</strong> -<p><br><a name="OPTIONS"></a> +<p><strong>swat</strong> is run from <strong>inetd</strong> +<p><a name="OPTIONS"></a> <h2>OPTIONS</h2> -<p><br><ul> -<p><br><a name="minuss"></a> -<li><strong><strong>-s smb configuration file</strong></strong> The default configuration file path is +<p><dl> +<p><a name="minuss"></a> +<p></p><dt><strong><strong>-s smb configuration file</strong></strong><dd> The default configuration file path is determined at compile time. -<p><br>The file specified contains the configuration details required by the +<p>The file specified contains the configuration details required by the <a href="smbd.8.html"><strong>smbd</strong></a> server. This is the file that <strong>swat</strong> will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See <a href="smb.conf.5.html">smb.conf (5)</a> for more information. -<p><br><a name="minusa"></a> -<li><strong><strong>-a</strong></strong> -<p><br>This option disables authentication and puts <strong>swat</strong> in demo mode. In +<p><a name="minusa"></a> +<p></p><dt><strong><strong>-a</strong></strong><dd> +<p>This option disables authentication and puts <strong>swat</strong> in demo mode. In that mode anyone will be able to modify the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. -<p><br>Do NOT enable this option on a production server. -<p><br></ul> -<p><br><a name="INSTALLATION"></a> +<p>Do NOT enable this option on a production server. +<p></dl> +<p><a name="INSTALLATION"></a> <h2>INSTALLATION</h2> -<p><br>After you compile SWAT you need to run <code>"make install"</code> to install the +<p>After you compile SWAT you need to run <code>"make install"</code> to install the swat binary and the various help files and images. A default install would put these in: -<p><br><pre> +<p><pre> /usr/local/samba/bin/swat /usr/local/samba/swat/images/* @@ -69,79 +69,79 @@ would put these in: </pre> -<p><br><a name="INETD"></a> +<p><a name="INETD"></a> <h2>INETD INSTALLATION</h2> -<p><br>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to +<p>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to enable <strong>SWAT</strong> to be launched via inetd. -<p><br>In <code>/etc/services</code> you need to add a line like this: -<p><br><code>swat 901/tcp</code> -<p><br>Note for NIS/YP users - you may need to rebuild the NIS service maps +<p>In <code>/etc/services</code> you need to add a line like this: +<p><code>swat 901/tcp</code> +<p>Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local <code>/etc/services</code> file. -<p><br>the choice of port number isn't really important except that it should +<p>the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your <strong>inetd</strong> daemon). -<p><br>In <code>/etc/inetd.conf</code> you should add a line like this: -<p><br><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code> -<p><br>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need +<p>In <code>/etc/inetd.conf</code> you should add a line like this: +<p><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code> +<p>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need to send a HUP signal to inetd. To do this use <code>"kill -1 PID"</code> where PID is the process ID of the inetd daemon. -<p><br><a name="LAUNCHING"></a> +<p><a name="LAUNCHING"></a> <h2>LAUNCHING</h2> -<p><br>To launch <strong>swat</strong> just run your favorite web browser and point it at +<p>To launch <strong>swat</strong> just run your favorite web browser and point it at <code>http://localhost:901/</code>. -<p><br><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but +<p><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire.</strong> -<p><br><h2>FILES</h2> +<p><h2>FILES</h2> -<p><br><strong>/etc/inetd.conf</strong> -<p><br>This file must contain suitable startup information for the +<p><strong>/etc/inetd.conf</strong> +<p>This file must contain suitable startup information for the meta-daemon. -<p><br><strong>/etc/services</strong> -<p><br>This file must contain a mapping of service name (e.g., swat) to +<p><strong>/etc/services</strong> +<p>This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp). -<p><br><strong>/usr/local/samba/lib/smb.conf</strong> -<p><br>This is the default location of the <em>smb.conf</em> server configuration +<p><strong>/usr/local/samba/lib/smb.conf</strong> +<p>This is the default location of the <em>smb.conf</em> server configuration file that <strong>swat</strong> edits. Other common places that systems install this file are <em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>. -<p><br>This file describes all the services the server is to make available +<p>This file describes all the services the server is to make available to clients. See <strong>smb.conf (5)</strong> for more information. -<p><br><a name="WARNINGS"></a> +<p><a name="WARNINGS"></a> <h2>WARNINGS</h2> -<p><br><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It +<p><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It will rearrange the entries and delete all comments, <a href="smb.conf.5.html#include"><strong>"include="</strong></a> and <a href="smb.conf.5.html#copy"><strong>"copy="</strong></a> options. If you have a carefully crafted <a href="smb.conf.5.html"><strong>smb.conf</strong></a> then back it up or don't use <strong>swat</strong>! -<p><br><a name="VERSION"></a> +<p><a name="VERSION"></a> <h2>VERSION</h2> -<p><br>This man page is correct for version 2.0 of the Samba suite. -<p><br><a name="SEEALSO"></a> +<p>This man page is correct for version 2.0 of the Samba suite. +<p><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, +<p><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. -<p><br><a name="AUTHOR"></a> +<p><a name="AUTHOR"></a> <h2>AUTHOR</h2> -<p><br>The original Samba software and related utilities were created by -Andrew Tridgell (samba-bugs@samba.org). Samba is now developed +<p>The original Samba software and related utilities were created by +Andrew Tridgell (samba@samba.org). Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. -<p><br>The original Samba man pages were written by Karl Auer. The man page +<p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) and updated for the Samba2.0 release by Jeremy Allison. -<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. -<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. +<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors and details on how to submit bug reports, comments etc. </body> |