| Michel Jouvin 2005-12-10, 2:45 am |
| Graham,
No I am not using any PythonImport directive neither on the prod server,=20
nor on the test server. On the test server, the only mod_python related=20
directive is :
LoadModule python_module modules/mod_python.so
I'll try you suggestion about adding some logging messages in mod_python.c. =
By the way, I just remember that I had one problem to build mod_python on=20
Tru64 with the native compiler (not tried with gcc) because of definition=20
conflict for macro _XOPEN_SOURCES defined by Phyton pyconfig.h. The problem =
is that mod_python includes types.h without this macro defined to the value =
used by Python and before including pyconfig.h (Python.h). My hack was=20
pretty dirty : undefine this macro in pyconfig.h to build mod_python=20
successfully. But may be it is responsible for this side effect=20
(unfortunatly this seems the only one...).
I'll try to find the time to check this in the coming days...
Michel
--On samedi 10 d=C3=A9cembre 2005 15:00 +1100 Graham Dumpleton=20
<grahamd@dscpl.com.au> wrote:
> Just to make sure, are you using PythonImport directive at all? Want to
> eliminate
> this as these get run regardless of whether a request against a
> mod_python
> handler is received. If the code associated with PythonImport took some
> time
> to run, that might be a contributor.
>
> Anyway, not sure what else to suggest. I would probably start adding
> extra
> logging calls in the mod_python.c file of mod_python so that one could
> see when
> the Apache child process init function for mod_python is entered and
> exited for
> each process ID. That way could see if that is returning quickly or
> taking some
> time.
>
> Graham
>
> On 10/12/2005, at 10:38 AM, Michel Jouvin wrote:
>
>
****************************************
*********************
* Michel Jouvin Email : jouvin@lal.in2p3.fr *
* LAL / CNRS Tel : +33 1 64468932 *
* B.P. 34 Fax : +33 1 69079404 *
* 91898 Orsay Cedex *
* France *
****************************************
*********************
|