From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Sat, 16 Mar 2019 13:31:00 -0000 [thread overview]
Message-ID: <f216e65043ddf6f0154399cccabc3202@xs4all.nl> (raw)
In-Reply-To: <b2d674f947e902064166f6522c081f00@smtp-cloud7.xs4all.net>
On 2019-03-16 13:45, Houder wrote:
> 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>
[snip]
> 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
Sorry, that should be:
export PATH=/usr/bin:/cygdrive/c/Windows/System32
(cygdrive, or whatever your prefix is)
as rsync is also dependent on .dll's from the Windows bin ...
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 13:31 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
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 [this message]
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=f216e65043ddf6f0154399cccabc3202@xs4all.nl \
--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).