From owner-freebsd-questions Thu Jul 11 18:26:33 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18871 for questions-outgoing; Thu, 11 Jul 1996 18:26:33 -0700 (PDT) Received: from nico.aarnet.edu.au (nico.aarnet.edu.au [139.130.204.16]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA18866 for ; Thu, 11 Jul 1996 18:26:31 -0700 (PDT) Received: from nico.telstra.net (nico.aarnet.edu.au [139.130.204.16]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id LAA29107 for ; Fri, 12 Jul 1996 11:23:40 +1000 Date: Fri, 12 Jul 1996 11:23:39 +1000 (EST) From: Wayne Farmer To: questions@freebsd.org Subject: Memory Process Limit when running /bin/sh Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have named running from /etc/sysconfig and hence /etc/rc on boot. It is running as a caching named and grows with time. But when it hits 64Mb, the following occurs : ... named[68]: savedata: malloc: Cannot allocate memory - ABORT ... /kernel: pid 68: named: uid 0: exited on signal 6 ... /kernel: uid 0 on /: file system full A previous answer suggested this was a shell limit and suggested the ulimit command in sh - I looked but did not find so I ran named again using tcsh with increased memory limits and it is now running at 90Mb no problems. Does /bin/sh have a built-in limit ? Can it be changed ? What is the suggestion in this type of case ? I have read where /bin/sh is not true Bourne. Thanks Wayne