Re: Rsync over SSH dies before it is able to send with lots of files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 8/11/2005 9:15 PM: > Out of curiousity do you have your /bin directory mounted with -X? If > so, this should remove most of the command line length limitations -- > except in 1.5.18 which was unable to allocate more

Re: Rsync over SSH dies before it is able to send with lots of files

On Thu, Aug 11, 2005 at 09:01:11PM -0600, Eric Blake wrote: >According to Christopher Faylor on 8/11/2005 11:34 AM: >>>Can you reproduce this with the latest Cygwin snapshot? > >snapshot 20050811 fixes the problem; I correctly got "Argument list too >long" on a 2 meg command line, in both bash 3.0

Re: Rsync over SSH dies before it is able to send with lots of files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 8/11/2005 11:34 AM: >>Can you reproduce this with the latest Cygwin snapshot? snapshot 20050811 fixes the problem; I correctly got "Argument list too long" on a 2 meg command line, in both bash 3.0 and in my private

Re: Rsync over SSH dies before it is able to send with lots of files

On Thu, Aug 11, 2005 at 02:02:05PM -0700, Brian Dessent wrote: >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. B

Re: Rsync over SSH dies before it is able to send with lots of files

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 o

Re: Rsync over SSH dies before it is able to send with lots of files

On 11 Aug 2005 at 7: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

Re: Rsync over SSH dies before it is able to send with lots of files

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 t

Re: Rsync over SSH dies before it is able to send with lots of files

On Aug 11 07:26, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to Eric Blake on 8/10/2005 7:09 AM: > > > > I still want to figure out why you were getting a crash. I tried the > > following: > > > > $ cd /tmp > > $ mount -m > > ... > > mount -f -s -b -X "c:/c

Re: Rsync over SSH dies before it is able to send with lots of files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/10/2005 7:09 AM: > > I still want to figure out why you were getting a crash. I tried the > following: > > $ cd /tmp > $ mount -m > ... > mount -f -s -b -X "c:/cygwin/bin" "/bin" > $ mkdir lots > $ # 45000 invocations of

Re: Rsync over SSH dies before it is able to send with lots of files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Brown on 8/9/2005 10:25 PM: > >>Hmm, you're making bash expand a wildcard into 45000 files. This >>shouldn't crash bash, but I'm guessing there is some of memory >>corruption or malloc failure when consuming so much memory all before

Re: Rsync over SSH dies before it is able to send with lots of files

On 9 Aug 2005 at 21:41, Eric Blake wrote: > For starters, since you are using rsync recursion, get rid of the * to > give rsync just a single filename at startup, rather than making bash > try to expand 45000 names all at once on the command prompt: Bingo! Of course now that you mention it, it's

Re: Rsync over SSH dies before it is able to send with lots of files

On Tue, Aug 09, 2005 at 11:56:00PM -0400, Christopher Faylor wrote: >On Tue, Aug 09, 2005 at 09:41:47PM -0600, Eric Blake wrote: >>> - Mounted the directory that I'm copying from elsewhere and made it >>> executable (worth a crack) >> >>The only difference you might make to get a larger command

Re: Rsync over SSH dies before it is able to send with lots of files

On Tue, Aug 09, 2005 at 09:41:47PM -0600, Eric Blake wrote: >> - Mounted the directory that I'm copying from elsewhere and made it >> executable (worth a crack) > >The only difference you might make to get a larger command line argument >length is to make rsync's directory mounted executable (no

Re: Rsync over SSH dies before it is able to send with lots of files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Brown on 8/9/2005 7:58 PM: > > rsync --progress -rtv 192.168.0.1::mydirectory/* c:\localcopy For starters, since you are using rsync recursion, get rid of the * to give rsync just a single filename at startup, rather than making bas

Re: Rsync over SSH dies before it is able to send with lots of files

> [EMAIL PROTECTED]:/cygdrive/e/path_to_files/* c:\localcopy > [EMAIL PROTECTED]'s password: Before anyone spots it (too late?), the lines above missed my "cleaning" before posting. There's nothing wrong with the SSH connection. The example in the post should all refer to [EMAIL PROTECTED] (m