On 2021-02-22 14:50, Hans-Bernhard Bröker wrote:
Am 22.02.2021 um 21:30 schrieb Brian Inglis:
I've often wondered if the heavy activity is due to Windows' defaults to
writing files with F+RX perms which triggers executable virus scans?
That could only be the case if Windows actually had an 'x
Am 22.02.2021 um 21:30 schrieb Brian Inglis:
I've often wondered if the heavy activity is due to Windows' defaults to
writing files with F+RX perms which triggers executable virus scans?
That could only be the case if Windows actually had an 'x' permission bit.
--
Problem reports: https:/
On 2021-02-22 13:12, Doug Henderson wrote:
On Sun, 21 Feb 2021 at 08:21, Satalink wrote:
I deal with a lot of very large files on a regular basis. I've noticed that
when I delve into these directories using in mintty and issue the command ls
-l (or ls -color=auto), a very large junk of memory
On Sun, 21 Feb 2021 at 08:21, Satalink via Cygwin wrote:
>
> I deal with a lot of very large files on a regular basis. I've noticed that
> when I delve into these directories using in mintty and issue the command ls
> -l (or ls -color=auto), a very large junk of memory is consumed. The
> memor
On 2021-02-21 08:18, Satalink via Cygwin wrote:
I deal with a lot of very large files on a regular basis. I've noticed that
when I delve into these directories using in mintty and issue the command ls
-l (or ls -color=auto), a very large junk of memory is consumed. The
memory leak seems to be
I deal with a lot of very large files on a regular basis. I've noticed that
when I delve into these directories using in mintty and issue the command ls
-l (or ls -color=auto), a very large junk of memory is consumed. The
memory leak seems to be proportionate to the number and size of files wit
6 matches
Mail list logo
