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.
The CPU usage. 1.00 = 100% of what your CPU can do. Anything over that means requests are stacking up and waiting for free cycles to run. It's like the boss coming in and dumping more work on your desk when you already have a full day.
The algorithm for computing load averages is quite trivial -- it's just an average of the number of processes in the CPU's run queue during the given period (1, 5, and 15 minutes) -- on SMP machines it's the sum of the number of processes in each run queue, again averaged. If you have a CPU load of over two, it means, on average, two processes were runable on the CPU during the given period. If you only have one processor, that obviously means that the CPU had to switch back and forth between multiple processes trying to run on it.
The average number of processes running in the last 1, 5 15 minutes may seem to be fairly useless info, but check into the batch command. Batch allows you to run a program(s) when that load average goes below .8 It can be set to a different number with the atrun command. It may come in handy for you some day. If you are running an X windows terminal, try this little perl script to watch the load average in the title bar of the terminal. Run it in the background.
my $host = `/bin/hostname`;
#open /proc/loadavg file
open(LOADAVG,"/proc/loadavg") || die "Cannot open /proc/loadavg: $!\n";