From: Chris Roehrig <croehrig@house.org>
To: cygwin@cygwin.com
Subject: Re: scp and ssh 'cat' stalls at 64k bytes
Date: Fri, 23 Jun 2023 18:59:04 -0700 [thread overview]
Message-ID: <b6e0a7b2-ba6d-35f9-04b5-ca2e9c00ffd9@house.org> (raw)
In-Reply-To: <59bddbbd-f934-8a23-3589-31e6db46639d@harkless.org>
On 2023-06-23 18:26, Dan Harkless via Cygwin wrote:
> On 6/23/2023 5:19 PM, Chris Roehrig via Cygwin wrote:
>> No worries; I imagine most people don't run sshd on cygwin.
>
> Hmm, I'd generally think the opposite, at least for users coming from
> more UNIXey / Linuxey backgrounds.
>
>> It looks to
>> me like the issue involves i/o between sshd and its sub-processes on
>> cygwin.
>>
>> Is anyone else able to successfully scp large files (>64KB) to cygwin as
>> the remote receiving end (with the latest cygwin)?
>
> Yes, with all Cygwin64 updates, I was able to scp a file of a few MB
> from Linux to Windows 10 with no issues. I also tried your 'cat'
> version, and that worked fine too.
>
> --
> Dan Harkless
> http://harkless.org/dan/
>
>
Thanks. There must be some issue with my setup. Very odd that 'pv'
works, but 'cat' does not. ldd shows they use identical libs. I guess
I'll start with the pv and cat source.
next prev parent reply other threads:[~2023-06-24 1:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 6:26 Chris Roehrig
2023-06-23 15:28 ` Brian Inglis
2023-06-23 19:41 ` Chris Roehrig
2023-06-23 23:07 ` Voris, Ben
[not found] ` <bced83bb-58c5-f2a8-bc03-578d6d9fd749@house.org>
[not found] ` <MW4PR84MB1684E6210C73D34ED2223319FE23A@MW4PR84MB1684.NAMPRD84.PROD.OUTLOOK.COM>
2023-06-24 0:19 ` Chris Roehrig
2023-06-24 1:26 ` Dan Harkless
2023-06-24 1:59 ` Chris Roehrig [this message]
2023-06-24 2:19 ` Dan Harkless
2023-06-24 5:35 ` Brian Inglis
2023-06-24 6:16 ` Dan Harkless
2023-06-24 7:47 ` Chris Roehrig
2023-06-24 7:12 ` Kevin Schnitzius
2023-06-24 8:45 ` Chris Roehrig
2023-07-05 19:20 ` Andrey Repin
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=b6e0a7b2-ba6d-35f9-04b5-ca2e9c00ffd9@house.org \
--to=croehrig@house.org \
--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).