From 69a26b387b2b1906637d6ef1ab29ddd874a553dc Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Fri, 12 May 2000 13:05:25 +0000 Subject: - added example config section to winbindd man page - reran yodldocs with newer version of yodl (This used to be commit faa3f49430775fd1bd327237f369f7b5df6fc0c6) --- docs/htmldocs/swat.8.html | 108 +++++++++++++++++++++++----------------------- 1 file changed, 54 insertions(+), 54 deletions(-) (limited to 'docs/htmldocs/swat.8.html') 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 @@ + swat (8) - + @@ -15,53 +16,52 @@

Samba

23 Oct 1998

- -


+

NAME

swat - Samba Web Administration Tool -


+

SYNOPSIS

-


swat [-s smb config file] [-a] -


+

swat [-s smb config file] [-a] +

DESCRIPTION

-


This program is part of the Samba suite. -


swat allows a Samba administrator to configure the complex +

This program is part of the Samba suite. +

swat allows a Samba administrator to configure the complex smb.conf file via a Web browser. In addition, a swat configuration page has help links to all the configurable options in the smb.conf file allowing an administrator to easily look up the effects of any change. -


swat is run from inetd -


+

swat is run from inetd +

OPTIONS

-


-


+

Do NOT enable this option on a production server. +

+

INSTALLATION

-


After you compile SWAT you need to run "make install" to install the +

After you compile SWAT you need to run "make install" to install the swat binary and the various help files and images. A default install would put these in: -


+
 
 /usr/local/samba/bin/swat
 /usr/local/samba/swat/images/*
@@ -69,79 +69,79 @@ would put these in:
 
 

 
-


+

 
INETD INSTALLATION

     
-

You need to edit your /etc/inetd.conf and /etc/services to
+
You need to edit your /etc/inetd.conf and /etc/services to
 enable SWAT to be launched via inetd. 
-

In /etc/services you need to add a line like this:
-

swat            901/tcp
-

Note for NIS/YP users - you may need to rebuild the NIS service maps
+
In /etc/services you need to add a line like this:
+
swat            901/tcp
+
Note for NIS/YP users - you may need to rebuild the NIS service maps
 rather than alter your local /etc/services file.
-

the choice of port number isn't really important except that it should
+
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 inetd daemon).
-

In /etc/inetd.conf you should add a line like this:
-

swat    stream  tcp     nowait.400  root    /usr/local/samba/bin/swat swat
-

One you have edited /etc/services and /etc/inetd.conf you need
+
In /etc/inetd.conf you should add a line like this:
+
swat    stream  tcp     nowait.400  root    /usr/local/samba/bin/swat swat
+
One you have edited /etc/services and /etc/inetd.conf you need
 to send a HUP signal to inetd. To do this use "kill -1 PID" where
 PID is the process ID of the inetd daemon.
-


+

 
LAUNCHING

     
-

To launch swat just run your favorite web browser and point it at
+
To launch swat just run your favorite web browser and point it at
 http://localhost:901/.
-

Note that you can attach to swat from any IP connected machine but
+
Note that you can attach to swat 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.
-

FILES

+
FILES

     
-

/etc/inetd.conf
-

This file must contain suitable startup information for the
+
/etc/inetd.conf
+
This file must contain suitable startup information for the
 meta-daemon. 
-

/etc/services
-

This file must contain a mapping of service name (e.g., swat) to
+
/etc/services
+
This file must contain a mapping of service name (e.g., swat) to
 service port (e.g., 901) and protocol type (e.g., tcp). 
-

/usr/local/samba/lib/smb.conf
-

This is the default location of the smb.conf server configuration
+
/usr/local/samba/lib/smb.conf
+
This is the default location of the smb.conf server configuration
 file that swat edits. Other common places that systems install
 this file are /usr/samba/lib/smb.conf and /etc/smb.conf.
-

This file describes all the services the server is to make available
+
This file describes all the services the server is to make available
 to clients. See smb.conf (5) for more information.
-


+

 
WARNINGS

     
-

swat will rewrite your smb.conf file. It
+
swat will rewrite your smb.conf file. It
 will rearrange the entries and delete all comments,
 "include=" and
 "copy=" options. If you have a
 carefully crafted smb.conf then back it up
 or don't use swat!
-


+

 
VERSION

     
-

This man page is correct for version 2.0 of the Samba suite.
-


+
This man page is correct for version 2.0 of the Samba suite.
+

 
SEE ALSO

     
-

inetd (8), nmbd (8),
+
inetd (8), nmbd (8),
 smb.conf (5).
-


+

 
AUTHOR

     
-

The original Samba software and related utilities were created by
-Andrew Tridgell (samba-bugs@samba.org). Samba is now developed
+
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.
-

The original Samba man pages were written by Karl Auer. The man page
+
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
 ftp://ftp.icce.rug.nl/pub/unix/)
 and updated for the Samba2.0 release by Jeremy Allison.
-samba-bugs@samba.org.
-

See samba (7) to find out how to get a full
+samba@samba.org.
+
See samba (7) to find out how to get a full
 list of contributors and details on how to submit bug reports,
 comments etc.
 
-- 
cgit