Mail Archives: cygwin/2002/11/28/04:14:20
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
> > > >
> > > > Has anyone else seen similar problems with apache?
> > > > Has anything changed in cygwin that would cause such behavior?
> > >
> > > That exactly the question I'd like to hear from the core Cygwin
> > > people. Corinna, may you pick this issue up?!
> >
> > Sure, if you post a *small* testcase to the ML which points to a problem
> > in Cygwin. Other than that you should probably debug apache first.
>
> it seems *very* obious that it's a cygwin internal problem, since
> *all* apache versions worked correctly up to cygwin 1.3.10-2 and then
> the same behaviour, locking of httpd processes began.
Cool. I guess apache rans fine with b20.
Guesswork isn't really helpful. Sure there are errors in Cygwin as they
are in apache as in any other big software project. Coincidentally other
applications might run better since 1.3.10.
You know how that works, don't you? You'll debug apache. You'll find a
problem. You could find a workaround in apache by creating a Cygwin
specific patch which also helps people running older versions of Cygwin.
And/or you could create a small testcase which demonstrates the problem
in Cygwin so that we have a chance to either fix it or demonstrate that
it's correct behaviour.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT cygwin DOT com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -