+1
Release what's fixed already, and then keep going afterwards.
But can somebody address MODPYTHON-53 please. (updating modpython.org website).
--
Deron Meranda
Actually it seems that this is yet another case of trying to get
mod_python to hook into more places in the Apache framework;
specifically to hook into other modules.
We've already been discussing specific-module hooks for
mod_ssl - http://issues.apache.org/jira/browse/MODPYTHON-94
On 02/02/2006, at 6:52 AM, Deron Meranda wrote:
Actually it seems that this is yet another case of trying to get
mod_python to hook into more places in the Apache framework;
specifically to hook into other modules.
We've already been discussing specific-module hooks for
mod_ssl -
Again this is a resend. I post one message via my secure SMTP and it
vanishes. Post one via normal SMTP and it goes to list straight away.
This sort of confirms what I suspected which is that my ISPs secure
SMTP is busted somehow in that randomly drops email. :-(
Sorry for the duplicate if first
Graham Dumpleton wrote:
On 01/02/2006, at 9:10 PM, Nicolas Lehuen wrote:
Hi,
I've just checked in some changes to the Python source code in order
to support Python 2.2. Now the test suite runs successfully on Python
2.2.3 on Windows 2000. I've checked that no regressions were
introduced in
Nicolas Lehuen writes:
I've just checked in some changes to the Python source code in order
to support Python 2.2. Now the test suite runs successfully on Python
2.2.3 on Windows 2000. I've checked that no regressions were
introduced in later Python versions, too.
The changes are pretty
I was looking at the new module importer used by mod_python.publisher in
3.2.6 to see whether it reloaded a module if file was replaced with an
older file and have come across some code that worries me a bit. Can
someone else (not just Nicolas) check this code and how it is used in
the context of
Okay, false alarm (I think). Have got myself worked up over nothing.
I missed something very important:
timestamp = fstat(opened.fileno())[-2]
That is the '[-2]' in the above.
I feel like a goose now.
I still though question why file/fstat is done and not stat/file though.
Ie., why open the
2006/2/2, Graham Dumpleton [EMAIL PROTECTED]:
Okay, false alarm (I think). Have got myself worked up over nothing.
I missed something very important:
timestamp = fstat(opened.fileno())[-2]
That is the '[-2]' in the above.
I feel like a goose now.
I still though question why file/fstat
2006/2/2, Graham Dumpleton [EMAIL PROTECTED]:
Note that up until now I hadn't even looked over how this new module
importer was implemented. I knew it wasn't going to solve various of the
existing module importer problems and I knew it was actually going to
introduce some new issues that would
Graham Dumpleton wrote ..
Okay, false alarm (I think). Have got myself worked up over nothing.
I missed something very important:
timestamp = fstat(opened.fileno())[-2]
That is the '[-2]' in the above.
I feel like a goose now.
Now for some explaination of why my brain turned off and
Quick response, because it's 4:36 AM here, I just woke up to feed my
daughter and took all this flak, but I need to sleep :). I guess
that's the problem of having a round-the-planet development team,
between those in America, Europe, Asia and Australia (nobody from
Antarctica yet ?)
Graham :
Nicolas Lehuen wrote ..
Well, I thought that if the file was modified, we needed to open it
anyway, but you're right, that's optimising for a minority case. We
might as well use stat and open the file only if it has changed.
I've wrote an alternative publisher a few months ago that
Daniel J. Popowich wrote:
Nicolas Lehuen writes:
I've just checked in some changes to the Python source code in order
to support Python 2.2. Now the test suite runs successfully on Python
2.2.3 on Windows 2000. I've checked that no regressions were
introduced in later Python versions, too.
2006/2/2, Jim Gallacher [EMAIL PROTECTED]:
If a formal decision was made, then it's a done deal, right? If not
and uses of 2.3 have slipped in then perhaps it's a done deal anyway
because no one can stomach the thought of taking out the 2.3-isms at
this late date.
My impression is that
Nicolas Lehuen wrote ..
2006/2/2, Graham Dumpleton [EMAIL PROTECTED]:
Note that up until now I hadn't even looked over how this new module
importer was implemented. I knew it wasn't going to solve various of
the
existing module importer problems and I knew it was actually going to
OK, I've changed cache.py so that it uses stat() then open() the file
if it needs to be reloaded. I've also added a unit test that makes
sure the module cache is behaving as expected.
Graham, I don't think the stat() / open() / fstat() sequence is
required. How would that improve accuracy ?
OK, I've reverted my changes. I left python22.py in place, because I
still hope to be able to use it with PythonImport. The only problem is
being able to define it in the unit tests.
Regards,
Nicolas
2006/2/2, Nicolas Lehuen [EMAIL PROTECTED]:
2006/2/2, Jim Gallacher [EMAIL PROTECTED]:
If a
2006/2/2, Graham Dumpleton [EMAIL PROTECTED]:
Nicolas Lehuen wrote ..
OK, I've reverted my changes. I left python22.py in place, because I
still hope to be able to use it with PythonImport. The only problem is
being able to define it in the unit tests.
I plead dumb. What is the connection
On Jan 29, 2006, at 6:05 PM, ben syverson wrote:
sigh
Any ideas?
Considering that MP2/libapreq2 - AFAIK - are designed for httpd2.0 --
does this compile on your system?
httpd2.0, libapreq2, apr and mod_perl2
On Feb 1, 2006, at 12:35 AM, Jonathan Vanasco wrote:
Considering that MP2/libapreq2 - AFAIK - are designed for httpd2.0
-- does this compile on your system?
httpd2.0, libapreq2, apr and mod_perl2
Yeah, sorry -- I should have posted a followup. This was the problem!
Thanks,
- ben
Hello All,
I recently upgraded to the following (on a rhel3 box mason2.2):
Apache/2.0.55
mod_ssl/2.0.55
OpenSSL/0.9.8
mod_apreq2-20050712/2.1.3-dev
mod_perl/2.0.2
Perl/v5.8.0
Everything has been running fine on my linux dev box (using firefox 1.5).
However, when I switch over to my windows box
Hello All,
I recently upgraded to the following (on a rhel3 box mason2.2):
Apache/2.0.55
mod_ssl/2.0.55
OpenSSL/0.9.8
mod_apreq2-20050712/2.1.3-dev
mod_perl/2.0.2
Perl/v5.8.0
Everything has been running fine on my linux dev box (using firefox 1.5).
However, when I switch over to my windows box
Ruediger Pluem wrote:
On 01/31/2006 08:13 PM, Robby Pedrica wrote:
Hi Rudiger
Thanks for the reply:
a. any idea on when a fix will be available or whether there are patches
available for these items?
b. Yes, if you manually disable a member in balancer-manager, then it becomes
-Ursprüngliche Nachricht-
Von: Robby Pedrica
Hi Rudiger,
I've applied patches and recompiled. My results are as follows:
1. apache starts up with the member 'b' disabled now
2. if I shutdown the working member 'a' httpd, then manager shows the change
only when you try and
Plm wrote:
-Ursprngliche Nachricht-
Von: Robby Pedrica
Hi Rudiger,
I've applied patches and recompiled. My results are as follows:
1. apache starts up with the member 'b' disabled now
2. if I shutdown the working member 'a' httpd, then manager shows the change only
-Ursprüngliche Nachricht-
Von: Robby Pedrica
Thanks Rudiger,
I've set redirect and route values - not sure if these are correct:
Proxy balancer://mycluster
BalancerMember http://192.168.4.2:80 redirect=1
BalancerMember http://192.168.4.3:80 route=1 status=D
/Proxy
I'm
-Ursprüngliche Nachricht-
Von: Plüm, Rüdiger,
This only works with session stickyness. So
ProxyPass / balancer://mycluster stickysession=SESSION_COOKIE
Proxy balancer://mycluster BalancerMember
http://192.168.4.2:80 route=a redirect=b BalancerMember
http://192.168.4.3:80
I think we're in agreement that the current failover does
not work as it should with HTTP, and is quite
cumbersome to get it to work. :)
I hope to later on this week work on code that has
a real hot standby status, and avoids the requirement
for sticky sessions. It won't replace what's in
there
Why the breaks? Certainly we still want to continue the
for loop even if we see a valid setting. For example,
to set a worker in DISABLED and STOPPED mode.
On Jan 31, 2006, at 4:32 PM, Ruediger Pluem wrote:
Index: modules/proxy/mod_proxy.c
I mean, of course, having status be simple flags +d+s
for example, rather than the whole word. The code looks
to be designed with that in mind.
On Feb 1, 2006, at 8:57 AM, Jim Jagielski wrote:
Why the breaks? Certainly we still want to continue the
for loop even if we see a valid setting. For
-Ursprüngliche Nachricht-
Von: Jim Jagielski
I think we're in agreement that the current failover does
not work as it should with HTTP, and is quite
cumbersome to get it to work. :)
Apart from the fact that it currently does not even work without
patches :-).
So I am keen on
-Ursprüngliche Nachricht-
Von: Jim Jagielski
Why the breaks? Certainly we still want to continue the
for loop even if we see a valid setting. For example,
to set a worker in DISABLED and STOPPED mode.
1. Currently there is no clear separation letter.
2. Setting status=disabled
On Feb 1, 2006, at 9:02 AM, Plüm, Rüdiger, VIS wrote:
-Ursprüngliche Nachricht-
Von: Jim Jagielski
I think we're in agreement that the current failover does
not work as it should with HTTP, and is quite
cumbersome to get it to work. :)
Apart from the fact that it currently does
-Ursprüngliche Nachricht-
Von: Jim Jagielski
On Feb 1, 2006, at 9:02 AM, Plüm, Rüdiger, VIS wrote:
So I am keen on feedback by Robby. I hope to find time to
commit these
changes to the trunk tonight, so that it works at least in the
cumbersome way :-).
I will cut the
Hey!
January has brought in some great improvements to mod_smtpd. If you
compare the code now to the code six months ago you'll see that it is
very clean and very workable now, not that it wasn't before it's just
that now some distinctions have been made that makes thinking about
Plm wrote:
-Ursprngliche Nachricht-
Von: Jim Jagielski
On Feb 1, 2006, at 9:02 AM, Plm, Rdiger, VIS wrote:
So I am keen on feedback by Robby. I hope to find time to
commit these
changes to the trunk
On 2/1/06, Rian Hunter [EMAIL PROTECTED] wrote:
mod_smtpd needs a bouncing mechanism! I need some help with this
because I am not sure how to approach this. Should I implement an
entire SMTP client in mod_smtpd to bounce messages? Should I relegate
this responsibility to a sendmail command or
On Feb 1, 2006, at 7:51 PM, Garrett Rooney wrote:
Well, we already have a small SMTP implementation in the SMTP queue
module, that could be made somewhat more generic and used for this
sort of thing.
Yeah I was thinking about that! I'm just so fearful of code-bloat and
possibly maintaining
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2006-01-27 17:02:23 -0500 (Fri, 27 Jan 2006) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
Documentation status is
APACHE 2.3 STATUS: -*-text-*-
Last modified at [$Date: 2005-12-16 16:06:45 -0500 (Fri, 16 Dec 2005) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
Documentation status is maintained
41 matches
Mail list logo
