X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=X5+lggZVZN1SM8aX8DKkYBk5uEamD2lLPZl8mwwEJVc=; b=FRG+Ru+w6z4gr+NaeDo5NwdFjL3FDFJUD1YyZT0mf666EYvDkMCJ2HLmNlNbzw1K5O W8PCpEuWcGx/haB6MZZvq2aGs05vG42ZDcMlupjuNnOxY82KM5jxvWN0U8Xuu3DBdx8k Aj0ScwKIH8Zwz5/Ub+3sjzTWKxSVamlEHzYyK/2eRKw717mn+1w+mvxfOLJQZZS2h3wA 6Qowqz9OKh6sZeYwoifiqIiAhivRdLGufWJOX3n4WlhvXqXNhj2NfmmhISAasznWJux8 BHG2yOmnitIGOi8gaD5sz1d1ELB22cXlONnt9CwAed05UrNAnMCPIocOWPbiKC+dzhjX hCVw== MIME-Version: 1.0 X-Received: by 10.50.53.161 with SMTP id c1mr10920165igp.95.1358846558983; Tue, 22 Jan 2013 01:22:38 -0800 (PST) In-Reply-To: References: Date: Tue, 22 Jan 2013 01:22:38 -0800 Message-ID: Subject: Re: BUG: FIFO (named pipe) is broken on Cygwin From: Greg Turner To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQla1BJAA3m8qgEXkfCBXN48inpus0V1PvNfI+UGYPxdSwVk5arB8lrrMyDp7GSjEW944etp Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Jan 21, 2013 at 7:38 PM, Zach Saw wrote: > > According to POSIX, FIFO allows multiple readers / writers. However, it > appears > that Cygwin's implementation only allows for multiple readers and single > writer. That's a known issue -- ostensibly, one not aggressively being worked on by anyone. I've tinkered with the code and discovered, unsurprisingly, that it's nontrivial to fix. It's somewhere on my todo list and presumably others', so if you can hang tight for a year or three, it may well get resolved. Otherwise, I'm afraid it's probably one of those tough-cookies-send-patches type situations. -gmt -- 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