X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <79EA1DCBF09A42BAB51DDB14456AE2BF@trcintl.com> From: "Lists" To: References: <200906191739 DOT n5JHcoBi001404 AT spam DOT trcww DOT com> <4A3BEE25 DOT 9010508 AT cygwin DOT com> <1C88F13C5CE84452AE2F41F23365AB73 AT trcintl DOT com> <20090622115136 DOT GQ5039 AT calimero DOT vinschen DOT de> <9A8D583A539F4BBCB2B2055172F6445A AT trcintl DOT com> <20090629095231 DOT GC30864 AT calimero DOT vinschen DOT de> Subject: Re: Possible Bug or limitation in Cygwin 1.7 and Rsync and file number limit Date: Wed, 1 Jul 2009 07:36:43 -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: n61CTE00012976 X-TRC-MailScanner: Found to be clean X-TRC-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=1.001, required 5.75, autolearn=not spam, BAYES_50 1.00, STOX_REPLY_TYPE 0.00) X-TRC-MailScanner-SpamScore: x X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > On Jun 26 23:42, Lists wrote: >>> On Jun 19 15:55, Lists wrote: >>>> >>> Works fine for me under the latest Cygwin 1.7.0-50 using your perl >>> script and your rsync options. I tend to agree to Larry's assumption >>> that some 3PP is interferring. >> >> Sorry to just now be replying but I have been out of the country. I >> tried the same procedure on yet another computer. I actually got it to >> run one time without a problem. I then deleted the copied files and >> repeated the procedure and got the same problem again. >> >> I am totally convienced there is a problem here. > > Still, I can't reproduce it. I just ran this with the latest Cygwin > from CVS and it works fine for me, multiple times, every time removing > the copied files from the former run. > > I ran the command the same way you did, I guess, just using different > paths for the source and destination directories: > > rsync --recursive \ > --human-readable \ > --delete \ > --times \ > --ignore-errors \ > --stats \ > --progress \ > -v -v \ > ~/tmp/rsync ~/tmp/rsync-tgt > >> Can anyone else try this and confirm the problem? If it works, I suspect >> if you try it again a time or two, you too will see the problem. Before >> trying it again, you need to make sure and delete the files from the >> destination directory. > > I tried it 6 times in a row, every time erasing the destination files. > Works fine for me. > > > Corinna > Perhaps you have hit upon the problem. I am just downloading and running setup-1.7.exe and it definetly has this problem. I tried to download and build it from CVS as you did but I have never done that before and for some reason it isn't working. I'm not even sure if I am downloading code for v1.5 or v1.7 but when I follow the instructions under the FAX, it won't build. So when will the latest changes be incorporated in the version downloaded in the setup-1.7.exe because it defintely has this problem. I have no doubt about it. Or, is there somewhere else I can find a pre-built version of the latest CVS cygwin1.dll? - 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