Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: <42757A42.2B4DA572@dessent.net>
Date: Sun, 01 May 2005 17:54:26 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: "read" bug in Cygwin 1.5.16?
References: <20050501235613 DOT 71599 DOT qmail AT web30205 DOT mail DOT mud DOT yahoo DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com


Christopher Faylor wrote:

> There was a problem with setting VMIN == VTIME == 0 on ttys/ptys.  I've
> just checked in a fix.  It will be in today's snapshot, when it shows
> up: http://cygwin.com/snapshots/ .

Peter Farley wrote:

>     kbattr.c_cc[VMIN] = 0;
>     kbattr.c_cc[VTIME] = 0;

If you're always using select() to read, you could set VMIN = 1 as a
workaround if you need to support versions of Cygwin prior to the above
fix.

Brian

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