public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Sat, 16 Mar 2019 13:46:00 -0000	[thread overview]
Message-ID: <889ba2303b3c63b3cf7c46725e631c71@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <1552742765380-0.post@n5.nabble.com>

On Sat, 16 Mar 2019 06:26:05, jwang  wrote:
> rsync  -vvv /tmp/test2.log /tmp/tmp/
> rsync: pipe: Connection timed out (116)
> rsync error: error in IPC code (code 14) at pipe.c(122) [sender=3.1.2]
> [sender] _exit_cleanup(code=14, file=pipe.c, line=122): about to call
> exit(14)
> 
> rsync used to work perfectly and still do on my other Windows 10 boxes.  
> Just one box has problem.  
> 
> About PATH - i think it is defined by cygwin /etc/profile and my other boxes
> also long PATH :)

Yes James,

But this is NOT about "what used to work", it is about what is NOT working NOW
on this specific machine ...

It is also not relevant (to a large extent) that rsync is working on the other
W10 boxes you own ...

The main issue (to us) here is: Is it Cygwin that is causing the problem? Said
differently, if it is not Cygwin, than we cannot help you.

In that case, you will have to rely on your own capabilities (and the support,
if any, given by Microsoft).

So, the reason I am asking to reduce your PATH definition is to exclude Cygwin
as the cause of your recent problem on this specific box.

Excluding, excluding ... that is the main theme here!

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

  reply	other threads:[~2019-03-16 13:46 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 [this message]
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=889ba2303b3c63b3cf7c46725e631c71@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).