1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.7"></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
<SPAN
61 > allows a Samba administrator to
62 configure the complex
<SPAN
68 > file via a Web browser. In addition,
72 > configuration page has help links
73 to all the configurable options in the
<TT
77 administrator to easily look up the effects of any change.
</P
100 >-s smb configuration file
</DT
103 >The default configuration file path is
104 determined at compile time. The file specified contains
105 the configuration details required by the
<SPAN
108 CLASS=
"REFENTRYTITLE"
111 > server. This is the file
116 The information in this file includes server-specific
117 information such as what printcap file to use, as well as
118 descriptions of all the services that the server is to provide.
122 > for more information.
129 >This option disables authentication and puts
133 > in demo mode. In that mode anyone will be able to modify
143 >WARNING: Do NOT enable this option on a production
152 >Prints the version number for
159 >-s
<configuration file
></DT
162 >The file specified contains the
163 configuration details required by the server. The
164 information in this file includes server-specific
165 information such as what printcap file to use, as well
166 as descriptions of all the services that the server is
168 HREF=
"smb.conf.5.html"
174 > for more information.
175 The default configuration file name is determined at
179 >-d|--debug=debuglevel
</DT
186 from
0 to
10. The default value if this parameter is
187 not specified is zero.
</P
189 >The higher this value, the more detail will be
190 logged to the log files about the activities of the
191 server. At level
0, only critical errors and serious
192 warnings will be logged. Level
1 is a reasonable level for
193 day to day running - it generates a small amount of
194 information about operations carried out.
</P
196 >Levels above
1 will generate considerable
197 amounts of log data, and should only be used when
198 investigating a problem. Levels above
3 are designed for
199 use only by developers and generate HUGE amounts of log
200 data, most of which is extremely cryptic.
</P
202 >Note that specifying this parameter here will
204 HREF=
"smb.conf.5.html#loglevel"
208 > parameter in the
<A
209 HREF=
"smb.conf.5.html"
218 >-l|--logfile=logbasename
</DT
221 >File name for log/debug files. The extension
225 > will be appended. The log file is
226 never removed by the client.
</P
232 >Print a summary of command line options.
</P
245 >Swat is included as binary package with most distributions. The
246 package manager in this case takes care of the installation and
247 configuration. This section is only for those who have compiled
251 >After you compile SWAT you need to run
<B
259 and the various help files and images. A default install would put
266 >/usr/local/samba/bin/swat
</P
270 >/usr/local/samba/swat/images/*
</P
274 >/usr/local/samba/swat/help/*
</P
283 >Inetd Installation
</H3
285 >You need to edit your
<TT
293 to enable SWAT to be launched via
<B
302 add a line like this:
</P
309 >Note for NIS/YP and LDAP users - you may need to rebuild the
310 NIS service maps rather than alter your local
<TT
315 >the choice of port number isn't really important
316 except that it should be less than
1024 and not currently
317 used (using a number above
1024 presents an obscure security
318 hole depending on the implementation details of your
328 add a line like this:
</P
332 >swat stream tcp nowait
.400 root
333 /usr/local/samba/bin/swat swat
</B
336 >One you have edited
<TT
344 HUP signal to inetd. To do this use
<B
348 > where PID is the process ID of the inetd daemon.
</P
359 >To launch SWAT just run your favorite web browser and
360 point it at
"http://localhost:901/".
</P
362 >Note that you can attach to SWAT from any IP connected
363 machine but connecting from a remote machine leaves your
364 connection open to password sniffing as passwords will be sent
365 in the clear over the wire.
</P
386 >This file must contain suitable startup
387 information for the meta-daemon.
</P
396 >This file must contain a mapping of service name
397 (e.g., swat) to service port (e.g.,
901) and protocol type
403 >/usr/local/samba/lib/smb.conf
</TT
407 >This is the default location of the
<SPAN
410 CLASS=
"REFENTRYTITLE"
413 > server configuration file that swat edits. Other
414 common places that systems install this file are
<TT
416 > /usr/samba/lib/smb.conf
</TT
421 >. This file describes all the services the server
422 is to make available to clients.
</P
438 > will rewrite your
<SPAN
441 CLASS=
"REFENTRYTITLE"
444 > file. It will rearrange the entries and delete all
452 > options. If you have a carefully crafted
<TT
455 > then back it up or don't use swat!
</P
465 >This man page is correct for version
3.0 of the Samba suite.
</P
481 CLASS=
"REFENTRYTITLE"
487 CLASS=
"REFENTRYTITLE"
500 >The original Samba software and related utilities
501 were created by Andrew Tridgell. Samba is now developed
502 by the Samba Team as an Open Source project similar
503 to the way the Linux kernel is developed.
</P
505 >The original Samba man pages were written by Karl Auer.
506 The man page sources were converted to YODL format (another
507 excellent piece of Open Source software, available at
<A
508 HREF=
"ftp://ftp.icce.rug.nl/pub/unix/"
510 > ftp://ftp.icce.rug.nl/pub/unix/
</A
511 >) and updated for the Samba
2.0
512 release by Jeremy Allison. The conversion to DocBook for
513 Samba
2.2 was done by Gerald Carter. The conversion to DocBook XML
4.2 for
514 Samba
3.0 was done by Alexander Bokovoy.
</P