From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Sat, 16 Mar 2019 12:45:00 -0000 [thread overview]
Message-ID: <b2d674f947e902064166f6522c081f00@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <1552733367004-0.post@n5.nabble.com>
On Sat, 16 Mar 2019 03:49:27, jwang wrote:
> rsync /tmp/test.log /cygdrive/c/temp/
> rsync: pipe: Connection timed out (116)
> rsync error: error in IPC code (code 14) at pipe.c(122) [sender=3.1.2]
>
> cygcheck.txt <http://cygwin.1069669.n5.nabble.com/file/t11507/cygcheck.txt>
Based on the output of cygcheck -srv,
- you are using W10 (while I am using W7 - rsync works at my place)
Also:
- Current System Time: Sat Mar 16 11:44:27 2019
- Windows 10 Home Ver 10.0 Build 17134
- you are using the 64-bits version of Cygwin (root = c:\cygwin64)
- Cygwin DLL version info: DLL version: 3.0.2
- rsync: version: 3.1.2-1
- librsync2: 1.0.0-1 (resulting in bin/cygrsync-2.dll)
(not installed at my place)
Your PATH definition is exceptionally long ...
- it contains e:\Cywin64\bin twice
- it contains a multitude of "bins", irrelevant to Cygwin
Finding the cause of your problem is an exercise in reducing your
environment to the absolute minimum, required to execute rsync.
I would suggest to (temporarily):
- uninstall librsync2 (it should not interfere w/ rsync, but it
is also not required)
- limit your PATH definition to e:\cygwin64
- i.e. export PATH=/usr/bin, if you are using bash
and run, rsync -vvv <some file> <some directory> again, and show
us the output.
Do not use the arguments that you used previously; create a new
file and a new directory to 'copy' to.
Remember, finding the cause of a problem, is first and foremost
about excluding any factor (you did not think of).
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-16 12:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 12:19 jwang
2019-03-04 12:36 ` Corinna Vinschen
2019-03-04 14:44 ` jwang
2019-03-05 9:46 ` jwang
2019-03-05 12:04 ` Corinna Vinschen
2019-03-05 13:16 ` jwang
2019-03-05 15:25 ` jwang
2019-03-06 10:00 ` jwang
2019-03-06 11:57 ` Corinna Vinschen
2019-03-06 12:05 ` jwang
2019-03-06 12:14 ` Corinna Vinschen
2019-03-06 14:00 ` jwang
2019-03-08 13:59 ` jwang
2019-03-08 14:18 ` Houder
2019-03-08 15:35 ` jwang
2019-03-08 20:59 ` Jerry Baker via cygwin
2019-03-09 1:23 ` jwang
2019-03-09 9:16 ` jwang
2019-03-11 15:02 ` jwang
2019-03-12 10:29 ` jwang
2019-03-16 8:36 ` jwang
2019-03-16 10:30 ` Houder
2019-03-16 10:49 ` jwang
2019-03-16 12:45 ` Houder [this message]
2019-03-16 13:13 ` jwang
2019-03-16 13:19 ` jwang
2019-03-16 13:26 ` jwang
2019-03-16 13:46 ` Houder
2019-03-16 14:18 ` jwang
2019-03-16 13:31 ` Houder
2019-03-17 6:45 ` Achim Gratz
2019-03-17 8:15 ` jwang
2019-03-17 9:07 ` Eliot Moss
2019-03-18 9:47 ` jwang
2019-04-02 8:45 ` jwang
2019-03-05 12:20 ` Andrey Repin
2019-03-05 13:15 ` jwang
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=b2d674f947e902064166f6522c081f00@smtp-cloud7.xs4all.net \
--to=houder@xs4all.nl \
--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).