From: Dan Kegel <dank@kegel.com>
To: cygwin@cygwin.com
Subject: Re: Problem with named pipes
Date: Tue, 11 Dec 2018 14:57:00 -0000 [thread overview]
Message-ID: <CAPF-yOaQx5ZTDHnVecyEOCtZp4sR9n3VgFU8Y0HTnrGKqfRz0g@mail.gmail.com> (raw)
In-Reply-To: <d5ff7ebb-6fc2-5ce6-e38b-6e6c9113d102@cornell.edu>
On Tue, Dec 11, 2018 at 6:42 AM Ken Brown <kbrown@cornell.edu> wrote:
> > Very tricky problem. The FIFO code falls over its own feet trying to
> > handle more than one writer (exec 7> is the first, echo blah is the
> > second writer). Sigh. This code needs a thorough rewrite...
>
> I'm coming back to this thread after three years. I'd be willing to put in some
> time working on this, if you could point me in the right direction.
I'm no cygwin developer, but:
It might be worth spending a little quality time with
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=tree;f=winsup/testsuite/winsup.api/ltp
to update it to handle the case you're interested in first...?
https://github.com/linux-test-project/ltp has come a long, long ways
since cygwin's copy was made. It might be interesting to just
try building and running LTP on cygwin and see how far it is from
working at all... I would not be surprised if cygwin's copy is highly customized
to avoid spikes.
- Dan
--
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
next prev parent reply other threads:[~2018-12-11 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 21:39 Ken Brown
2016-01-08 20:58 ` Corinna Vinschen
2018-12-11 14:42 ` Ken Brown
2018-12-11 14:57 ` Dan Kegel [this message]
2018-12-11 19:40 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPF-yOaQx5ZTDHnVecyEOCtZp4sR9n3VgFU8Y0HTnrGKqfRz0g@mail.gmail.com \
--to=dank@kegel.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).