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.
my $TESTDIR = getcwd() . "\\test"; my $MVCMD = "mv test.txt " .
$TESTDIR . "\\test.txt"; my $RMCMD = "rm " . $TESTDIR .
"\\test.txt test2.txt";
Even using Strawberry Perl, "" in above lines cause error.
Oh, I see, when I copy-pasted the script into the thread, it added a few code
changes,
I ran your script twice, once in command prompt and once in mintty.
Both attempts finished without any problems.
Thanks for running the script and trying it. What OS and Cygwin version were
you using?
--
Problem reports: https://cygwin.com/problems.html
FAQ:
Windows 10 Professional (64 bit) 22H2 Version 10.0.19045.2130
Cygwin: CYGWIN_NT-10.0-19045 HP-Z230 3.3.6-341.x86_64 2022-09-05 11:15 UTC
x86_64 Cygwin
And you?
I've seen the issue on Windows Server 2012 R2 Version 6.3 (Build 9600) and
Windows Server 2019 Version 1809 (OS Build 17763.3532) with
We've been encountering Cygwin commands that are intermittently hanging on
Windows. We don't have any predictable way to reproduce it besides running
commands in a loop until we encounter a hang. So, we've created a script that
will loop and execute 5 different Cygwin commands (touch, cp, mv,
The script was written using Strawberry Perl with Cygwin in the %PATH%
variable. Then the script makes system calls using that Cygwin.
On Mon, 7 Nov 2022 22:06:46 +
Derek Pagel wrote:
> I've printed the script below for reference:
>
> use strict;
> use
We've had problems with slow Cygwin commands, so we were able to capture a
stack trace when the 'cp' program taking a long time to complete, and we
noticed in the stack trace that the last thing cygwin1.dll does is calls
assert. What might that suggest? And are there any situations that would
In the past we've noticed that Cygwin commands are intermittently slow and can
take about 42 seconds to complete on Windows. We then installed Cygserver to
try and avoid the slowness and it has worked for the most part. However, we do
still have instances where we've noticed the commands are
Stop using ` already. Or at the very least use it properly.
Either
icacls `cygpath -m interchange.20230418091901`
or
icacls "$(cygpath -m interchange.20230418091901)"
Not to mention, you don't need to cygpath the file in current directory.
Just
icacls "interchange.20230418091901.tmp"
should
Looks like the ACL has not been written, so the incoming ACEs are still being
looked up (and/or maybe inherited)?
Where was that file moved from and what were the files' permissions and ACLs
before and after?
Anyone know what execute permission *a* means? -rwxrwxrwa [above]
Could be long ACL lists with many unique ACEs that need looked up on AD, and/or
slow ADCs, and/or slow AV, and/or slow net:
for each file show the outputs of
$ ls -dl $f
$ getfacl $f
$ icacls "`cygpath -m $f`"
and also attach as text, the output from strace on the cp
I've been seeing an issue where Cygwin commands sometimes take a while to
complete, or they will not complete at all and will have to be manually killed
through task manager. I installed Cygserver and that helped to lessen the
number of times that the issue happens but it didn't get rid of it.
how big are these files and from where to where are you copying them ?
AV interference ?
The files being copied are not very big at all and they're just being copied
from one directory to another on the same server.
--
Problem reports: https://cygwin.com/problems.html
FAQ:
I have been able to replicate Cygwin commands hanging on a Windows 2019 server
by running a program that loops through cp, mv, chmod and rm 100 times every 15
mins. I'm also running each of those Cygwin commands through a Microsoft
utility that reports which specific Windows API a thread has
We are seeing more instances of application slowness due to Cygwin programs
like 'cp' and 'mv' being executed. The files being 'cp' or 'mv' are not very
big and they stay on the same server. We have installed Cygserver which has
improved things a little bit but there are still many cases of
I've been having intermittent slowness with Cygwin commands even after
installing Cygserver. It has helped reduce the frequency of occurrences of
slowness, but it hasn't gotten rid of them completely. I recently had a
'mv.exe' that was slow, so I ran a few commands to get some details on the
17 matches
Mail list logo
