Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <002501c2a142$1d17d5d0$5388883e@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Cary Lewis" <clewis AT mobilecom DOT com>, <cygwin AT cygwin DOT com>
References: <3E2D8043936AD611AF7D00508B5E9F4B28D4FA AT server3 DOT mobilecom DOT com>
Subject: Re: Looking for named pipe solution in cygwin
Date: Wed, 11 Dec 2002 18:21:23 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Cary Lewis <clewis AT mobilecom DOT com> wrote:

> I have an existing unix application that makes extensive use of named
> pipes:
>
> mknod pipe p
>
> and shell scripts and 'C' programs that read and write pipes.
> Messages must be read in order that they were written to pipe. As
> well many processes must be able to write to a pipe and not have
> their messages intermingled.
>
> Does anyone have a solution for this for cygwin?

Unix named pipes / FIFOs haven't been implemented for Cygwin. No one has got
around to it.

> Any help would be appreciated.
>
> NOTE: The pipes don't have to be named (I can handle that separately).

I don't believe there is any way to have multiple processes write to an
anonymous pipe.

> BTW the other posix emulators like Interix now SFU and MKS support
> these kinds of pipes, so it should be easy right?

As I said above, no one has gotten round to it.

> How does the /dev/ttyX file work.

Cygwin notices access to certain 'files' and does clever things with them.
For more detail: "Use the source, Luke!".

> In a bash window I can echo hello
>> /dev/tty or /dev/ttyM, where M is my tty, and I get hello on my
>> screen, but
> I can't echo hello >/dev/ttyN where N is another terminal, I get
> /dev/ttyN invalid argument.

Strange - works for me.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/