From owner-freebsd-questions Wed Aug 27 13:25:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA03978 for questions-outgoing; Wed, 27 Aug 1997 13:25:27 -0700 (PDT) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA03969 for ; Wed, 27 Aug 1997 13:25:20 -0700 (PDT) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.8.5/8.8.5) with SMTP id QAA10115; Wed, 27 Aug 1997 16:51:21 -0300 (EST) Date: Wed, 27 Aug 1997 16:51:20 -0300 (EST) From: Paulo Fragoso To: Jason Alan Nordwick cc: freebsd-questions@FreeBSD.ORG Subject: Re: malloc failes to get over 64M In-Reply-To: <19970827121920.14025.qmail@scheme.xcf.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, On 27 Aug 1997, Jason Alan Nordwick wrote: > > On 2.1.7.1 I can not seem to malloc more than 64M. I have tried > to reset the rlimit, but that doesn't work. And it reports that > there is no hard limit set, either ? Yes, there is a hard limit. Try modify this whith 'limit' in csh: % limit cputime unlimited filesize unlimited datasize 65536 kbytes stacksize 8192 kbytes coredumpsize unlimited memoryuse 29476 kbytes memorylocked 9826 kbytes maxproc 512 openfiles 512 % % limit datasize 131070 % limit cputime unlimited filesize unlimited datasize 131070 kbytes stacksize 8192 kbytes coredumpsize unlimited memoryuse 29476 kbytes memorylocked 9826 kbytes maxproc 512 openfiles 512 % now you can malloc to 128M :-) > > Jay > -- > Join the FreeBSD Revolution! > mailto:nordwick@xcf.berkeley.edu > http://xcf.berkeley.edu/~nordwick > Paulo Fragoso. http://www.nlink.com.br