From: Jim Brain <brain@jbrain.com>
To: cygwin@cygwin.com
Subject: cygwin Rsync x32 issue
Date: Sat, 13 Feb 2021 22:33:59 -0600 [thread overview]
Message-ID: <cad3a794-d335-0522-689b-d8a4b826a723@jbrain.com> (raw)
I perused the archive and did not see anything noted about this, but
please forgive me if it's been discussed.
Server: ubuntu 2004, running rsync 3.1.3 protocol version 31
client Windows 10 x64.
When calling rsync x64 3.2.4dev, transfer works fine.
When using rsync x32 3.2.4dev, downloaded last night, same transfer
fails, with:
"
dup() in/out/err failed
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
[sender] _exit_cleanup(code=12, file=io.c, line=228): entered
rsync error: error in rsync protocol data stream (code 12) at io.c(228)
[sender=3.2.4dev]
[sender] _exit_cleanup(code=12, file=io.c, line=228): about to call exit(12)
"
cwrsync fails in the same way.
Sadly, I would ignore and just use x64 rsync (as I normally do on my
system here), but this is to set up a sync job for a elderly user who
wants to update his web site and only has Windows x32 bit.
Any help would be most appreciated. I can probably come up with an
alternate solution (scp or zip/ftp) but rsync seemed a clean approach to
ensuring his local version of the site and the web version stayed in sync.
Jim
next reply other threads:[~2021-02-14 4:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 4:33 Jim Brain [this message]
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
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=cad3a794-d335-0522-689b-d8a4b826a723@jbrain.com \
--to=brain@jbrain.com \
--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).