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: <0a3901c2bd28$e0cf2ad0$a400a8c0@bluebox> From: "Eugene Rosenzweig" To: References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030115084952 DOT 02c82e40 AT pop3 DOT cris DOT com> Subject: Re: possible cygwin bug: delays when using pipes Date: Thu, 16 Jan 2003 17:31:14 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 16 Jan 2003 06:31:03.0160 (UTC) FILETIME=[D77F9780:01C2BD28] Your guess is correct, I do run seti AT home in the background and stopping it gets rid of the problem. Very unfortunate situation since this makes cygwin virtually unusable in certain software configurations. ----- Original Message ----- From: "Randall R Schulz" To: Sent: Thursday, January 16, 2003 3:54 AM Subject: Re: possible cygwin bug: delays when using pipes > 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 > -- 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/