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.
I am setting up a server to do nothing but handle FTP and Telnet. I am using RedHat 7.1 and it is refusing all teh connections from anywhere. I saw something in the beinging about a firewall and didnt choose one, so I assumed that it didnt install the firewall. Why would it be refusing all of these connections then?
If its going to do a lot of telnet and FTP then you will want to run your telnet/ftp daemons all the time, instead of having inetd start them each time someone attempts to connect. Just remove the ftp and telnet lines from /etc/inetd.conf and put those same lines in one of your startup scripts. Remember to restart inetd !
Wel, If I am not mistaken, all he wanted is to enable telnet and ftp and disable ipchains or iptables to allow connection. With command ntsysv, it will let him enable and disable services by selecting them checking or unchecking..that's all and next time he reboots services will remain as he selected whether on or off.
Originally posted by nabil Wel, If I am not mistaken, all he wanted is to enable telnet and ftp...
Correct. My original post in this thread wasn't a solution but just a comment, as if you leave inetd starting the ftp and telnet daemons each time someone wants to connect you're introducing an unnecessary overhead as the trade-off of saving memory by killing the daemon when its not in use isn't worth the additional overhead of starting it up again all the time.
As you replied saying that ntsysv would take care of this I was just wondering how it would decide what to run all the time, and what to let inetd start... clearly we're talking cross purposes!