This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Still looking for named pipe solution in cygwin


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]