X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.7 required=5.0 	tests=AWL,BAYES_50,FAKE_REPLY_C,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <F464953BCA8D41BCA62C80EEFF2805BA@trcintl.com>
From: "Lists" <lists AT trcintl DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Re: Possible Bug or limitation in Cygwin 1.7 and Rsync and file number limit
Date: Wed, 15 Jul 2009 13:47:27 -0500
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
X-TRC-MailScanner-Information: Please contact the ISP for more information
X-TRC-MailScanner-ID: n6FIdhS3007519
X-TRC-MailScanner: Found to be clean
X-TRC-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=2.013, 	required 5.75, FAKE_REPLY_C 2.01, STOX_REPLY_TYPE 0.00)
X-TRC-MailScanner-SpamScore: xx
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

>snip<
>
> I just discovered some additional information that may help get to the
> bottom of this.  Not sure what made me think of this, but I decided to try
> an older version of rsync.  If I run rsync 3.0.4-1 or 3.0.5-1, I
> experience the problem.  However, when I run 2.6.9-2, the only other
> version of rsync I can find built specifically for cygwin 1.7, the problem
> goes away and all works fine?
>
> By the way Corinna, in case I didn't say it before, thank you very much
> for trying to help out and for the time you spend on this project!
>
> - Kyle
>

I realize this problem wasn't being worked on as the developers could not
reproduce it however I thought I would give an update just the same.  I
downloaded the latest version of the 1.7 cygwin1.dll this morning dated
7-13-2009 and this problem is now fixed.  If I put the old 1.7 dll in place 
(dated 6-18-2009),
the problem immediately returns.  So whatever the problem was, this latest
build seems to have corrected it.

Thanks to all for the hard work in maintaining cygwin!

- Kyle


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