[
http://issues.apache.org/jira/browse/MODPYTHON-126?page=comments#action_12366319
]
Graham Dumpleton commented on MODPYTHON-126:
FWIW, I think I know how to fix the above so it works. This time I stumbled
onto the fact that in Apache one can p
Hello.
In our package in Mandriva I patch mod_python.c so that the mutex stuff is put
in "/var/cache/httpd/mod_python/". But now with mod_python-3.2.7 plus fixes
from the trunk and running the test suite it complains it cannot access
"/var/cache/httpd/mod_python/" (of course). So my question/re
[
http://issues.apache.org/jira/browse/MODPYTHON-111?page=comments#action_12366331
]
Sebastjan Trepca commented on MODPYTHON-111:
OK, I understand and agree with your but then someone should change the
documentation because now it says:
"
A ses
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=all ]
Sebastjan Trepca updated MODPYTHON-111:
---
Component: documentation
> Sessions don't set accessed time on read
>
>
> Key: MODPYTHON-111
tisdagen den 14 februari 2006 18.35 skrev Jim Gallacher:
> Oden Eriksson wrote:
> > tisdagen den 14 februari 2006 14.19 skrev Jim Gallacher:
> >>Oden Eriksson wrote:
> >>>Hello.
> >>>
> >>>In our package in Mandriva I patch mod_python.c so that the mutex stuff
> >>>is put in "/var/cache/httpd/mod_p
On Tue, 14 Feb 2006, Jim Gallacher wrote:
I wonder if we should generalize this, so rather than PythonMutexDir, we have
PythonModuleConfig. Usage might look like:
PythonModuleConfig mutex_dir /path/to/mutexs
PythonModuleConfig max_mutex_locks 8
I may be wrong, but I think the reason this wa
Based on today's traffic on the mailing lists, I think that we should
go for a short-term 3.2.8 release of mod_python, with certified Apache
2.2 support on multiple platforms. The code is only there but I
suppose we'll need a lot of testing, so maybe we could expect to
release this in a month or tw
2006/2/14, Nicolas Lehuen <[EMAIL PROTECTED]>:
> Based on today's traffic on the mailing lists, I think that we should
> go for a short-term 3.2.8 release of mod_python, with certified Apache
> 2.2 support on multiple platforms. The code is only there but I
> suppose we'll need a lot of testing, so
Nicolas Lehuen wrote:
Based on today's traffic on the mailing lists, I think that we should
go for a short-term 3.2.8 release of mod_python, with certified Apache
2.2 support on multiple platforms. The code is only there but I
suppose we'll need a lot of testing, so maybe we could expect to
relea
On Tue, 14 Feb 2006, Nicolas Lehuen wrote:
2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
[...]
If we want to go down the path of having interim 3.2 bug rollup releases
while 3.3 is being developed, might I suggest that we target the following
for such a release in the near future.
MODPYTHO
Grisha wrote ..
>
> On Tue, 14 Feb 2006, Nicolas Lehuen wrote:
>
> > 2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
> > [...]
> >> If we want to go down the path of having interim 3.2 bug rollup releases
> >> while 3.3 is being developed, might I suggest that we target the following
> >> for su
Grisha wrote ..
>
> On Tue, 14 Feb 2006, Jim Gallacher wrote:
>
> > I wonder if we should generalize this, so rather than PythonMutexDir,
> we have
> > PythonModuleConfig. Usage might look like:
> >
> > PythonModuleConfig mutex_dir /path/to/mutexs
> > PythonModuleConfig max_mutex_locks 8
>
> I
Is my list of suggested JIRA items then seen as being reasonable for
such a projected release?
Do we want to create a new JIRA issue for the mutex directory issue and
also include a fix for that, but limit it to just an option to configure
to override the directory?
Graham
Nicolas Lehuen wrote .
Graham Dumpleton wrote:
Grisha wrote ..
On Tue, 14 Feb 2006, Jim Gallacher wrote:
I wonder if we should generalize this, so rather than PythonMutexDir,
we have
PythonModuleConfig. Usage might look like:
PythonModuleConfig mutex_dir /path/to/mutexs
PythonModuleConfig max_mutex_locks 8
Graham Dumpleton wrote:
Is my list of suggested JIRA items then seen as being reasonable for
such a projected release?
This seems reasonable, since we have either already committed the fixes
or have patches available (I think).
Do we want to create a new JIRA issue for the mutex directory i
Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > Is my list of suggested JIRA items then seen as being reasonable for
> > such a projected release?
>
> This seems reasonable, since we have either already committed the fixes
> or have patches available (I think).
I don't have changes ready for
Hmmm, somehow I managed to vapourise an email, didn't even get
to my sent mail box. Let me try this again.
Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > Correct, is actually done from the mod_python module init function.
> >
> > The only way one could have it dynamically changing is throug
Hi,
I've built Apache 2.2 and tested mod_python SVN trunk with it.
The two register_cleanup tests fail. Apparently it's because the test
code registers a cleanup function giving the current request as
parameter. Of course when the cleanup function is called, the request
object is no longer valid,
18 matches
Mail list logo
