X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Subject: RE: Call for testing Cygwin snapshot
Date: Tue, 25 Apr 2006 15:37:46 -0400
Message-ID: <B6C33E7A8278A0408B707C9B491720D4045315@STEELPO.steeleye.com>
From: "Ernie Coskrey" <Ernie.Coskrey@steeleye.com>
To: <cygwin@cygwin.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k3PJbtkJ025966

> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Jerry D. Hedden
> Sent: Tuesday, April 25, 2006 9:27 AM
> To: cygwin@cygwin.com
> Subject: RE: Call for testing Cygwin snapshot
> 
> 
> Jerry D. Hedden wrote:
> >I have a cron job (a bash script)
> >that runs every 6 minutes, polling and downloading info off the web. 
> >
> >The problem is the script hangs at various places and the stuck
> >processes keep building up.
> >
> >Further, I have to kill these processes using the task monitor:  kill
> >reports 'No such process'.
> 
> Christopher Faylor replied:
> > As mentioned above, a test case showing the problem sure 
> would be nifty.
> 
> I agree and would have provided one if I could.  However, I 
> have no idea
> what is causing this, nor how to write a test case for it.
> 
> As I said, it's a cron job running a bash script - nothing fancy.  The
> hang does not happen on every invokation of the script, but it does
> occur frequently.  Where in the script it gets stuck seems to be
> random: wget, mkdir, mv, date, diff, etc..
> 
> > Also, knowing the first snapshot which shows the problem 
> would be helpful.
> 
> As I said, these sort of problems started after the 
> 2006-03-09 snapshot.
>  I double checked, and the problem does occur with the 2006-03-13
> snapshot.
> 
> 

I wonder if this might be related to the following:

http://cygwin.com/ml/cygwin/2006-02/msg01062.html

The fix suggested in the original message - http://www.cygwin.com/ml/cygwin-patches/2003-q2/msg00004.html - might help.

Ernie Coskrey
SteelEye Technology, Inc.

--
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/


