Changeset 134 for branches/samba-3.0/docs/manpages/swat.8
- Timestamp:
- May 23, 2008, 6:56:41 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/manpages/swat.8
r44 r134 1 .\"Generated by db2man.xsl. Don't modify this, modify the source. 2 .de Sh \" Subsection 3 .br 4 .if t .Sp 5 .ne 5 6 .PP 7 \fB\\$1\fR 8 .PP 9 .. 10 .de Sp \" Vertical space (when we can't use .PP) 11 .if t .sp .5v 12 .if n .sp 13 .. 14 .de Ip \" List item 15 .br 16 .ie \\n(.$>=3 .ne \\$3 17 .el .ne 3 18 .IP "\\$1" \\$2 19 .. 20 .TH "SWAT" 8 "" "" "" 1 .\" Title: swat 2 .\" Author: 3 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/> 4 .\" Date: 05/21/2008 5 .\" Manual: System Administration tools 6 .\" Source: Samba 3.0 7 .\" 8 .TH "SWAT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools" 9 .\" disable hyphenation 10 .nh 11 .\" disable justification (adjust text to left margin only) 12 .ad l 21 13 .SH "NAME" 22 14 swat - Samba Web Administration Tool 23 15 .SH "SYNOPSIS" 24 16 .HP 1 25 swat [ -s <smb config file>] [-a] [-P]17 swat [\-s\ <smb\ config\ file>] [\-a] [\-P] 26 18 .SH "DESCRIPTION" 27 19 .PP 28 20 This tool is part of the 29 21 \fBsamba\fR(7) 30 suite .22 suite\. 31 23 .PP 32 24 swat 33 25 allows a Samba administrator to configure the complex 34 26 \fBsmb.conf\fR(5) 35 file via a Web browser . In addition, a27 file via a Web browser\. In addition, a 36 28 swat 37 29 configuration page has help links to all the configurable options in the 38 \fIsmb .conf\fR39 file allowing an administrator to easily look up the effects of any change .30 \fIsmb\.conf\fR 31 file allowing an administrator to easily look up the effects of any change\. 40 32 .PP 41 33 swat … … 44 36 .SH "OPTIONS" 45 37 .PP 46 -s smb configuration file47 .RS 3n48 The default configuration file path is determined at compile time . The file specified contains the configuration details required by the38 \-s smb configuration file 39 .RS 4 40 The default configuration file path is determined at compile time\. The file specified contains the configuration details required by the 49 41 \fBsmbd\fR(8) 50 server . This is the file that51 swat 52 will modify . The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See53 \fIsmb .conf\fR54 for more information .55 .RE 56 .PP 57 -a58 .RS 3n42 server\. This is the file that 43 swat 44 will modify\. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\. See 45 \fIsmb\.conf\fR 46 for more information\. 47 .RE 48 .PP 49 \-a 50 .RS 4 59 51 This option disables authentication and places 60 52 swat 61 in demo mode. In that mode anyone will be able to modify the 62 \fIsmb.conf\fR 63 file. 64 .sp 65 \fBWARNING: Do NOT enable this option on a production server. \fR 66 .RE 67 .PP 68 -P 69 .RS 3n 70 This option restricts read-only users to the password management page. 71 swat 72 can then be used to change user passwords without users seeing the "View" and "Status" menu buttons. 73 .RE 74 .PP 75 -V 76 .RS 3n 77 Prints the program version number. 78 .RE 79 .PP 80 -s <configuration file> 81 .RS 3n 82 The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See 83 \fIsmb.conf\fR 84 for more information. The default configuration file name is determined at compile time. 85 .RE 86 .PP 87 -d|--debuglevel=level 88 .RS 3n 53 in demo mode\. In that mode anyone will be able to modify the 54 \fIsmb\.conf\fR 55 file\. 56 .sp 57 \fIWARNING: Do NOT enable this option on a production server\. \fR 58 .RE 59 .PP 60 \-P 61 .RS 4 62 This option restricts read\-only users to the password management page\. 63 swat 64 can then be used to change user passwords without users seeing the "View" and "Status" menu buttons\. 65 .RE 66 .PP 67 \-d|\-\-debuglevel=level 68 .RS 4 89 69 \fIlevel\fR 90 is an integer from 0 to 10 . The default value if this parameter is not specified is zero.91 .sp 92 The higher this value, the more detail will be logged to the log files about the activities of the server . At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out.93 .sp 94 Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem . Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.70 is an integer from 0 to 10\. The default value if this parameter is not specified is 0\. 71 .sp 72 The higher this value, the more detail will be logged to the log files about the activities of the server\. At level 0, only critical errors and serious warnings will be logged\. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\. 73 .sp 74 Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\. 95 75 .sp 96 76 Note that specifying this parameter here will override the 97 77 \fIlog level\fR 98 78 parameter in the 99 \fIsmb.conf\fR 100 file. 101 .RE 102 .PP 103 -l|--logfile=logdirectory 104 .RS 3n 105 Base directory name for log/debug files. The extension 106 \fB".progname"\fR 107 will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client. 108 .RE 109 .PP 110 -h|--help 111 .RS 3n 112 Print a summary of command line options. 79 \fIsmb\.conf\fR 80 file\. 81 .RE 82 .PP 83 \-V 84 .RS 4 85 Prints the program version number\. 86 .RE 87 .PP 88 \-s <configuration file> 89 .RS 4 90 The file specified contains the configuration details required by the server\. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\. See 91 \fIsmb\.conf\fR 92 for more information\. The default configuration file name is determined at compile time\. 93 .RE 94 .PP 95 \-l|\-\-log\-basename=logdirectory 96 .RS 4 97 Base directory name for log/debug files\. The extension 98 \fB"\.progname"\fR 99 will be appended (e\.g\. log\.smbclient, log\.smbd, etc\.\.\.)\. The log file is never removed by the client\. 100 .RE 101 .PP 102 \-h|\-\-help 103 .RS 4 104 Print a summary of command line options\. 113 105 .RE 114 106 .SH "INSTALLATION" 115 107 .PP 116 Swat is included as binary package with most distributions . The package manager in this case takes care of the installation and configuration. This section is only for those who have compiled swat from scratch.108 Swat is included as binary package with most distributions\. The package manager in this case takes care of the installation and configuration\. This section is only for those who have compiled swat from scratch\. 117 109 .PP 118 110 After you compile SWAT you need to run … … 120 112 to install the 121 113 swat 122 binary and the various help files and images. A default install would put these in: 123 .TP 3n 124 \(bu 114 binary and the various help files and images\. A default install would put these in: 115 .sp 116 .RS 4 117 .ie n \{\ 118 \h'-04'\(bu\h'+03'\c 119 .\} 120 .el \{\ 121 .sp -1 122 .IP \(bu 2.3 123 .\} 125 124 /usr/local/samba/sbin/swat 126 .TP 3n 127 \(bu 125 .RE 126 .sp 127 .RS 4 128 .ie n \{\ 129 \h'-04'\(bu\h'+03'\c 130 .\} 131 .el \{\ 132 .sp -1 133 .IP \(bu 2.3 134 .\} 128 135 /usr/local/samba/swat/images/* 129 .TP 3n 130 \(bu 136 .RE 137 .sp 138 .RS 4 139 .ie n \{\ 140 \h'-04'\(bu\h'+03'\c 141 .\} 142 .el \{\ 143 .sp -1 144 .IP \(bu 2.3 145 .\} 131 146 /usr/local/samba/swat/help/* 147 .sp 148 .RE 132 149 .SS "Inetd Installation" 133 150 .PP 134 151 You need to edit your 135 \fI/etc/inetd .conf \fR152 \fI/etc/inetd\.conf \fR 136 153 and 137 154 \fI/etc/services\fR 138 155 to enable SWAT to be launched via 139 inetd .156 inetd\. 140 157 .PP 141 158 In … … 145 162 swat 901/tcp 146 163 .PP 147 Note for NIS/YP and LDAP users - you may need to rebuild the NIS service maps rather than alter your local164 Note for NIS/YP and LDAP users \- you may need to rebuild the NIS service maps rather than alter your local 148 165 \fI /etc/services\fR 149 file .150 .PP 151 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 your166 file\. 167 .PP 168 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 152 169 inetd 153 daemon) .170 daemon)\. 154 171 .PP 155 172 In 156 \fI/etc/inetd .conf\fR173 \fI/etc/inetd\.conf\fR 157 174 you should add a line like this: 158 175 .PP 159 swat stream tcp nowait .400 root /usr/local/samba/sbin/swat swat176 swat stream tcp nowait\.400 root /usr/local/samba/sbin/swat swat 160 177 .PP 161 178 Once you have edited 162 179 \fI/etc/services\fR 163 180 and 164 \fI/etc/inetd .conf\fR165 you need to send a HUP signal to inetd . To do this use166 kill -1 PID167 where PID is the process ID of the inetd daemon .181 \fI/etc/inetd\.conf\fR 182 you need to send a HUP signal to inetd\. To do this use 183 kill \-1 PID 184 where PID is the process ID of the inetd daemon\. 168 185 .SH "LAUNCHING" 169 186 .PP 170 To launch SWAT just run your favorite web browser and point it at "http://localhost:901/" .171 .PP 172 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 .187 To launch SWAT just run your favorite web browser and point it at "http://localhost:901/"\. 188 .PP 189 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\. 173 190 .SH "FILES" 174 191 .PP 175 \fI/etc/inetd .conf\fR176 .RS 3n177 This file must contain suitable startup information for the meta -daemon.178 .RE 179 .PP 180 \fI/etc/services\fR 181 .RS 3n182 This file must contain a mapping of service name (e .g., swat) to service port (e.g., 901) and protocol type (e.g., tcp).183 .RE 184 .PP 185 \fI/usr/local/samba/lib/smb .conf\fR186 .RS 3n192 \fI/etc/inetd\.conf\fR 193 .RS 4 194 This file must contain suitable startup information for the meta\-daemon\. 195 .RE 196 .PP 197 \fI/etc/services\fR 198 .RS 4 199 This file must contain a mapping of service name (e\.g\., swat) to service port (e\.g\., 901) and protocol type (e\.g\., tcp)\. 200 .RE 201 .PP 202 \fI/usr/local/samba/lib/smb\.conf\fR 203 .RS 4 187 204 This is the default location of the 188 205 \fBsmb.conf\fR(5) 189 server configuration file that swat edits . Other common places that systems install this file are190 \fI /usr/samba/lib/smb .conf\fR191 and 192 \fI/etc/smb .conf \fR. This file describes all the services the server is to make available to clients.206 server configuration file that swat edits\. Other common places that systems install this file are 207 \fI /usr/samba/lib/smb\.conf\fR 208 and 209 \fI/etc/smb\.conf \fR\. This file describes all the services the server is to make available to clients\. 193 210 .RE 194 211 .SH "WARNINGS" … … 197 214 will rewrite your 198 215 \fBsmb.conf\fR(5) 199 file . It will rearrange the entries and delete all comments,216 file\. It will rearrange the entries and delete all comments, 200 217 \fIinclude=\fR 201 218 and 202 219 \fIcopy= \fR 203 options . If you have a carefully crafted204 \fI smb .conf\fR205 then back it up or don 't use swat!220 options\. If you have a carefully crafted 221 \fI smb\.conf\fR 222 then back it up or don\'t use swat! 206 223 .SH "VERSION" 207 224 .PP 208 This man page is correct for version 3 .0 of the Samba suite.225 This man page is correct for version 3\.0 of the Samba suite\. 209 226 .SH "SEE ALSO" 210 227 .PP … … 214 231 .SH "AUTHOR" 215 232 .PP 216 The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. 217 .PP 218 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 219 ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. 220 233 The original Samba software and related utilities were created by Andrew Tridgell\. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\. 234 .PP 235 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 236 ftp://ftp\.icce\.rug\.nl/pub/unix/) and updated for the Samba 2\.0 release by Jeremy Allison\. The conversion to DocBook for Samba 2\.2 was done by Gerald Carter\. The conversion to DocBook XML 4\.2 for Samba 3\.0 was done by Alexander Bokovoy\.
Note:
See TracChangeset
for help on using the changeset viewer.