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.
i have a Intel Quad Core Xeon X3440 (4 x 2.53GHz, 8MB Cache, Hyper Threaded) with 16gig and 1tb harddrive with a 1gb port and my apache is causing my cpu to go up to 100% on all four cores heres my http.config
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
Looking at that shot (of htop's output, which doesn't show iowait)
I'd say the CPUs are bored out of their tree on each individual task,
and I'll hazard the guess that the I/O subsystem of your MySQL
database is the bottleneck in this scenario. What exactly ARE you
running on the machine, what is the hard-disk subsystem (controller
type, how many disks, which raid level,...)?
Say what ?. They're all running flat out - mainly userspace code.
I wonder if the sort has been inverted. @awww hit F4 to check the sort of the CPU%.
Sorry, wasn't specific; not a single task was sitting at high CPU;
and yes, I didn't consider a reversed sort order - that wouldn't
make too much sense imho. Unfortunately the ntop shot doesn't
show "waits", which is what I suspect will be high on the box.
Sorry, but those all look like they're taken at different times, and
none of these have a load that gets close to what your first shot
showed us. For future reference: can you please, instead of using
screenshots on an external site just copy & paste the text into code-blocks?
Makes life so much easier and quicker for people willing to help you.