Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 28 Nov 2002 10:13:59 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.3.16-1: Apache 1.3.24 not rotating/lockup problem Message-ID: <20021128101359.A23323@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3DE48797 DOT 5030004 AT atrove DOT com> <3DE4F8EE DOT 8E7CAE83 AT wapme-systems DOT de> <20021127185855 DOT O1398 AT cygbert DOT vinschen DOT de> <3DE59878 DOT A9D64756 AT wapme-systems DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DE59878.A9D64756@wapme-systems.de> User-Agent: Mutt/1.3.22.1i 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/