From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin Rsync x32 issue
Date: Tue, 16 Feb 2021 07:30:06 -0500 [thread overview]
Message-ID: <5e1e27d5-e4fc-f174-4a14-c7f8505dce0b@cornell.edu> (raw)
In-Reply-To: <9dcf94bb-6231-1785-7bf9-0aca60133004@cornell.edu>
On 2/15/2021 6:18 PM, Ken Brown via Cygwin wrote:
> On 2/14/2021 9:48 PM, Jim Brain wrote:
>> On 2/14/2021 8:21 PM, Ken Brown via Cygwin wrote:
>>>
>>>
>>> strace -o rsync.strace rsync...
>>>
>>> Then post rsync.strace somewhere where people can look at it.
>>
>> https://www.dropbox.com/s/v1n9i77jhq3b3zh/rsync.strace?dl=0
>
> Thanks. For the sake of comparison, could you also post the strace output from
> a successful (64-bit) run? I saw a suspicious CreateProcess failure, but I'd
> like to be sure it doesn't occur in the successful run also.
I just took a closer look at the CreateProcess failure and saw that it was
trying to start 64-bit ssh. It looks like your problem is that you forgot to
install openssh in your 32-bit Cygwin installation.
Ken
next prev parent reply other threads:[~2021-02-16 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 4:33 Jim Brain
2021-02-14 5:39 ` Brian Inglis
2021-02-14 5:55 ` Jim Brain
2021-02-15 0:01 ` Ken Brown
2021-02-15 2:04 ` Jim Brain
2021-02-15 2:21 ` Ken Brown
2021-02-15 2:48 ` Jim Brain
2021-02-15 23:18 ` Ken Brown
2021-02-16 1:57 ` Jim Brain
2021-02-16 2:11 ` Jim Brain
2021-02-16 12:30 ` Ken Brown [this message]
2021-02-16 23:32 ` Jim Brain
2021-02-18 6:35 ` Andrey Repin
2021-02-18 21:50 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 22:49 Jim Brain
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=5e1e27d5-e4fc-f174-4a14-c7f8505dce0b@cornell.edu \
--to=kbrown@cornell.edu \
--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).