I can't run SWAT. Asking for help.

[Ivan Evstegneev]

Hello!!!

First of all I want say that I used this "how-to":
http://samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html#xinetd
as my guide and here I'll give the complete log of my actions:

1) Locating the SWAT File:

this line describes the how-to's preferences:
"/usr/sbin the default location on most Linux systems"

                          and I have this file in the same folder.

2) Locating the SWAT Support Files:
   
this line describes the how-to's preferences:
"frodo:~ # whereis swat
swat: /usr/sbin/swat /usr/share/man/man8/swat.8.gz"

**** and this is what I got on my terminal:
"[root at localhost ~]# whereis swat
swat: /usr/sbin/swat    /usr/share/swat   /usr/share/man/man8/swat.8.gz"

**** as you can see there are two identical paths except the middle one, but I'll talk about it later.


3) We must now check where swat expects to find its support files.

this line describes the how-to's preferences:
"frodo:/ # strings /usr/sbin/swat | grep "/swat"
/swat/
...
/usr/share/samba/swat
frodo:/ #"

******* here some little "spike" appeared, in my case I can only view 
        the man pages for "strings" command but when I tried to run it, I got "command not found".
        and 'cause of it I followed the next instruction:

"jht at frodo:/> find /usr/share/samba/swat -print
/usr/share/samba/swat
/usr/share/samba/swat/help
/usr/share/samba/swat/lang
/usr/share/samba/swat/lang/ja
/usr/share/samba/swat/lang/ja/help
/usr/share/samba/swat/lang/ja/help/welcome.html
/usr/share/samba/swat/lang/ja/images
/usr/share/samba/swat/lang/ja/images/home.gif
...
/usr/share/samba/swat/lang/ja/include
/usr/share/samba/swat/lang/ja/include/header.nocss.html
...
/usr/share/samba/swat/lang/tr
/usr/share/samba/swat/lang/tr/help
/usr/share/samba/swat/lang/tr/help/welcome.html
/usr/share/samba/swat/lang/tr/images
/usr/share/samba/swat/lang/tr/images/home.gif
...
/usr/share/samba/swat/lang/tr/include
/usr/share/samba/swat/lang/tr/include/header.html
/usr/share/samba/swat/using_samba..................................."

******* but for the /usr/share/samba/swat I got nothing. But when I changed a path to "/usr/share/swat"
        it described me all those files listed above. So now you see that the only difference between how-to's paths and mine 
        is that I have swat supported files in "/usr/share/swat" folder and not in "/usr/share/samba/swat"... 
        Actually I created "samba" folder and copied there swat files... but as you can observe it got no effect.


4) Enabling SWAT for Use.

this line describes the how-to's preferences:
"The control file (or files) can be located in the file /etc/inetd.conf
or in the directory /etc/[x]inet[d].d or in a similar location"

***** So I found my "xinetd.conf" and added the following lines as they
asked me: "# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
#              to configure your Samba server. To use SWAT, \
#              connect to port 901 with your favorite web browser.
service swat
{
	port    = 901
	socket_type     = stream
	wait    = no
	only_from = localhost
	user    = root
	server  = /usr/sbin/swat
	log_on_failure  += USERID
	disable = no
}
"


******and now my "xinetd.conf" file looks like this:

"#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/

defaults
{
	instances               = 60
        log_type                = SYSLOG authpriv
        log_on_success		= HOST PID
        log_on_failure		= HOST
	cps			= 25 30
}

includedir /etc/xinetd.d

# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
#              to configure your Samba server. To use SWAT, \
#              connect to port 901 with your favorite web browser.
service swat
{
        port    = 901
        socket_type     = stream
        wait    = no
        only_from = localhost
        user    = root
        server  = /usr/sbin/swat
        log_on_failure  += USERID
        disable = no
}

"

******* Then I opened my firefox and wrote this command:        
        "http://localhost:901/" but it didn't work...


        Am I missing something? or doing something wrong? Any help will
be gladly accepted. :))))


Ivan.