Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-12 Thread Chet Ramey
On 8/10/13 12:47 AM, Bob Proulx wrote: > John Vincent wrote: >> I find that if I enter the command: >> echo {1..2000} >> it runs, but afterwards whenever I enter another command I get the error: >> -bash: fork: Cannot allocate memory > > You need to allocate more virtual memory space to your m

Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-12 Thread Greg Wooledge
On Fri, Aug 09, 2013 at 10:47:21PM -0600, Bob Proulx wrote: > John Vincent wrote: > > echo {1..2000} > > it runs, but afterwards whenever I enter another command I get the error: > > -bash: fork: Cannot allocate memory > > You need to allocate more virtual memory space to your machine. You >

Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-09 Thread Bob Proulx
John Vincent wrote: > I find that if I enter the command: > echo {1..2000} > it runs, but afterwards whenever I enter another command I get the error: > -bash: fork: Cannot allocate memory You need to allocate more virtual memory space to your machine. You are asking it to do more than it can

memory allocation bug in bash 4.2.39(1)-release

2013-08-09 Thread John Vincent
I'm using bash 4.2.39(1)-release, part of Fedora release 17 (Beefy Miracle) I find that if I enter the command: echo {1..2000} it runs, but afterwards whenever I enter another command I get the error: -bash: fork: Cannot allocate memory I guess that the memory allocated to all those n