Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID:	<3B289972.9AD08955@lapo.it>
Date:	Thu, 14 Jun 2001 13:01:07 +0200
From:	Lapo Luchini <lapo AT lapo DOT it>
X-Mailer:	Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language:	it,en,fr,es,ja
MIME-Version:	1.0
To:	cygwin-apps AT cygwin DOT com
Subject:	about rsync's "read error"
References:	<3B22707B DOT 1448EB07 AT lapo DOT it> <20010611174927 DOT A17007 AT redhat DOT com> <3B25D329 DOT A8C043D7 AT lapo DOT it> <20010612104345 DOT D26626 AT redhat DOT com> <20010613142408 DOT A9592 AT redhat DOT com>

The unix version had some "hang" problems caused by improper closing of the
socket, it seems that those are the same problem that caused cywin compiled
version to always report "read error" after sending.
There's a patch for that hang problem, on rsync mailing list, that solves that
problems for unix version and incidentally solves cygwin's problems as well.

It's a "working on", tough.. maybe we could use that to do a rsync-2.4.6-2,
marking it as "experimental" in setup.exe
Or maybe it's better to just wait that rsync finishes to develop 2.4.7, that
will contain that patch?
I tested it in various ways and it shouws no problems (it shows one problem
less, actually), but I can't say I'm *really* sure it works perfectly.

Anyway, the package is ready nonetheless at:
http://www.lapo.it/tmp/rsync-2.4.6-2.tar.bz2
http://www.lapo.it/tmp/rsync-2.4.6-2-src.tar.bz2

--
Lapo 'Raist' Luchini
lapo AT lapo DOT it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)

- Raw text -