From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 125677 invoked by alias); 16 Mar 2019 13:46:09 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 125461 invoked by uid 89); 16 Mar 2019 13:46:09 -0000 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 Received: from lb2-smtp-cloud7.xs4all.net (HELO lb2-smtp-cloud7.xs4all.net) (194.109.24.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 16 Mar 2019 13:46:07 +0000 Received: from tmp.9w8abNGpMi ([83.162.234.136]) by smtp-cloud7.xs4all.net with ESMTPSA id 59dUh97aNLMwI59dVhRQ8B; Sat, 16 Mar 2019 14:46:05 +0100 Date: Sat, 16 Mar 2019 13:46:00 -0000 Message-ID: <889ba2303b3c63b3cf7c46725e631c71@smtp-cloud7.xs4all.net> From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: rsync failed after windows 10 update References: <1552053188219-0.post@n5.nabble.com> <1552094225496-0.post@n5.nabble.com> <1552122636414-0.post@n5.nabble.com> <1552386193066-0.post@n5.nabble.com> <1552725398537-0.post@n5.nabble.com> <7103ba88f8a4ed85791eaff5e3d69e68@smtp-cloud9.xs4all.net> <1552733367004-0.post@n5.nabble.com> <1552741985987-0.post@n5.nabble.com> <1552742765380-0.post@n5.nabble.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 X-SW-Source: 2019-03/txt/msg00435.txt.bz2 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