From: Andrey Repin <anrdaemon@yandex.ru>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: cygwin Rsync x32 issue
Date: Thu, 18 Feb 2021 09:35:38 +0300 [thread overview]
Message-ID: <1397517063.20210218093538@yandex.ru> (raw)
In-Reply-To: <dda0c248-643b-ed5f-6194-0cd322bce316@cornell.edu>
Greetings, Ken Brown!
I have a problem with rsync that sounds very similar to this one.
Every. Damn. Time. I attempt to upload files to a server, first attempt always
fail approx halfway through. No matter if I upload no files or a hundred of
them.
First attempt always fail. Then - immediately - I try again exactly same
command and - lo and behold - it runs down to completion.
The error message is
sending incremental file list
…
attempt to hack rsync failed.
rsync error: protocol incompatibility (code 2) at receiver.c(582) [receiver=3.1.0]
Strace http://www.rootdir.org/upload/Bugs/rsync.Cygwin-2021-02-18/rsync-20210218-085750.61.trace.xz
--
With best regards,
Andrey Repin
Thursday, February 18, 2021 1:00:56
Sorry for my terrible english...
next prev parent reply other threads:[~2021-02-18 6:50 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
2021-02-16 23:32 ` Jim Brain
2021-02-18 6:35 ` Andrey Repin [this message]
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=1397517063.20210218093538@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).