From: Jeremy Drake <cygwin@jdrake.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: pipe hang issue when running as SYSTEM
Date: Thu, 24 Mar 2022 20:42:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.BSO.2.21.2203242039010.56460@resin.csoft.net> (raw)
In-Reply-To: <20220322221756.2b7e80ec0a51e7ebd9df5a53@nifty.ne.jp>
On Tue, 22 Mar 2022, Takashi Yano wrote:
> > Thanks for the report. This is expected problem as mentioned
> > in b531d6b commit message. However, I could not imagin the
> > situation that the service has multiple writer for the pipe
> > and one of them is a non-cygwin app.
> >
> > Question is: Does the docker invoke the command using SYSTEM
> > account? Or is the processes in docker determined as running
> > as a service?
>
> I confirmed the processes in Windows docker are running as
> well_known_service_sid. Let me consider a while.
>
Just got another report to MSYS2 of this behavior, this time from a Gitlab
CI runner that is running as a service and trying to pipe output from
Microsoft cl.exe while running configure. This user reports that 3.3.4
with your "[PATCH v2] Cygwin: pipe: Avoid deadlock for non-cygwin writer."
applied to it does not solve the problem.
https://github.com/msys2/MSYS2-packages/issues/2893
next prev parent reply other threads:[~2022-03-25 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:45 Jeremy Drake
2022-03-22 10:18 ` Takashi Yano
2022-03-22 13:17 ` Takashi Yano
2022-03-25 3:42 ` Jeremy Drake [this message]
2022-03-25 5:42 ` Takashi Yano
2022-03-25 7:09 ` Jeremy Drake
2022-03-25 11:11 ` Takashi Yano
2022-03-25 17:01 ` Jeremy Drake
2022-03-29 9:11 ` Takashi Yano
2022-03-25 7:48 ` Roumen Petrov
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=alpine.BSO.2.21.2203242039010.56460@resin.csoft.net \
--to=cygwin@jdrake.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).