Your guess is correct, I do run seti@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" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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@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/
