From: <sten.kristian.ivarsson@gmail.com>
To: "'Ken Brown'" <kbrown@cornell.edu>
Cc: "'cygwin'" <cygwin@cygwin.com>
Subject: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple writers
Date: Wed, 1 Apr 2020 09:45:56 +0200 [thread overview]
Message-ID: <004601d607f9$94b6d6f0$be2484d0$@gmail.com> (raw)
In-Reply-To: <249be61e-da8a-7da1-ca67-0c4c6433a415@cornell.edu>
> On 3/31/2020 5:10 PM, sten.kristian.ivarsson@gmail.com wrote:
> >> On 3/28/2020 10:19 PM, Ken Brown via Cygwin wrote:
> >>> On 3/28/2020 11:43 AM, Ken Brown via Cygwin wrote:
> >>>> On 3/28/2020 8:10 AM, sten.kristian.ivarsson@gmail.com wrote:
> >>>>>> On 3/27/2020 10:53 AM, sten.kristian.ivarsson@gmail.com wrote:
> >>>>>>>> On 3/26/2020 7:19 PM, Ken Brown via Cygwin wrote:
> >>>>>>>>> On 3/26/2020 6:39 PM, Ken Brown via Cygwin wrote:
> >>>>>>>>>> On 3/26/2020 6:01 PM, sten.kristian.ivarsson@gmail.com wrote:
> >>>>>>>>>>> The ENIXIO occurs when parallel child-processes
> >>>>>>>>>>> simultaneously using O_NONBLOCK opening the descriptor.
[snip]
> Thanks. This runs fine with the current HEAD of topic/fifo.
We are very grateful for your efforts
The test-program works fine now with the latest commits in topic/fifo
There are some (possible other) issues that make our application doesn't
work as in Linux and we haven't had the time to dig into what the problems
are yet. A quick guess is that it is related to signals and possible related
to pselect, but we need to dig deeper into the logic to narrow down the
problems. Shall we "close" this issue even if we find out that there's still
problems with "named pipes" later on ?
The application server (the open source project) that we're trying to make
work in Windows can be found here https://bitbucket.org/casualcore/ (if
interested)
Once again, tnx Ken
Kristian
> Ken
next prev parent reply other threads:[~2020-04-01 7:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 11:11 sten.kristian.ivarsson
2020-03-25 12:44 ` Ken Brown
[not found] ` <18be01d602ab$0bbfca30$233f5e90$@gmail.com>
2020-03-26 14:06 ` Sv: " Ken Brown
2020-03-26 15:11 ` Ken Brown
2020-03-26 16:03 ` Norton Allen
2020-03-26 16:44 ` Ken Brown
2020-03-26 17:00 ` Norton Allen
2020-03-26 22:01 ` Sv: " sten.kristian.ivarsson
2020-03-26 22:39 ` Ken Brown
2020-03-26 23:19 ` Ken Brown
2020-03-27 13:10 ` Ken Brown
2020-03-27 14:53 ` Sv: " sten.kristian.ivarsson
2020-03-27 22:56 ` Ken Brown
2020-03-27 23:00 ` Ken Brown
2020-03-28 12:10 ` Sv: " sten.kristian.ivarsson
2020-03-28 15:43 ` Ken Brown
2020-03-29 2:19 ` Ken Brown
2020-03-30 17:44 ` Ken Brown
2020-03-31 21:10 ` Sv: " sten.kristian.ivarsson
2020-03-31 22:02 ` Ken Brown
2020-04-01 7:45 ` sten.kristian.ivarsson [this message]
2020-04-01 13:47 ` Sv: " Ken Brown
2020-04-01 8:52 ` sten.kristian.ivarsson
2020-04-01 16:15 ` Ken Brown
2020-04-01 17:14 ` Sv: " sten.kristian.ivarsson
2020-04-01 18:34 ` Ken Brown
2020-04-02 2:19 ` Ken Brown
2020-04-02 8:05 ` Sv: " sten.kristian.ivarsson
2020-04-02 12:47 ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple wri Gregery Barton
2020-04-02 18:21 ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple writers Ken Brown
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='004601d607f9$94b6d6f0$be2484d0$@gmail.com' \
--to=sten.kristian.ivarsson@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).