From: Derek Pagel <Derek.Pagel@infor.com>
To: "Cygwin (cygwin@cygwin.com)" <cygwin@cygwin.com>
Subject: RE: Commands are hanging on Windows 2019
Date: Mon, 17 Oct 2022 20:23:00 +0000 [thread overview]
Message-ID: <CH2PR02MB60242814E319A313353CC379E5299@CH2PR02MB6024.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CA+kUOa=ZmysiwpMwGqLft+VW5-s8CYo8od7MBC85EM8+Lhwvgg@mail.gmail.com>
We haven't had any luck with finding the issue in the PATH.
However, we were able to replicate the following issue on Windows 2019; In the case of a sleep command hanging on version 3.3.6, running Procmon shows the command (C:\cygwin64\bin\sleep.exe 5) created with Process Create but there is no Process Start logged for the resulting PID. The first operation for the PID is a DeviceIoControl on sleep.exe. After that the logging looks normal for the PID (compared to a working sleep on v 3.3.4) except for some missing reads on Registry Keys. The 8th operation is a LoadImage for sleep.exe and then nothing more is logged for the PID. It seems to have lost its way at the very beginning of the process.
-----Original Message-----
From: Cygwin <cygwin-bounces+derek.pagel=infor.com@cygwin.com> On Behalf Of Adam Dinwoodie
Sent: Saturday, October 15, 2022 7:45 AM
To: Cygwin (cygwin@cygwin.com) <cygwin@cygwin.com>
Subject: Re: Commands are hanging on Windows 2019
Sent by an external sender. Please be cautious about clicking on links and opening attachments.
----------------------------------------------------------------------------------------------------------------
On Wed, 12 Oct 2022 at 16:13, Derek Pagel via Cygwin wrote:
>
> We're seeing a bunch of commands (mv, which, rm) that are hanging or take a long time to complete on Windows 2019. It does not happen consistently but intermittently about once a week. The issue doesn't happen when running the cmd on the cmd line but when the cmd is called from another program. We can't replicate the issue from the command line. Is anyone familiar with this issue?
This sounds like an issue with your PATH containing some directories (e.g. network shares) that are slow.
If that's not enough to point you in the right direction, can you provide the information requested at the below link, so we've something more to go on?
> Problem reports: https://cygwin.com/problems.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2022-10-17 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 15:12 Derek Pagel
2022-10-15 12:45 ` Adam Dinwoodie
2022-10-17 20:23 ` Derek Pagel [this message]
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=CH2PR02MB60242814E319A313353CC379E5299@CH2PR02MB6024.namprd02.prod.outlook.com \
--to=derek.pagel@infor.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).