X-Spam-Check-By: sourceware.org
Message-ID: <d4c0d4800602140904r1ce8afa9l51653af196d8adee@mail.gmail.com>
Date: Tue, 14 Feb 2006 10:04:07 -0700
From: Stewart Midwinter <stewart DOT midwinter AT gmail DOT com>
To: Michael Brand <cygwin AT brand DOT scso DOT com>
Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1
Cc: cygwin AT cygwin DOT com
In-Reply-To: <43F174FF.1040102@brand.scso.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <d4c0d4800602131415w1303dcct74981a739f4ebdbc AT mail DOT gmail DOT com> 	 <43F174FF DOT 1040102 AT brand DOT scso DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k1EH4Hcj020727

fyi..

---------- Forwarded message ----------
From: Michael Brand <cygwin AT brand DOT scso DOT com>
Date: Feb 13, 2006 11:13 PM
Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1
To: Stewart Midwinter <stewart DOT midwinter AT gmail DOT com>
Cc: cygwin AT cygwin DOT com


 Nope, I never found a good solution, and suspect that a good solution
here requires patching some Cygwin internals, but here are three
workarounds we used back then:

 1. Disable one CPU.
 2. Use watchdog processes that will kickstart things if they get stuck.
 3. Switch to *much* older Cygwin versions, which seem to be free of
this problem.

 I am still hoping for a Cygwin version that fixes this, but I guess
that as long as there are so few people who, like me, use Cygwin as a
mass-processing infrastructure, there is little chance of this problem
getting to the top of the list of priorities.

 Cheers,
 M.


 Stewart Midwinter wrote:

 From: Michael Brand <cygwin <at> brand.scso.com>



 I disabled one of the CPUs on my dual-CPU Xeon, and everything started working

 well, so I guess this is a dual-cpu problem.



 I tried running my scripts on several dual-CPU Xeons (different
computer models, but all of them HPs), ... snip ...
it generally crashes an hour or two later, at the most.

 Joining the party a *little* late here ... :-)

I too have a dual-CPU Xeon made by HP and it too has a problem with a
tcsh script hanging when it runs for a long time (it's a polling
script). We suspect that it might have to do with forking, but are
unable to test that theory at this time.

Apart from disabling the 2nd CPU (which kind of defeats the purpose of
having such a machine!), did you ever find any other solution?

thanks
Stewart



--
Stewart Midwinter
stewart AT midwinter DOT ca
stewart DOT midwinter AT gmail DOT com
Skype, GoogleTalk, iChatAV, MSN, Yahoo: midtoad
AIM:midtoad1






--
Stewart Midwinter
stewart AT midwinter DOT ca
stewart DOT midwinter AT gmail DOT com
Skype, GoogleTalk, iChatAV, MSN, Yahoo: midtoad
AIM:midtoad1

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