You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

[EDIT]: For everyone else out there using fedora, I just found this neat feature in system-config-services: If you click the "On Demand Services" tab you can edit all the xinetd services, such as swat, without needing to manually edit files. Swat of course must be checked to enable it.

--->Error: "The connection to the server was reset while the page was loading."
I tried Eiphany, but that just refused to connect at all (though it did not report a "connection refused" as it would for other blocked ports).

I also noticed that I get this firefox message whether or not Swat is actually running!!
Alternatively, if I do not "chkconfig swat on/manually edit /etc/xinetd.d/swat "disable" to "no", then I just get a "connection refused" like I would for any blocked port.

Sorry looks like you're better at this than me, but I've checked my core1 and core3 books, that have swat instructions in them, unfortunately they don't shed any light on your problem. What you've done agrees with what they say.
I've managed to get by without swat, using the RH Samba server configuration gui.

I actually managed to get it working quite straightforwardly on a Fedora Core 6 i386 machine, so I guess the rather unique problems on my FC5 x86_64 must be the result of some fiddling I've done at some point or other.

Would be nice if I knew how to fix it, as some guru once said, there is always a way to fix things on linux (supposedly!). But then I guess you can't have everything... If nobody knows, and it hasn't affected anyone else, then I'm not going to spend the next 4 weeks wrapping my head around it!