X-Spam-Check-By: sourceware.org Date: Mon, 13 Feb 2006 20:05:03 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1 Message-ID: <20060214010503.GE22242@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Mon, Feb 13, 2006 at 03:15:16PM -0700, Stewart Midwinter wrote: >From: Michael Brand 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? Yes. Upgrade from Cygwin 1.5.7. cgf -- 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/