Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 11 Aug 2005 13:34:44 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Rsync over SSH dies before it is able to send with lots of files Message-ID: <20050811173444.GB11563@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <42FA081C DOT 25957 DOT 24F4EADF AT localhost> <42FA2A6A DOT 29370 DOT 257AEDF0 AT localhost> <42F9FC86 DOT 8060602 AT byu DOT net> <42FB51FF DOT 3000000 AT byu DOT net> <20050811143112 DOT GD2816 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050811143112.GD2816@calimero.vinschen.de> User-Agent: Mutt/1.5.8i On Thu, Aug 11, 2005 at 04:31:12PM +0200, Corinna Vinschen wrote: >On Aug 11 07:26, Eric Blake wrote: >> Aha - I found something. When I first ran the touch command above, I >> stopped at about 8000 files (or about 400k for the subsequent echo command >> line), which gave the nice "Argument list too long" error. But when I >> increased the number of files to 45000 (or about 2 meg of command line), >> the same command failed with a segfault with bash 3.0, and gave no input >> but left $? at 5 (matching EIO) on the alpha bash 3.1. I will have to try >> debugging it now, but it seems odd that exec() is dying with E2BIG in one >> case and EIO when the input is even bigger. > >Can you reproduce this with the latest Cygwin snapshot? Corinna chided me into making sure that exec*() was more bulletproof in it's E2BIG detection so I've implemented better protection in the current snapshot. http://cygwin.com/snapshots/ cgf (who's about to have a multitasking meltdown unless he drinks more coffee soon) -- 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/