From owner-freebsd-isp Tue Oct 20 10:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12288 for freebsd-isp-outgoing; Tue, 20 Oct 1998 10:48:57 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from guardian.fortress.org (guardian-ext.fortress.org [199.202.137.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12273 for ; Tue, 20 Oct 1998 10:48:50 -0700 (PDT) (envelope-from andrew@guardian.fortress.org) Received: from localhost (andrew@localhost) by guardian.fortress.org (8.8.8/8.8.8) with SMTP id NAA09059; Tue, 20 Oct 1998 13:48:23 -0400 (EDT) (envelope-from andrew@guardian.fortress.org) Date: Tue, 20 Oct 1998 13:48:23 -0400 (EDT) From: Andrew Webster Reply-To: andrew@pubnix.net To: freebsd-isp@FreeBSD.ORG Subject: INN/CCD Question 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 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. Are these 2 problems related, and what do I need to tune to fix them? Thanks in advance! Andrew Webster andrew@pubnix.net Key fingerprint = CF E8 16 B8 A6 DB E3 C9 83 E7 96 24 25 58 15 6E PubNIX Montreal Connected to the world Branche au monde P.O. Box 147 Cote Saint Luc, Quebec H4V 2Y3 tel 514.990.5911 http://www.pubnix.net fax 514.990.9443 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message