From: Chris Roehrig <croehrig@house.org>
To: Ken Brown via Cygwin <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.2.6c1f49f83fde (TEST)
Date: Sat, 16 Oct 2021 10:42:57 -0700 [thread overview]
Message-ID: <E0CDBC6F-4F84-495A-BCA4-A7B049BA8928@house.org> (raw)
In-Reply-To: <13495a25-2ae9-69f9-cd8e-6e6ff0e1af9e@cornell.edu>
On Mon Sep 27 2021, at 7:26 AM, Ken Brown via Cygwin <cygwin@cygwin.com> wrote:
> On 9/26/2021 8:57 PM, Chris Roehrig wrote:
>> I have installed this (completely this time) and have encountered no issues with it. I'm getting full gigabit speeds with my rsync transfers. Looks great!
>
> Thanks for testing.
I've encountered a crash that might be related. I had previously been having occasional crashes/hangs of cat.exe over the years, but this is the first time I've ever gotten an error message:
cygwin error: 0 [fifo_reader] cat 11398 C:\cygwin\bin\cat.exe: *** fatal error - Can't add a client handler, Win32 error 123
cat here is reading from a fifo created with mkfifo.
I've only encountered it once (out of daily runs over the last couple weeks) and don't know how to replicate it. Possibly a race? Looks like my script has tried to mitigate this with a sleep 1 between the mkfifo and the fork: cat < $fifo &
I only encounter this issue on Cygwin (it has always worked fine without the sleep on Linux and MacOS).
-- Chris
next prev parent reply other threads:[~2021-10-16 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 1:53 Ken Brown via Cygwin-announce
2021-09-27 0:57 ` Chris Roehrig
2021-09-27 14:26 ` Ken Brown
2021-10-16 17:42 ` Chris Roehrig [this message]
2021-10-17 16:19 ` Ken Brown
2021-10-17 20:52 ` cat fifo hang [Re: [ANNOUNCEMENT] cygwin 3.3.0-0.2.6c1f49f83fde (TEST)] Chris Roehrig
2021-10-17 22:15 ` Ken Brown
2021-10-24 21:51 ` 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=E0CDBC6F-4F84-495A-BCA4-A7B049BA8928@house.org \
--to=croehrig@house.org \
--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).