Samba SWAT issues...

[kaze]

Having a devil of a time getting SWAT up.

I thought I selected it during install.

/etc/services has the swat 901/tcp line - it is not commented out

There is no /etc/inetd.d directory.

There is a /etc/xinetd.d directory, but no swat file in it.

I was unable to download the samba-swat rpm from the redhat site either via
rpm ftp or via http from a web browser, but found it on CD #3 and:

[root at ImediaArchive root]# rpm -ivh samba-swat-3.0.0-15.i386.rpm
warning: samba-swat-3.0.0-15.i386.rpm: V3 DSA signature: NOKEY, key ID
4f2a6fd2
Preparing...                ###########################################
[100%]
        package samba-swat-3.0.0-15 is already installed
[root at ImediaArchive root]# rpm -qi samba-swat-3.0.0-15.i386.rpm
package samba-swat-3.0.0-15.i386.rpm is not installed
[root at ImediaArchive root]# rpm -q samba-swat-3.0.0-15.i386.rpm
package samba-swat-3.0.0-15.i386.rpm is not installed
[root at ImediaArchive root]# rpm -e samba-swat-3.0.0-15.i386.rpm
error: package samba-swat-3.0.0-15.i386.rpm is not installed
[root at ImediaArchive root]# rpm -ivh samba-swat-3.0.0-15.i386.rpm
warning: samba-swat-3.0.0-15.i386.rpm: V3 DSA signature: NOKEY, key ID
4f2a6fd2
Preparing...                ###########################################
[100%]
        package samba-swat-3.0.0-15 is already installed
[root at ImediaArchive root]#

So, I can't install it cause it's already there, and I can't remove it cause
it's not there...

Anyway there now is a /etc/xinetd.d/swat, so I went in there and changed the
disabled to "no"

Question: is inetd.d the same as xinetd.d?

I did a "kill -1 1178" where xinitd.d's PID was 1178, nothing at
http://ImediaArchive:901 (no firewall btwn them)

In /etc/xinetd.conf I added: "swat stream tcp nowait.400 root
/usr/local/samba/bin/swat swat" but vi highlights the three words swat in
yellow..

kill -1 1178 again, but still nothing.

What to do? I got SWAT up a few months ago really quickly on a Debian box
(not that it solved all my SAMBA issues yet either) but this is overly
frustrating on Fedora - what to do?