from this link i found
http://us4.samba.org/samba/docs/man/...html#id2589859
is this what you wanted??
regards Vinny
Validate SWAT Installation
The very first step that should be taken before attempting to configure a host system for SWAT operation is to check that it is installed. This may seem a trivial point to some, however several Linux distributions do not install SWAT by default, even though they do ship an install-able binary support package containing SWAT on the distribution media.
When you have confirmed that SWAT is installed it is necessary to validate that the installation includes the binary swat file as well as all the supporting text and Web files. A number of operating system distributions in the past have failed to include the necessary support files, even though the swat binary executable file was installed.
Finally, when you are sure that SWAT has been fully installed, please check the SWAT has been enabled in the control file for the inter-networking super-daemon (inetd or xinetd) that is used on your operating system platform.
Locating the swat File
To validate that SWAT is installed, first locate the swat binary file on the system. It may be found under the following directories:
/usr/local/samba/bin the default Samba location.
/usr/sbin the default location on most Linux systems.
/opt/samba/bin
The actual location is much dependant on the choice of the operating system vendor, or as determined by the administrator who compiled and installed Samba.
There are a number methods that may be used to locate the swat binary file. The following methods may be helpful:
If swat is in your current operating system search path it will be easy to find it. You can ask what are the command-line options for swat as shown here:
frodo:~ # swat -?
Usage: swat [OPTION...]
-a, --disable-authentication Disable authentication (demo mode)
Help options:
-?, --help Show this help message
--usage Display brief usage message
Common samba options:
-d, --debuglevel=DEBUGLEVEL Set debug level
-s, --configfile=CONFIGFILE Use alternative configuration file
-l, --log-basename=LOGFILEBASE Basename for log/debug files
-V, --version Print version
