>ls -al -- 1min 32sec
>
>find -- 4min 46sec
Probably security/anti-virus software, I had this problem for a long
time with Rapport until I'd stop it in taskmgr > services tho I
believe newer versions of Rapport improved this somewhat.
I doubt 1.5 minutes for a simple ls is just caused
On 2020-09-21 12:34, Kurt Carlson via Cygwin wrote:
> The attached source replicates the erratic qsort problem. This compiles
> both cygwin and RHEL. In the following, the first descending dpcsort has
> erroneous results:
>
> kc: uname -a
> CYGWIN_NT-10.0 kacds 3.1.7(0.340/5/3) 2020-08-22 17:48 x8
The attached source replicates the erratic qsort problem. This compiles
both cygwin and RHEL. In the following, the first descending dpcsort has
erroneous results:
kc: uname -a
CYGWIN_NT-10.0 kacds 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin
kc: cc c19.c -o c19
kc: ./c19
# consort qsort struct
On 2020-09-21 09:20, Ken Brown via Cygwin wrote:
> On 9/21/2020 10:53 AM, Praveen Kumar Chandrakar via Cygwin wrote:
>> Hello,
>>
>> We are experiencing some issues with the Cygwin commands (ie. from bash
>> -login) taking several minutes on three of our Windows 2016 servers.
>>
>> ls -al -- 1
The 1.x and 2.x versions of socat have now been separated into separate
packages for Cygwin.
socat 1.7.3.4-2 is now available. It's the same as the -1 package, but the
package hint now clarifies that it's the 1.x series.
socat2 2.0.0-0.1.b9 is now available. This is upstream version 2.0.0-b9.
so
On 9/21/2020 10:53 AM, Praveen Kumar Chandrakar via Cygwin wrote:
Hello,
We are experiencing some issues with the Cygwin commands (ie. from bash
-login) taking several minutes on three of our Windows 2016 servers.
ls -al -- 1min 32sec
find -- 4min 46sec
When you search for a specif
Hello,
We are experiencing some issues with the Cygwin commands (ie. from bash
-login) taking several minutes on three of our Windows 2016 servers.
ls -al -- 1min 32sec
find -- 4min 46sec
When you search for a specific file, such as ls -al ./ABC/XYZ.txt, it is
very quick.
We ran strac
On Sat, Sep 19, 2020 at 1:37 AM Thomas Wolff wrote:
> > Cygwin can be expected to run on all modern, released versions of Windows,
> > from
> > Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all later versions of
> > Windows, except Windows S mode due to its limitations. The 32 bit version
Thanx all who helped out with this
The reason to why we thought it worked in mysterious ways was a coincidence of
how it worked in cygwin shell (due to /etc/profile etc) and that we didn't
realize/investigate that the variable was NULL at this moment and that we fell
back to our own default-val
I have uploaded xterm-360.
Changes:
Update to upstream xterm 360.
Change runtime configuration to use xterm default DEC conformance level
(VT420) again, which now also supports graphics output.
Thomas
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwi
10 matches
Mail list logo