Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 recently upgraded from Fedora 9 to Fedora 12 (x86_64 version) and I'm having performance problems with httpd, which is the main purpose for this particular machine.
When I tried to start httpd the first time, I encountered problems with the /etc/httpd/conf/httpd.conf file: the modules mod_file_cache.so and mod_mem_cache.so appeared to be missing from the new OS, so I commented out those lines from my previous version of httpd.conf.
Now, when I check the status of httpd, I get the following:
[root@localhost]# service httpd status
httpd dead but subsys locked
I'm not sure what that means. Apache does seem to be running, and queries from outside to my web site are serviced normally most of the time. If I query active processes, I see 12 instances of httpd running:
Notice the first entry is assigned to root? That's odd... not sure I've ever seen that before.
At any rate, I've noticed some pretty odd behavior out of the web site: just this morning, the machine performance went to hell. I checked "top" -- it took about 90 seconds for the terminal window to respond, and then refresh time, which is supposed to be around 2 seconds, took more like 30 seconds to a minute. There was no single process eating the cpu, but the httpd processes were sitting at the top, along with a single mysqld process. This condition lasted at least 10 minutes, and then I manually rebooted the machine (e.g. hit the Big Red Switch.)
I'd like to reduce the number of processes httpd spawns. When people hit my server, it seems to generate a whole bunch of httpd processes, like 20 or 25. I think there's a parameter in httpd.conf that controls that, but I don't recall which. Can anybody suggest normal settings for httpd.conf that will tame this process-spawning? Thanks.