Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
ok I turned of the firewall and looked in both places both /etc/hosts.deny and /etc/hosts.allow were blank except for the # and the words describing what it is after the # sign
yet it gives the same problem error
I tried the guarddog got it installed and used it to disable the firewall then I went to lokkit to see if it was disabled. And it was not after it states that it was disabled in the terminal it says this
[root@loocalhost guarddog-2.0.0] # Mutex destroy failure: Device or resource busy
kdeinit: Fatal IO error: client killed
Kdeinit: sending SIGHUP to children
Kdeinit: sending SIGTERM to children
this is where I enter guarddog
[root@loocalhost guarddog-2.0.0] # guarddog
also it looks like there are three ways to install it
not knowing what I was doing at the time I did all three lol
The "Mutex destroy failure..." error message has no bearing on anything. And in lokkit, it will always say High, no matter what the actual firewall settings are. If guarddog says it is off, then it is off. Did you try swat after you disabled the firewall in Guarddog?
Is there another way to get into swat I did try typing swat in /usr/local/samba/bin also swat 901/tcp but it just goes to the next line and it is blanke somthing like this
[root@localhost bin] swat 901/tcp
the next line is blank like the line above this line shows. Also if I enter somthig nothing happens.