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.
Red Hat 7.1 Workstation (Not deluxe) complete install...
Ximian Gnome complete install.......
Now, my system is pretty darn bitchin........ but when I check the CPU/Mem usage applet, I am always seeing the CPU bar going from 0-50% then back to zero, kinda like a heartbeat.... And the memory useage seems to just climb the longer the system has been up and running......
Anyone got any ideas why?? Are there 'memory leaks' like in windoze?
Are there any 'Memory Compactors' out there for Linux like there are for Windowz?
Is there a program that will track down runaway threads or loose programs???
Here are my system specs if it helps.....
Intel P-III 1000
Asus CUSL2-C Mainboard
Creative Labs SoundBlaster Live! X-Gamer 5.1
256mb Micron PC-133 RAM
46g IBM Deskstar (Win2k)
30g Western Digital (Red Hat)
Pioneer 16x DVD
Philips 8x4x32 CD-RW
I thought my system would just FLY with linux, and it really does most times.... But sometimes it slows down. And there is the fact that the CPU is always 'working'... And the free memory seems to dissappear......
Since you said "CPU/Mem usage applet"; I hear the word java. Java is both a memory and CPU hog. It's quite possible that your monitoring program is the one eating up the CPU. I'd suggest that you get to a command line and use 'top'. It will tell you everything you want to know and possibly more than you need to know.
So I appear to be using 103MB, but of that 103MB 3.5MB is used for buffers and 53MB is being used as disk cache. If I was to access a few more files and execute a few more programs them I would use all my free memory for caches and buffers. When a program needs to use the RAM these buffers would be flushed and the memory give to the program. You need to look at what the memory is being used for as much as how much is being used. The good old UNIX 'always-full' memory model.
What this really means is that of your 240MB of used memory, 149MB is used for disk caching.
When you run a program like Netscap it is read from the harddisk into memory and executed. When you shut it the program terminates, yet the data read from the HDD is kept in memory so long as that memory isn't needed for anything else. If you then start Netscape again a few moments later (or even hours if the machine hasn't needed the memory for anything else) the OS won't read all the data off the hard disk again, it will simply used the 'cached' copy that is in memory from the last time. This helps to speed things along as even very fask disks are *very* slow compared to memory. A similar process happens when you save things to disk, its stored in memory and then written to disk when its convienient for the OS.
So you're really using about 91MB of memory, the rest is just being used for caching becuase its not needed for anything else. If you had lots of programs running or a program that was chewing all your memory this figure for disk cache would be very small.
Hope that explains things a little. Its just touching the surface.
This thread has been helpful for me, however it has not answered all of my questions on the subject. Essentially I cannot account for all of the memory.
Using a compination of top and free, I've found that I still cannot account for 60-90 megs worth of ram. Is there anything else that might be eating it up? Could 60-90 megs be "missing" from rounding error - everything is displayed in MBs in top.