From owner-freebsd-stable Tue Nov 5 08:58:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10039 for stable-outgoing; Tue, 5 Nov 1996 08:58:04 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA10034 for ; Tue, 5 Nov 1996 08:58:00 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id IAA03067; Tue, 5 Nov 1996 08:57:50 -0800 (PST) Message-Id: <199611051657.IAA03067@austin.polstra.com> To: src@NS.Contrib.Com Subject: Re: innd can't malloc - why? Newsgroups: polstra.freebsd.stable In-Reply-To: <199611051250.NAA11668@NS.Contrib.Com> References: <199611051250.NAA11668@NS.Contrib.Com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Tue, 05 Nov 1996 08:57:50 -0800 From: John Polstra Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199611051250.NAA11668@NS.Contrib.Com> src@NS.Contrib.Com write: > maybe i'm a little ignorant, but my innd lately vanishes very often > our of the blue (i.e. not during expire) telling me > > Nov 5 07:52:15 news innd: ME cant remalloc 8392960 bytes Cannot allocate memory > > i recently upgraded the machine to 128MB RAM (yes, i have the > 'options "MAXMEM=131072"' in the kernel) and 300MB swap, > which should be enough! Check your "ulimit" values, and make sure that they're not too low. From sh or bash, type "ulimit -a". From csh, type "limit". Obviously, you have to do this in the same context your innd process is started in. You can increase these limits from "/etc/profile" or ".profile" in the home directory (for sh). See your shell's manual page for details. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth