X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=qtZGmY
	hT6re4UHA7DqvRst+wBOepn2Xe4sv4YITMqrr670HM5UaDAs3zbZLoAVUPQMebaT
	+Cg0pLTcxNcyVBw0qoH9TurtLH7vlFgxwrdd9UZnnZFuermOPU5eLWct6VH7t4u4
	XofJvpNWDugeUILvjx8e4uBuv0NGdaCDsLLJ4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=iWRjoYYn7oU9
	ZvixoDngbVoTT38=; b=lh4L3RB2zzQEAxgeo1Plg6pqy4WlhioZ4K9sIbxBk0fn
	6cgN6lfLG4Hr/vomV+QXkEwW/uacpadSbYqSWn07i5tnSRBkLTaJw1H67MnxLUDZ
	j8V0FvNe1mnM/Y8KOIa6cNQrEjNdI553ibecbYSLgh3TmN5U8b8tXez66o64m2Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=boxes, capabilities, pipec, W10
X-HELO: lb2-smtp-cloud7.xs4all.net
Date: Sat, 16 Mar 2019 14:46:05 +0100
Message-ID: <889ba2303b3c63b3cf7c46725e631c71@smtp-cloud7.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: rsync failed after windows 10 update
References: <1552053188219-0 DOT post AT n5 DOT nabble DOT com> <d4e4d78e-99da-bf59-ec9e-06e2562c1333 AT yahoo DOT com> <1552094225496-0 DOT post AT n5 DOT nabble DOT com> <1552122636414-0 DOT post AT n5 DOT nabble DOT com> <1552386193066-0 DOT post AT n5 DOT nabble DOT com> <1552725398537-0 DOT post AT n5 DOT nabble DOT com> <7103ba88f8a4ed85791eaff5e3d69e68 AT smtp-cloud9 DOT xs4all DOT net> <1552733367004-0 DOT post AT n5 DOT nabble DOT com> <b2d674f947e902064166f6522c081f00 AT smtp-cloud7 DOT xs4all DOT net> <1552741985987-0 DOT post AT n5 DOT nabble DOT com> <1552742765380-0 DOT post AT n5 DOT nabble DOT com>
In-Reply-to: <1552742765380-0.post@n5.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

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