X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=2.6 required=5.0	tests=AWL,BAYES_20,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DONT_USE_RAW_EMAIL_IN_BODY,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_CG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20100817215134.GB16955@ednor.casa.cgf.cx>
References: <AANLkTimUy1qmQtS1Ld+YarZC_RySN5xTkHnZAYhJO6MT AT mail DOT gmail DOT com> <20100817215134 DOT GB16955 AT ednor DOT casa DOT cgf DOT cx>
From: Etienne Carriere <etienne DOT carriere AT gmail DOT com>
Date: Thu, 19 Aug 2010 07:42:32 +0200
Message-ID: <AANLkTin4WwPBSE7fvcYbrosWTYjXo97SUMaA-KEzBCF4@mail.gmail.com>
Subject: Re: Curious behavior of fifo on cygwin 1.7.5
To: cygwin AT cygwin DOT com
Content-Type: multipart/mixed; boundary=0015175caae4373ce2048e26a7f3
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

--0015175caae4373ce2048e26a7f3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

Thanks for your answer . In order to have the standard behavior, I
open/close the filedescriptor before/after each read as in the
attached code and it seems to work

Regards,

Etienne Carri=E8re

2010/8/17 Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>:
> On Tue, Aug 17, 2010 at 07:25:25PM +0200, Etienne Carriere wrote:
>>Hello,
>>
>>I currently have a curious behavior with fifo (named pipes on cygwin
>>1.7.5) . I first discovered when using Nagios on cygwin but I achieved
>>to simplify it . The scenario is the following :
>
> If you search the mailing list archives, you'll see a fair number of
> problems with fifos and you'll also see my acknowledgement of same.
>
> fifos in Cygwin are a work-in-progress and are not guaranteed to work
> like their linux counterparts.
>
> I do poke at them from time to time but, for now, you'll have to
> consider them to be "as-is". =A0That means that some things are broken.
>
> cgf
>
> --
> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html
> FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/
> Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html
> Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple
>
>

--0015175caae4373ce2048e26a7f3
Content-Type: application/octet-stream; name="consume_fifo_workaround.c"
Content-Disposition: attachment; filename="consume_fifo_workaround.c"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_gd16phg00

I2luY2x1ZGUgPHN0ZGlvLmg+CiNpbmNsdWRlIDxzdGRsaWIuaD4KCmludCBj
b25zdW1lKHZvaWQpewoJRklMRSAqZnA7CgljaGFyIGlucHV0X2J1ZmZlclsx
MDAwXTsKCXdoaWxlKDEpewogICAgICAgIAlmcD1mb3BlbigiL3RtcC9maWZv
LmNtZCIsInIiKTsKCQlpZiAoZmdldHMoaW5wdXRfYnVmZmVyLChpbnQpKHNp
emVvZihpbnB1dF9idWZmZXIpLTEpLGZwKSE9TlVMTCl7CgkJCXNsZWVwKDEp
OwoJCQlwcmludGYoIlJFQUQ6ICclcydcbiIsaW5wdXRfYnVmZmVyKTsKCQl9
CiAgICAgICAgCWZjbG9zZShmcCk7Cgl9Cn0KCgppbnQgbWFpbiAoY2hhciAq
KmFyZ3YpewoJY29uc3VtZSgpOwp9Cg==


--0015175caae4373ce2048e26a7f3
Content-Type: text/plain; charset=us-ascii

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
--0015175caae4373ce2048e26a7f3--