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.
Can you explain to me what is unix protocol? and what is Active UNIX domain sockets?
Well, for "Active Unix Domain sockets", according to that tutorial on linux planet:
You can ignore everything under "Active UNIX domain sockets." Those are local inter-process communications, not network connections. To avoid displaying them at all, do this:
$ netstat --inet -a
This will display only network connections, both listening and established.
Since the unix protocol falls under the Active UNIX domain sockets, you can likely ignore all of that also.
Glad I could be of help!
I am most definitely not any kind of a networking guru. But from a security standpoint, I have wondered about this also. Form my rather limited understanding, I have found that simply running:
netstat --inet -a
will yield the most useful info.
NOTE: If you have any bittorrent apps running, you will get a crapload of connections when you run netstat because it will list all of the users that are uploading or downloading your torrent files.