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.
Because in Linux they show all "threads" as "processes" (unlike UNIX which shows only processes and requires other tools to look at threads). So what you're actually seeing is multiple "threads". This has to do with the way the Linux community chose to deal with the NPTL (Native Posix Thread Library).
If you had to use the -m it means you, like me, have a server that has an older procps package that didn't do this by default. It doesn't really change anything except the way it displays.
If they are threads they are using the same memory map (/proc/<pid>/maps). When I looked at this in the past I saw it mainly for a couple of Java things. By looking at the process name I was able to identify all the pids (using the -m) then find that there were real "processes" with different maps. All the other "processes" had the same maps as one of the above.
The main reason this becomes important is the way it is viewed would make you think the process is using more CPU and Memory than it really is if you summed up all the "processes". By doing the above exercise I was able to confirm that the memory maps were the same so it was only uses the total for one rather than the total for all.