X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 17 Aug 2010 17:51:34 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Curious behavior of fifo on cygwin 1.7.5 Message-ID: <20100817215134.GB16955@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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". That means that some things are broken. cgf -- 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