7 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.57"></HEAD
27 >swat
--
Samba Web Administration Tool
</DIV
29 CLASS=
"REFSYNOPSISDIV"
39 > [-s
<smb config file
>] [-a]
</P
49 >This tool is part of the
<A
58 > allows a Samba administrator to
59 configure the complex
<A
60 HREF=
"smb.conf.5.html"
66 > file via a Web browser. In addition,
70 > configuration page has help links
71 to all the configurable options in the smb.conf file allowing an
72 administrator to easily look up the effects of any change.
</P
74 >swat is run from inetd
</P
89 >-s smb configuration file
</DT
92 >The default configuration file path is
93 determined at compile time. The file specified contains
94 the configuration details required by the
<B
98 > server. This is the file that swat will modify.
99 The information in this file includes server-specific
100 information such as what printcap file to use, as well as
101 descriptions of all the services that the server is to provide.
105 > for more information.
112 >This option disables authentication and puts
113 swat in demo mode. In that mode anyone will be able to modify
114 the smb.conf file.
</P
117 >Do NOT enable this option on a production
132 >After you compile SWAT you need to run
<B
140 and the various help files and images. A default install would put
147 >/usr/local/samba/bin/swat
</P
151 >/usr/local/samba/swat/images/*
</P
155 >/usr/local/samba/swat/help/*
</P
164 >Inetd Installation
</H3
166 >You need to edit your
<TT
174 to enable SWAT to be launched via inetd.
</P
180 add a line like this:
</P
187 >Note for NIS/YP users - you may need to rebuild the
188 NIS service maps rather than alter your local
<TT
193 >the choice of port number isn't really important
194 except that it should be less than
1024 and not currently
195 used (using a number above
1024 presents an obscure security
196 hole depending on the implementation details of your
206 add a line like this:
</P
210 >swat stream tcp nowait
.400 root
211 /usr/local/samba/bin/swat swat
</B
214 >One you have edited
<TT
222 HUP signal to inetd. To do this use
<B
226 > where PID is the process ID of the inetd daemon.
</P
236 >To launch swat just run your favorite web browser and
237 point it at
"http://localhost:901/".
</P
239 >Note that you can attach to swat from any IP connected
240 machine but connecting from a remote machine leaves your
241 connection open to password sniffing as passwords will be sent
242 in the clear over the wire.
</P
264 >This file must contain suitable startup
265 information for the meta-daemon.
</P
274 >This file must contain a mapping of service name
275 (e.g., swat) to service port (e.g.,
901) and protocol type
281 >/usr/local/samba/lib/smb.conf
</TT
285 >This is the default location of the
<TT
289 > server configuration file that swat edits. Other
290 common places that systems install this file are
<TT
292 > /usr/samba/lib/smb.conf
</TT
297 >. This file describes all the services the server
298 is to make available to clients.
</P
314 > will rewrite your
<TT
318 > file. It will rearrange the entries and delete all
330 > options. If you have a carefully crafted <TT
333 > then back it up or don't use swat! </P
343 >This man page is correct for version 2.2 of
367 HREF="smb.conf
.5.html
"
381 >The original Samba software and related utilities
382 were created by Andrew Tridgell. Samba is now developed
383 by the Samba Team as an Open Source project similar
384 to the way the Linux kernel is developed.</P
386 >The original Samba man pages were written by Karl Auer.
387 The man page sources were converted to YODL format (another
388 excellent piece of Open Source software, available at
390 HREF="ftp://ftp.icce.rug.nl/pub/unix/
"
392 > ftp://ftp.icce.rug.nl/pub/unix/</A
393 >) and updated for the Samba 2.0
394 release by Jeremy Allison. The conversion to DocBook for
395 Samba 2.2 was done by Gerald Carter</P