Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
A daemon is a background process that waits for work to do. Typically it LISTENs on a specific port and when it gets a request does whatever it is designed for.
sendmail = Waits for requests to do mail
sshd = Waits for ssh (user login/command) requests
nfsd = Waits for requests from remote hosts to allow filesystems to be mounted from local host to remote host.
xinetd (or inetd) = Specialized daemon that is configured to listen for other items that you don't want running as daemons of their own. Some daemons have low usage so there is no reason to eat up CPU by running them all the time. By having xinetd LISTEN for their ports it can be used to only start the daemon when it knows there is a request for it. An example would be ftpd. ftpd is designed for allowing remote users to connect and transfer files. There is no reason for ftpd to be running all the time on most servers so it would typically only be started via xinetd (or inetd).
Most daemons are started at your boot up by init scripts. If you didn't start it from terminal you can't really bring it into the foreground later. You can actually start things as daemons from the command line by backgrounding them. This is done by putting "&" at the end of the command line. Also for such backgrounded processes to stay running after you log out of the terminal you would have to use the "nohup" command at the start of the command line. If you did background a job at command line you can bring it back to the foreground by using fg.
The following commands will give you more information:
Look at "fg", "bg", background in that man page.