delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/03/25/10:20:09

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: <3E2D8043936AD611AF7D00508B5E9F4B3B6972@server3.mobilecom.com>
From: Cary Lewis <clewis AT mobilecom DOT com>
To: cygwin AT cygwin DOT com
Subject: Still looking for named pipe solution in cygwin
Date: Tue, 25 Mar 2003 10:19:25 -0500
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Mar 2003 15:25:13.0062 (UTC) FILETIME=[BAD18860:01C2F2E2]

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?

Any help would be appreciated.

NOTE: The pipes don't have to be named (I can handle that separately).

I would be open to the possibility of paying for such an enhancement. Please
send a quotation or proposal to me directly.

Thank you.


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019