From owner-freebsd-isp Tue Oct 20 11:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17758 for freebsd-isp-outgoing; Tue, 20 Oct 1998 11:40:31 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17752 for ; Tue, 20 Oct 1998 11:40:28 -0700 (PDT) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.8.8/8.8.8) with SMTP id OAA17484; Tue, 20 Oct 1998 14:40:45 -0400 (EDT) Date: Tue, 20 Oct 1998 14:40:45 -0400 (EDT) From: Dan Swartzendruber To: andrew@pubnix.net cc: freebsd-isp@FreeBSD.ORG Subject: Re: INN/CCD Question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Oct 1998, Andrew Webster wrote: > > I am happy to report that ccd/inn is a great combination and has been > running with excellent results since I implemented this. > > However, I have two small memory related problems when the system intially > boots. > > The system is running on a P233 with 128MB ram and a 18GB ccd array for > the spool on 2.2.5-Stable. > > During the boot, the fsck -p can't fsck the ccd because of a memory > allocation problem. I've made sure that the swapon -a and the ccdconfig > take place BEFORE the fsck. If I run fsck by hand in the shell, it works > fine though. > > I have a similar problem when inn starts (rc.news run from rc.local), it > cannot malloc enough memory, but if I run rc.news by hand from a root > shell, it works just fine. /etc/login.conf. The daemon class is relevant when booting, but when you do it interactively, it isn't (so you're okay). I was burned by this also. I think in 2.2 the limits are way too low... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message