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: <5.2.0.9.2.20030115084952.02c82e40@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Wed, 15 Jan 2003 08:54:16 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: possible cygwin bug: delays when using pipes In-Reply-To: <094e01c2bc92$dfdd61f0$a400a8c0@bluebox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Eugene, Cygwin 1.3.18 + Cygwin pipes + background, low-priority CPU load = Long delays in Cygwin pipe I/O Are you running SETI AT home? That seems to be the most popular. It runs at the lowest priority, but still produces this symptom. I've been ignored every time I pointed this out. I guess those of us who run Cygwin as well as background CPU-soaker apps will have to choose one or the other (or develop considerable patience while using Cygwin). Randall Schulz At 04:37 2003-01-15, Eugene Rosenzweig wrote: >Seemingly, whenever I use a pipe in bash the cygwin freezes for a long time. >For example: >'echo a | cat' takes about 10 seconds to execute, 'bash -l -i' takes about a >minute. > >I am not sure when the problem appeared. Might have been last cygwin dll >release but I am not sure. First time I noticed was running 'bash -l -i'. I >changed the cygwin.bat recently so for a while I thought it was my meddling >but as far as I can see that is not the case. Right now the cygwin is quite >unusable since any non-trivial command line takes a long time to execute. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/