1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.77"></HEAD
28 >swat
--
Samba Web Administration Tool
</DIV
30 CLASS=
"REFSYNOPSISDIV"
40 > [-s
<smb config file
>] [-a]
</P
50 >This tool is part of the
<A
59 > allows a Samba administrator to
60 configure the complex
<A
61 HREF=
"smb.conf.5.html"
67 > file via a Web browser. In addition,
71 > configuration page has help links
72 to all the configurable options in the
<TT
76 administrator to easily look up the effects of any change.
</P
99 >-s smb configuration file
</DT
102 >The default configuration file path is
103 determined at compile time. The file specified contains
104 the configuration details required by the
<B
108 > server. This is the file that
<B
112 The information in this file includes server-specific
113 information such as what printcap file to use, as well as
114 descriptions of all the services that the server is to provide.
118 > for more information.
125 >This option disables authentication and puts
129 > in demo mode. In that mode anyone will be able to modify
139 >WARNING: Do NOT enable this option on a production
155 >After you compile SWAT you need to run
<B
163 and the various help files and images. A default install would put
170 >/usr/local/samba/bin/swat
</P
174 >/usr/local/samba/swat/images/*
</P
178 >/usr/local/samba/swat/help/*
</P
187 >Inetd Installation
</H3
189 >You need to edit your
<TT
197 to enable SWAT to be launched via
<B
206 add a line like this:
</P
213 >Note for NIS/YP users - you may need to rebuild the
214 NIS service maps rather than alter your local
<TT
219 >the choice of port number isn't really important
220 except that it should be less than
1024 and not currently
221 used (using a number above
1024 presents an obscure security
222 hole depending on the implementation details of your
232 add a line like this:
</P
236 >swat stream tcp nowait
.400 root
237 /usr/local/samba/bin/swat swat
</B
240 >One you have edited
<TT
248 HUP signal to inetd. To do this use
<B
252 > where PID is the process ID of the inetd daemon.
</P
262 >To launch SWAT just run your favorite web browser and
263 point it at
"http://localhost:901/".
</P
265 >Note that you can attach to SWAT from any IP connected
266 machine but connecting from a remote machine leaves your
267 connection open to password sniffing as passwords will be sent
268 in the clear over the wire.
</P
290 >This file must contain suitable startup
291 information for the meta-daemon.
</P
300 >This file must contain a mapping of service name
301 (e.g., swat) to service port (e.g.,
901) and protocol type
307 >/usr/local/samba/lib/smb.conf
</TT
311 >This is the default location of the
<TT
315 > server configuration file that swat edits. Other
316 common places that systems install this file are
<TT
318 > /usr/samba/lib/smb.conf
</TT
323 >. This file describes all the services the server
324 is to make available to clients.
</P
340 > will rewrite your
<TT
344 > file. It will rearrange the entries and delete all
356 > options. If you have a carefully crafted
<TT
359 > then back it up or don't use swat!
</P
369 >This man page is correct for version
2.2 of
393 HREF=
"smb.conf.5.html"
407 >The original Samba software and related utilities
408 were created by Andrew Tridgell. Samba is now developed
409 by the Samba Team as an Open Source project similar
410 to the way the Linux kernel is developed.
</P
412 >The original Samba man pages were written by Karl Auer.
413 The man page sources were converted to YODL format (another
414 excellent piece of Open Source software, available at
416 HREF=
"ftp://ftp.icce.rug.nl/pub/unix/"
418 > ftp://ftp.icce.rug.nl/pub/unix/
</A
419 >) and updated for the Samba
2.0
420 release by Jeremy Allison. The conversion to DocBook for
421 Samba
2.2 was done by Gerald Carter
</P