[mod_python] strange behavior with mpm worker (inaccurate number of max processes?)

Alec Matusis matusis at yahoo.com
Mon Jan 21 05:24:38 EST 2008


We are using worker MPM

Our apache configuration is 

 

ServerLimit 40

ThreadLimit 70

 

StartServers          10

MaxClients            1600

MinSpareThreads       75

MaxSpareThreads       200

ThreadsPerChild       40

MaxRequestsPerChild   10000

 

When apache is restarted with 

#apachectl stop

#apachectl start

We get in the error log:

[notice] mod_python: Creating 32 session mutexes based on 40 max processes
and 40 max threads

[notice] Apache/2.2.6 (Unix) mod_python/3.3.1 Python/2.4.1 configured --
resuming normal operations

This is what we expect.

 

Now we restart apache this way: 

#apachectl restart

In the error log:

[notice] SIGHUP received.  Attempting to restart

 [notice] mod_python: Creating 32 session mutexes based on 11 max processes
and 40 max threads.

 [notice] mod_python: using mutex_directory /tmp 

 [notice] Apache/2.2.6 (Unix) mod_python/3.3.1 Python/2.4.1 configured --
resuming normal operations

 

Where does this number "11 max processes" come from? We do not have it
anywhere in the configuration.

 

 

We get

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20080121/552e9eaf/attachment.html


More information about the Mod_python mailing list