summaryrefslogtreecommitdiff
path: root/docs/docbook/projdoc/SWAT.sgml
blob: ad43fd7b8a41cbfa4e8b4bd4f39e3c76f87c9c22 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
<chapter id="SWAT">
<chapterinfo>
	&author.jht;
	<pubdate>April 21, 2003</pubdate>
</chapterinfo>

<title>SWAT - The Samba Web Admininistration Tool</title>

<para>
There are many and varied opinions regarding the usefulness or otherwise of SWAT.
No matter how hard one tries to produce the perfect configuration tool it remains
an object of personal taste. SWAT is a tool that will allow web based configuration
of samba. It has a wizard that may help to get samba configured quickly, it has context
sensitive help on each smb.conf parameter, it provides for monitoring of current state
of connection information, and it allows network wide MS Windows network password
management.
</para>

<sect1>
<title>SWAT Features and Benefits</title>

<para>
There are network administrators who believe that it is a good idea to write systems
documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT
does not store the configuration file in any intermediate form, rather, it stores only the
parameter settings, so when SWAT writes the smb.conf file to disk it will write only
those parameters that are at other than the default settings. The result is that all comments
will be lost from the smb.conf file. Additionally, the parameters will be written back in
internal ordering.
</para>

<para><note>
So before using SWAT please be warned - SWAT will completely replace your smb.conf with
a fully optimised file that has been stripped of all comments you might have placed there
and only non-default settings will be written to the file.
</note></para>

<para>
SWAT should be installed to run via the network super daemon. Depending on which system
your Unix/Linux system has you will have either an <filename>inetd</filename> or
<filename>xinetd</filename> based system.
</para>

<para>
The nature and location of the network super
</para>

<sect2>
<title>The SWAT Home Page</title>

<para>
Blah blah here.
</para>

</sect2>
<sect2>
<title>Global Settings</title>

<para>
Document steps right here!
</para>

</sect2>
<sect2>
<title>The SWAT Wizard</title>

<para>
Lots of blah blah here.
</para>

</sect2>

<sect2>
<title>Share Settings</title>

<para>
Document steps right here!
</para>

</sect2>

<sect2>
<title>Printing Settings</title>

<para>
Document steps right here!
</para>

</sect2>
<sect2>
<title>The Status Page</title>

<para>
Document steps right here!
</para>

</sect2>

<sect2>
<title>The Password Change Page</title>

<para>
Document steps right here!
</para>

</sect2>
</sect1>
</chapter>