Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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.20030109084211.01e86d88@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Thu, 09 Jan 2003 08:48:02 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Recent (1.3.18) Pipe Changes
Mime-Version:	1.0

Hi,

Am I to understand from the lack of any response to my and other people's 
reports of long delays in pipe access under Cygwin 1.3.18 when low-priority 
CPU demand is present that this behavior is not considered problematic, 
undesirable or unacceptable?

Is there any chance of getting better behavior short of providing the 
solution myself?

Randy 


--
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/

- Raw text -