[notice] mod_python:

[ulises]

[Wed Jul 13 23:43:04 2005] [notice] mod_python: Creating 32 session mutexes based on 0 max processes and 250 max threads.
[Wed Jul 13 23:43:08 2005] [notice] Apache/2.0.54 (Win32) mod_python/3.1.3 Python/2.3.3 mod_ssl/2.0.54 OpenSSL/0.9.7c PHP/5.0.4 mod_perl/1.999.21 Perl/v5.8.6 configured -- resuming normal operations
[Wed Jul 13 23:43:08 2005] [notice] Server built: May 29 2005 12:18:55
[Wed Jul 13 23:43:08 2005] [notice] Parent: Created child process 3044
[Wed Jul 13 23:43:12 2005] [notice] mod_python: Creating 32 session mutexes based on 0 max processes and 250 max threads.
[Wed Jul 13 23:43:16 2005] [notice] Child 3044: Child process is running
[Wed Jul 13 23:43:16 2005] [notice] Child 3044: Acquired the start mutex.
[Wed Jul 13 23:43:16 2005] [notice] Child 3044: Starting 250 worker threads.

Solution for Bug Sorry español

[Wiedmann]

Where is your problem?

[ulises]

Where is your problem?

for mod_python: Creating 32 session mutexes based on 0 max processes and 250 max threads.

[Wiedmann]

Which information do you expect instead of this one?

BTW:

When I watch the "error.log" I see this, and I am looking for a solution:

mod_python: Creating 32 session mutexes based on 0 max processes and 250 max threads.

That's just for your information, like the other [info] in the "error.log". It's nothing with the level warn, error, crit, alert or emerg.