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 Message-Id: <3.0.5.32.20031224181524.007c21c0@incoming.verizon.net> X-Sender: vze1u1tg AT incoming DOT verizon DOT net Date: Wed, 24 Dec 2003 18:15:24 -0500 To: cygwin AT cygwin DOT com From: "Pierre A. Humblet" Subject: Re: Please try the latest snapshot -- it is close to cygwin 1.5.6 In-Reply-To: <20031224165934.GA4585@redhat.com> References: <20031224152951 DOT GA34487383 AT hpn5170x> <20031223222816 DOT GA23935 AT redhat DOT com> <20031224152951 DOT GA34487383 AT hpn5170x> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:59 AM 12/24/2003 -0500, Christopher Faylor wrote: >On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote: >>On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote: >>> The subject says it all. >>> >>> I'm hoping to release cygwin 1.5.6 shortly after Christmas. >> >>On WinMe the queue runner forked by the exim daemon still occasionally >>produces a popup indicating an error in Cygwin1.dll > >"a popup indicating an error".......? > >Not too helpful. It has happened once more, but differently. ps shows the child as defunct. Sysinternals shows everything normal, pinfo exists in the child. There is no fork failure, in fact the one I mentioned earlier is the only one out of 17070 runs. This time when I killed the daemon (just to see), I got 330495 [main] exim 34658275 proc_subproc: couldn't get proc lock. Something is wrong. 330520 [main] exim 34658275 proc_subproc: couldn't get proc lock. Something is wrong Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/