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:	<4274D150.9080309@1979.usna.com>
Date:	Sun, 01 May 2005 08:53:36 -0400
From:	"Jerry D. Hedden" <jdhedden AT 1979 DOT usna DOT com>
User-Agent:	Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin-1.5.16-1: FIFOs broken

 >>>> However, that said, the above WJFFM.  In fact, it works more like
 >>>> linux in 1.5.16 than it does on 1.5.15, i.e., the cat command exits
 >>>> after printing "YOUR TEXT HERE" whereas it continues to block in
 >>>> 1.5.15.

 >> I tried the 4/30 snapshot of cygwin1.dll.  It exhibited the behavior
 >> you mentioned with the 'cat' exiting after it reads text.  However,
 >> this is a bad thing.  It means that the FIFO is being set EOF after
 >> there is no more data.  I tried my client-server app with the
 >> snapshot cygwin1.dll, and it failed because of this.
 >>
 >> It seems to me that the behavior of FIFOs under 1.5.15 was correct,
 >> and that under both 1.5.16 and the snapshot, FIFOs are now broken.

 > FWIW, I just tested your example under Solaris 8 and it works just
 > like Christopher describes.

Okay.  I have seen the error of my ways.  I'm going to rewrite my app to 
use UPD instead.

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

- Raw text -