Apache Configuration Question

Hi,

I came accross the below article about mod_python and Apache.

http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html

I was wondering if the version of Apache that comes with this stack is using the worker MPM or prefork MPM?

Thanks for a fantastic stack, it has saved me days

Regards

Mark

The Apache that comes with the DjangoStack is using prefork MPM. You can tell be running

root@ip-10-196-54-175:/opt/bitnami# apachectl -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c

prefork.c indicates prefork is being used. worker.c world indicate that worker is being used.

I read on http://blog.projectfondue.com/2009/8/25/apache-… that in ubuntu you can switch to worker by running the following command:

sudo apt-get install apache2-mpm-worker

However after successfully running that command I still get

root@ip-10-196-54-175:/opt/bitnami# apachectl -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c

Interestingly, I see worker.c listed under

root@ip-10-196-54-175:/opt/bitnami# apache2 -l
Compiled in modules:
core.c
mod_log_config.c
mod_logio.c
worker.c
http_core.c
mod_so.c

Can anyone explain what’s happening here?

Hi,

Django Stack works with mod_wsgi by default. As ianrcohen posted, Apache was compiled using the prefork MPM.

BitNami Stacks, AMIs and Virtual Appliances are slef-contained and independent of the system. All the required files are installed in the installation directory and “/opt/bitnami” in the Virtual Appliances and AMI cases. You can use the system package manager to install other modules but the Apache server is independent of the system Apache. You can find more info at http://wiki.bitnami.com