From owner-freebsd-isp Fri Dec 20 01:14:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA12969 for isp-outgoing; Fri, 20 Dec 1996 01:14:50 -0800 (PST) Received: from serv1.zsb.th-darmstadt.de (server.zsb.th-darmstadt.de [130.83.63.190]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA12937; Fri, 20 Dec 1996 01:14:22 -0800 (PST) Received: from localhost (petzi@localhost) by serv1.zsb.th-darmstadt.de (8.8.2/8.8.2) with SMTP id KAA14349; Fri, 20 Dec 1996 10:12:53 +0100 (MET) Date: Fri, 20 Dec 1996 10:12:51 +0100 (MET) From: Michael Beckmann X-Sender: petzi@serv1.zsb.th-darmstadt.de Reply-To: Michael Beckmann To: isp@freebsd.org, hackers@freebsd.org Subject: innd can't remalloc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, my innd dies almost every day, and in the log I see messages like: Dec 20 08:52:37 news innd: SERVER cant remalloc 2097408 bytes Cannot allocate memory This is always the last message from innd, until I restart rc.news . I am running 2.1.5-RELEASE on this machine, and the problem is the same with inn 1.4 and 1.5.1. It seems to me that the crash occurs when the innd process grows to around 128 MB. I assume I am running into some kernel limitation, something like: "no process may have more than 128 MB RAM resident", but I cannot see any setting for that. Could anyone help me out ? I have already tried increasing some limits with ulimit statements at the beginning of rc.news, but this problem didn't go away. Cheers, Michael