> Elfyn McBratney wrote:
> >
> > > > Yup. It's been running now for over six hours.
> > >
> > > ok, could you load it a bit with apache's 'ab' tool?! and see if it
> > > complains with too many failing requests?
> > >
> > > I'll check this afternoon the new cygwin snapshot.
> > >
> > > Stipe
> >
>
Elfyn McBratney wrote:
>
> > > Yup. It's been running now for over six hours.
> >
> > ok, could you load it a bit with apache's 'ab' tool?! and see if it
> > complains with too many failing requests?
> >
> > I'll check this afternoon the new cygwin snapshot.
> >
> > Stipe
>
> I've attached about
> > Yup. It's been running now for over six hours.
>
> ok, could you load it a bit with apache's 'ab' tool?! and see if it
> complains with too many failing requests?
>
> I'll check this afternoon the new cygwin snapshot.
>
> Stipe
I've attached about 5 tests with loads of requests, no rhyme in
> Yup. It's been running now for over six hours.
ok, could you load it a bit with apache's 'ab' tool?! and see if it
complains with too many failing requests?
I'll check this afternoon the new cygwin snapshot.
Stipe
[EMAIL PROTECTED]
-
> Elfyn McBratney wrote:
> >
> > Just an update: Apache has been running for over three hours now :-)
It's
> > looking very good that this bug has well and truly died! ::-)
>
> so you used the Feb 20, cygwin 1.3.21 snapshot for this?!
>
> Stipe
Yup. It's been running now for over six hours.
Elfyn McBratney wrote:
>
> Just an update: Apache has been running for over three hours now :-) It's
> looking very good that this bug has well and truly died! ::-)
so you used the Feb 20, cygwin 1.3.21 snapshot for this?!
Stipe
[EMAIL PROTECTED]
> > Dylan Cuthbert wrote:
> > >
> > > Any more information on this problem? Anyone solved it?
> >
> > unfortunatly no. I guessed the latest cygwin 1.3.20-x, which included
> > some TCP connection related fixes would be the cure, but it didn't.
> >
> > > server-status makes it obvious what's being
> Dylan Cuthbert wrote:
> >
> > Any more information on this problem? Anyone solved it?
>
> unfortunatly no. I guessed the latest cygwin 1.3.20-x, which included
> some TCP connection related fixes would be the cure, but it didn't.
>
> > server-status makes it obvious what's being said in this thr
Dylan Cuthbert wrote:
>
> Any more information on this problem? Anyone solved it?
unfortunatly no. I guessed the latest cygwin 1.3.20-x, which included
some TCP connection related fixes would be the cure, but it didn't.
> server-status makes it obvious what's being said in this thread - ie. the
Any more information on this problem? Anyone solved it?
server-status makes it obvious what's being said in this thread - ie. the
children forked by apache aren't allowing themselves to be re-used on a
different connection properly, hence they all eventually lock up (once
KeepAlive times out) and
On Thu, Nov 28, 2002 at 05:15:52AM +0100, Stipe Tolj wrote:
> Corinna Vinschen schrieb:
> >
> > On Wed, Nov 27, 2002 at 05:55:10PM +0100, Stipe Tolj wrote:
> > > > I guess the main apache process that is suppose to arbitrate the
> > > > requests is not working properly with cygwin 1.3.16-1
> > > >
Corinna Vinschen schrieb:
>
> On Wed, Nov 27, 2002 at 05:55:10PM +0100, Stipe Tolj wrote:
> > > I guess the main apache process that is suppose to arbitrate the
> > > requests is not working properly with cygwin 1.3.16-1
> > >
> > > Has anyone else seen similar problems with apache?
> > > Has anyt
On Wed, Nov 27, 2002 at 05:55:10PM +0100, Stipe Tolj wrote:
> > I guess the main apache process that is suppose to arbitrate the
> > requests is not working properly with cygwin 1.3.16-1
> >
> > Has anyone else seen similar problems with apache?
> > Has anything changed in cygwin that would cause
Hi Paul,
first thanks for all the debugging information.
> I've just updated my copy of cygwin to 1.3.16-1 and have found
> that apache does not rotate through the running processes anymore
> it just serves from the one process.
> This can results in "page not found errors"
>
> The version of cy
Hi,
I've just updated my copy of cygwin to 1.3.16-1 and have found
that apache does not rotate through the running processes anymore
it just serves from the one process.
This can results in "page not found errors"
The version of cygwin I had before was 1.3.12-2. Apache worked fine
and rotated thro
15 matches
Mail list logo
