Message-Id: <1136686821.13286.251326103@webmail.messagingengine.com>
From: "Brett Serkez" <techie@serkez.net>
To: "Ken Senior" <seniork@gmail.com>, cygwin@cygwin.com
Cc: cygwin@cygwin.com
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
References: <43BDAFBC.9080401@gmail.com>    <1136506661.2833.251196190@webmail.messagingengine.com>    <43BDBBC2.1040100@gmail.com>    <1136509322.5881.251198868@webmail.messagingengine.com>    <43BDCD93.1060009@gmail.com>    <1136517852.14114.251205876@webmail.messagingengine.com>    <43BFE85F.80308@gmail.com>
Subject: Re: cygwin and rsync
In-Reply-To: <43BFE85F.80308@gmail.com>
Date: Sat, 07 Jan 2006 21:20:21 -0500
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

<...snip...>
> Does this tell anyone anything?  If not, I could traverse the learning
> curve on getting gdb information from the process.

As an additional thought on why rsync may be hanging on a write to
stdout, presuming the cause is a deadlock.  What is the size of the file
it is hanging on?  We saw earlier that the number of bytes was around a
magic number.  I'm wondering if the number of bytes to be transmitted is
encountering a conversion error (truncation,sign,...). If one of the two
copies mis-understood how many bytes were to be transmitted it might
stop reading or writing to early and come out of sync with the other.

You might consider excluding this file and see if rsync is successful or
encounters another similar file it hangs on and exclude it and see if
they have something in common such as their size.

Just a thought,

Brett
----------------------------------------------------------------
Brett C. Serkez, Techie


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