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: Date: Fri, 18 Mar 2005 09:36:45 -0700 From: Aaron Humphrey Reply-To: Aaron Humphrey To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.5.13 Vs. SETI AT Home on Windows XP In-Reply-To: <423A3D2B.1050807@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <423A3D2B DOT 1050807 AT acm DOT org> X-IsSubscribed: yes On Thu, 17 Mar 2005 18:30:03 -0800, David Rothenberger wrote: > On 3/17/2005 6:20 PM, John Whitlock wrote: > > I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C > > required). The cygwin shell was very slow to start, and executing > > "bash --login -i -x" showed that the time consuming programs were the same > > (id -un, uname -s, etc.). I also tried reinstalling base packages, a > > complete reinstall, etc. On a whim, I shut down SETI AT Home, and things were > > back to normal speed. To clarify: Is this the new "BOINC" client for SETI AT Home, or the older standalone version? I never had a speed problem with the older version, but I did with the BOINC one. > I believe you're experiencing the same problem discussed in > . > Summary: Try a snapshot. The latest snapshot does work to fix these problems for me. The problem I first saw, actually, was a severalfold(~50 times) slowdown in scp, which I got to go away by pausing the BOINC client(which is running both SETI AT Home and ClimatePrediction software). But yesterday I discovered that starting up Cygwin shells was also slow. The snapshot fixes the scp problem as well. --Aaron V. Humphrey -- 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/