In relation to packages, redhat always broke samba into multiple bits, samba-common, samba-server, samba-swat etc. you installed the bits you wanted. you may not have originally installed the samba-swat file.
Now on to the problem: I assume xinetd is started? #service xinetd status [1] if its not started then: #service xinetd start if it is already started, try restarting it (in case it has not been restarted since the last config change:) #service xinetd restart if its still not working then, there is a bit of a bug (or there was at some stage) with swat and the only_from line. Try commenting out that line (being aware that anyone will then be able to connect to your swat, although they still have to authenticate) and restarting xinetd (see above) [1] NB in the above I have assumed that fedora has followed redhat in having the "service" command. If not run the script directly, eg #/etc/init.d/xinetd status (etc) Hmm thinking again, on redhat the sile for xinetd/swat's configuration is usually /etc/xinetd.d/swat, nor /etc/xinetd.d/services. Maybe fedora does this differently. is that where the rpm installed it? On Fri, 16 Apr 2004 13:21:35 +1200 Roger Searle <[EMAIL PROTECTED]> wrote: > Hi, I'm trying to get swat going again, this time on my notebook running > fedora. Been following some links sent last time: > > http://info.ccone.at/INFO/Samba/SWAT.html > http://rtfm.dyndns.info/tips/2000/05/05/31.shtml > > First I couldn't locate the swat binary anywhere even after installing > the samba package from the CDs, so I downloaded samba-3.0.2a source > files and successfully compiled/installed. My first compile! > > When I try http://127.0.0.1:901/ in mozilla I get "the document > contains no data". > > I have the following in the /etc/xinetd.d/services file: > { > service swat > port = 901 > socket_type = stream > wait = no > only_from = localhost > user = root > server = /usr/local/samba/sbin/swat > log_on_failure += USERID > disable = no > } > > I have confirmed that the path to the swat executable is correct, and > have restarted the smb and xinetd services, and then tried rebooting but > still can't get swat running in the browser. Can anyone suggest what I > should do next? > > Cheers, > Roger > > > -- Nick Rout <[EMAIL PROTECTED]>
