Date: Tue, 20 Oct 1998 14:40:45 -0400 (EDT) From: Dan Swartzendruber <druber@mail.kersur.net> To: andrew@pubnix.net Cc: freebsd-isp@FreeBSD.ORG Subject: Re: INN/CCD Question Message-ID: <Pine.BSF.3.96.981020144001.15876B-100000@mail.kersur.net> In-Reply-To: <Pine.BSF.3.96.981020133546.22537A-100000@guardian.fortress.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981020144001.15876B-100000>