[mod_python] 3.1.1b Feedback

Conrad Steenberg conrad at hep.caltech.edu
Wed Oct 22 11:56:13 EST 2003

Hi Grisha

Since I was one of the complainers about the session locks in 3.1.0a,
I'm happy to confirm that 3.1.1b now works for me. Thanks!

The server startup log is given below. I don't actually use the
mod_python sessions, so for me it would still be useful to be able to
turn that feature off. But that is just a minor footnote :-)


I noticed another surprising behaviour relating to the PythonImport and
PythonPath directives (not new with 3.1.1b though):

For a Directory directive in the main httpd.conf file e.g.

<Directory /usr/mypath/>
       SetHandler python-program
       AddHandler python-program .py
       PythonInterpPerDirective On
       PythonHandler myhandler
       DirectoryIndex myhandler.py
       PythonInterpPerDirectory On

# Name of the interpreter
       PythonInterpreter default_interp
       PythonPath "sys.path+['/usr/mypath']"
# Init for the 'default' server
PythonImport server_init default_interp

The PythonImport directive loads the file /usr/mypath/server-init.py
into the default_interp interpreter. If the PythonPath directive is
omitted, this import fails. 



[Wed Oct 22 11:41:00 2003] [notice] mod_python: Creating 150 session
mutexes based on 150 max processes and 0 max threads.
[Wed Oct 22 11:41:00 2003] [error] (28)No space left on device:
mod_python: Failed to create global mutex 125 of 150
[Wed Oct 22 11:41:00 2003] [error] mod_python: We can probably continue,
but with diminished ability to process session locks.
[Wed Oct 22 11:41:00 2003] [error] mod_python: Hint: On Linux, the
problem may be the number of available semaphores, check 'sysctl
[Wed Oct 22 11:41:00 2003] [notice] Apache/2.0.47 (Unix) mod_ssl/2.0.47
OpenSSL/0.9.7b mod_python/3.1.1b Python/2.2.3 configured -- resuming
normal operations

Conrad Steenberg <conrad at hep.caltech.edu>

More information about the Mod_python mailing list