From owner-freebsd-hackers Sat Dec 21 13:36:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02698 for hackers-outgoing; Sat, 21 Dec 1996 13:36:16 -0800 (PST) Received: from server.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 NAA02688; Sat, 21 Dec 1996 13:36:07 -0800 (PST) Received: from localhost (petzi@localhost) by server.zsb.th-darmstadt.de (8.8.2/8.8.2) with SMTP id WAA01456; Sat, 21 Dec 1996 22:35:36 +0100 (MET) Date: Sat, 21 Dec 1996 22:35:35 +0100 (MET) From: Michael Beckmann X-Sender: petzi@server.zsb.th-darmstadt.de To: Joerg Wunsch cc: isp@freebsd.org, hackers@freebsd.org Subject: Re: innd can't remalloc In-Reply-To: <199612201742.SAA04883@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Dec 1996, J Wunsch wrote: > datasize 131072 kbytes > ^^^^^^^^^^^^^ > You can override this using: > > options "MAXDSIZ='(256UL*1024*1024)'" > > (For 2.2 systems, leave out the '' quotes. Should be converted to an > official option.) It works !! Thank you. Next thing I'm going to upgrade to FreeBSD 2.2, to get the better malloc and some other enhancements from it. The innd doesn't have to be that large. I tried linking my inn with -lgnumalloc , but it was a desaster. Ever seen a sysload of 20 on a FreeBSD box ? I couldn't believe my eyes. 2.2-ALPHA performs very well on my other newsserver, no crashes or problems since I installed it three weeks ago. Cheers, Michael