Message-ID: <4AF5A3B3.7010403@monai.ca>
Date: Sat, 07 Nov 2009 08:43:31 -0800
From: Steven Monai <steve+cygwin AT monai DOT ca>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problem with rsync 3.0.6-1 under 1.7.0-62 and 63
References: <4AF58831 DOT 3080306 AT cs DOT umass DOT edu>
In-Reply-To: <4AF58831.3080306@cs.umass.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Eliot Moss wrote:
> I am getting this output when trying to rsync
> to any of several systems. I have RSYNC_RSH set
> to use ssh, and the ssh commands work just fine.
> This smells like some kind of non-matching library
> issue to me ...
> 
> rsync: Failed to dup/close: Bad file descriptor (9)
> rsync error: error in IPC code (code 14) at
> /home/lapo/packaging/rsync-3.0.6-1/src/rsync-3.0.6/pipe.c(72)
> [sender=3.0.6]
> rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
> Connection reset by peer (104)
> rsync error: error in IPC code (code 14) at
> /home/lapo/packaging/rsync-3.0.6-1/src/rsync-3.0.6/io.c(1525)
> [sender=3.0.6]

I am curious to know: What is the specific command-line you're using to
invoke rsync when it produces the above output?

Yours may not be a Cygwin-specific problem, as I routinely use rsync
over ssh on 1.7.0-63, and I have never seen that. The rsync mailing list
is another resource you could try. The 'rsync FAQ' and 'rsync current
issues' pages (google them) may also be of help.

-SM
--

--
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