Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In development, I'd like to have changes to my application propagate immediately. "MaxRequestsPerChild 1" restarts each process after a request, but if there are multiple server processes, changes still don't propagate until each process restarts.

I've tried several different directives to limit the number of server processes to 1:

StartServers 1
MinSpareThreads 1
MaxSpareThreads 1
ThreadLimit 1
ThreadsPerChild 1
MaxClients 1
MaxRequestsPerChild 1

Apache still starts with multiple (3) apache2 processes. I'm using the mpm_worker module

share|improve this question

Having those parameters is very counter productive for apache performance, I wouldn't recommend them.

Depending on the language you're developing with you have different mechanisms to ensure a proper load of new code, but in any case the only way to kill all children at the same time would be to restart apache, with that you'll be kicking everyone out so I don't really think you want to do that either.

My recommendation would be to find the best way to reload code depending on what you are running, for example for python you can use mod_wsgi

share|improve this answer
I'm using mod_wsgi, and I'm developing, so I'm not worried about performance. I want a solution that reloads the application whenever any change is made. According to, setting MaxRequestsPerChild 1 seems to be the only option. However, I also need to have only one process running. How can I configure that? – Michael Gummelt Jan 16 '11 at 23:30
Michael, you haven't read that document properly if the conclusion you came to is that MaxRequestPerChild is the only solution. That solution only applies to embedded mode or Apache's main processes. Use daemon mode of mod_wsgi and delegate your WSGI application to that. You can then setup the code change monitoring described in that document. Using daemon mode also allows you to run the single process you are after. – Graham Dumpleton Jan 17 '11 at 2:59
Graham is completely right, that's the right way to do it – lynxman Jan 17 '11 at 8:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.