This is the mail archive of the
mailing list for the Cygwin project.
Re: Piping on 64-bit Cygwin, STC found
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 21 Jun 2016 16:49:49 -0600
- Subject: Re: Piping on 64-bit Cygwin, STC found
- Authentication-results: sourceware.org; auth=none
- References: <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo dot ref at mail dot yahoo dot com> <1989991589 dot 1040675 dot 1465521483978 dot JavaMail dot yahoo at mail dot yahoo dot com> <6ecc2a84-449f-01f1-0ef7-440e97a9b850 at dronecode dot org dot uk> <1341561944 dot 11163115 dot 1466484828091 dot JavaMail dot yahoo at mail dot yahoo dot com> <7E3D11F0-CD6B-4AF4-991B-2C3AD0E08D07 at etr-usa dot com> <7365C9D7-91DF-491F-A979-A3B7291CFC99 at etr-usa dot com>
On Jun 21, 2016, at 4:40 PM, Warren Young <email@example.com> wrote:
> On Jun 21, 2016, at 3:57 PM, Warren Young <firstname.lastname@example.org> wrote:
>> Hereâs what a simple test case looks like:
>> $ dd if=/dev/urandom bs=4k count=4m |
>> gpg -c --force-mdc |
>> gpg -d > /dev/null
> I seem to have stumbled upon the actual STC.
Hereâs a screen shot of the error the second MinTTY gives on trying to exit:
The âman bashâ is the command I tried to give, and the âviâ command never executed, even after closing the first MinTTY window. The defunct âlessâ process is of course a child of the âmanâ process.
> Just increase those values...I used 64k and 64M
To be clear, I mean bs=64k count=64M, for 4 TiB of transfer. This ran for about half an hour before it started causing problems in the other MinTTY window here. I didnât write down the amount transferred at that time, unfortunately, though dd did report it. Almost certainly many times more than available RAM at any rate.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple