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'm not sure whether "httpd -V" is 100% reliable for this, as someone might have edited src/include/httpd.h instead to change HARD_SERVER_LIMIT, in which case I don't think it will show up in "httpd -V".
One way to confirm this is to change MaxClients to above what you think HARD_SERVER_LIMIT is (i.e. to 257+ if we assume the default HARD_SERVER_LIMIT of 256 is in force), and run "apachectl configtest" or "httpd -t" to test the syntax of the config file. If MaClients is higher than HARD_SERVER_LIMIT you'll get an error message similar to this:
WARNING: MaxClients of 257 exceeds compile time limit of 256 servers,
lowering MaxClients to 256. To increase, please see the
HARD_SERVER_LIMIT define in src/include/httpd.h.
Whether you are using prefork or worker MPM depends on your configuration (see https://httpd.apache.org/docs/2.0/mpm.html). One way to tell which is in use, is to run "httpd -V" and look for the "Server MPM" line. Alternately run "httpd -l", and look for prefork.c or worker.c in the output.
If you're changing things in the source, I trust you are recompiling too, otherwise your changes will have no effect. If so, the MPM is specified with the "--with-mpm=MPM" option to the configure command. The default is prefork on Unix.
If you are recompiling, is there a reason for running Apache 2.2.15 and not the latest patch level (2.2.22)?
The correct way to change #define values is to add something like "-D HARD_SERVER_LIMIT=1024" to your CFLAGS environment variable before compiling.