> From: Tim Moloney [mailto:email@example.com]
> Sent: 07 March 2002 18:01
> Greg Stein wrote:
> > On Wed, Mar 06, 2002 at 06:48:11PM -0500, Tim Moloney wrote:
> > I believe it is Apache itself.
> > In the past few days, Apache has been tweaking some very basic structures
> > [...]
> > Until then, I would suggest that you grab Apache from, say, Monday and see
> > if that will work for you.
> > [ and yah: it is entirely possible that we could be screwed: we can't back
> > up too far cuz we need some very recent mod_dav changes, yet the latest
> > isn't working or is incompatible with svn for some reason (e.g. the recent
> > changes to APR to deal with some symbol renames) ]
> >>As an aside, I had tried updating both Apache and Subversion because I
> >>was getting httpd processing that were maxing out the CPU and never
> >>completing the svn file transfer. I was hoping that the update would
> >>fix this problem not my situation worse. =(
> > Related to the changes I mentioned, some bugs crept in which caused infinite
> > loops in Apache. The Apache internals have been getting some excellent
> > cleaning, simplification, and correctness fixes, but at the same times, the
> > code is rather complicated. Bugs were added :-) They're getting cleaned up,
> > but a bit of patience with httpd is in order for the next few days...
> More information on this issue.
> Using Subversion revision 1436 and
> - httpd-2.0, apr, and apr-util from 2002-03-04 20:00
> Fixes the bad status line but has the infinite loop problem.
> - httpd-2.0, apr, and apr-util from 2002-03-01 20:00
> Fixes both the bad status line and the infinite loop problems.
> Hopefully the httpd developers on this list will find this useful.
I tried a few hours ago with httpd-2.0 HEAD and latest subversion
and checkout, update and commit work fine for me.
FYI, there were a few bugs fixed in the last 12 hours.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Mar 7 18:34:49 2002