delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
Message-ID: | <1058553448.3f183e6879a0d@www.mail.cloud9.net> |
Date: | Fri, 18 Jul 2003 14:37:28 -0400 |
From: | Gene Livshits <livshits AT cloud9 DOT net> |
To: | "" <cygwin AT cygwin DOT com> |
Subject: | Re: Problem with cygwin.dll ver 1.5.0-1 |
References: | <1058543936 DOT 3f18194077d1b AT www DOT mail DOT cloud9 DOT net> <20030718160810 DOT GB5223 AT redhat DOT com> |
In-Reply-To: | <20030718160810.GB5223@redhat.com> |
MIME-Version: | 1.0 |
User-Agent: | Internet Messaging Program (IMP) 3.2 |
X-Originating-IP: | 170.148.10.46 |
X-AntiVirus: | checked by Vexira MailArmor (version: 2.0.1.7; VAE: 6.20.0.1; VDF: 6.20.0.42; host: russian-caravan.cloud9.net) |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id h6IIbei15784 |
Here is a more detailed description of the problem: + /usr/bin/rsync -arvzu -e /usr/bin/ssh --delete --force --stats -- progress --rsync-path /usr/bin/rsync z floyd.orangeblues.com:/tmp Failed to dup/close : Socket operation on non-socket rsync error: error in IPC code (code 14) at /tmp/rsync-2.5.6/pipe.c(68) rsync: read error: Connection reset by peer rsync error: error in rsync protocol data stream (code 12) at /tmp/rsync- 2.5.6/i o.c(177) Quoting Christopher Faylor <cgf-idd AT cygwin DOT com>: > On Fri, Jul 18, 2003 at 11:58:56AM -0400, Gene Livshits wrote: > >It looks like the rsync -e ssh problem with sockets was not fixed in > >cygwin1.dll ver 1.5.0-1. Does anyone know how to fix it or when it's > >going to be fixed? > > Rather than assume that we know what you are talking about, why not > file > a proper bug report detailing what specifically, "the 'rsynce -e ssh' > problem" is? > > You can read: http://cygwin.com/problems.html for a description on > how to file problem reports. I've quoted one section below: > > # Do not assume that your problem is so trivial or so "well known" > that > it does not require any details or background from you. Many (most?) > people who report problems fall into the trap of assuming that people > are "clued into" their mental state when, in most cases, this is not > the > case. > > As a rule of thumb, if you find yourself referring to your problem as > the problem with XYZ rather than a problem with XYZ then your message > is > suspect. Using "the" in this context means that you are assuming > that > your problem is well known. Unless you can point to an email message > thread or FAQ entry (either of which is a good idea, btw) please do > not > assume that the readers of your message will be familiar with your > problem. > -- > Please use the resources at cygwin.com rather than sending personal > email. > Special for spam email harvesters: send email to aaaspam AT sourceware DOT org > and be permanently blocked from mailing lists at sources.redhat.com > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |