From owner-freebsd-stable Fri Dec 19 02:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA11106 for stable-outgoing; Fri, 19 Dec 1997 02:58:18 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from brane.digs.iafrica.com (sz9qqJZhjAwfwSwIVn+NuqZjBYr1qnj8@brane.digs.iafrica.com [196.7.162.25]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA11091 for ; Fri, 19 Dec 1997 02:58:01 -0800 (PST) (envelope-from iang@digs.iafrica.com) Received: from digs.iafrica.com [127.0.0.1] ([GTPld4P6XWAY5n+ndQL1vZvW3W23qlpV]) by brane.digs.iafrica.com with esmtp (Exim 1.71 #1) id 0xj07w-0000Vv-00; Fri, 19 Dec 1997 12:57:56 +0200 To: stable@freebsd.org Subject: fsck problem at boot time X-Attribution: BOFH Date: Fri, 19 Dec 1997 12:57:56 +0200 From: Ian Freislich Message-Id: Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Were having a problem with our news server at boot time. Fsck complains that it can't alloc about 8Mb of memory for lncntp (?) when it comes to check the news spool filesystem - a ccd of 4 4Gb disks. This problem relates to the resources allowed to the boot process, run as user daemon - as I'm led to believe. Fscking a 16Gb disk requires more memory than the kernel is willing to give to fsck. The entry in /etc/login.conf for daemon hints that the limits set here are used for rc. Changing the limits here, running cap_mkdb and rebooting proved otherwise. My eventual solution to the problem was to add the follwing to .etc.rc: ulimit -d 65536 ulimit -s 65536 ulimit -m 65536 ulimit -l 65536 Which is IMHO a rather inelegant hack. Can anyone suggest a better solution or at least empathise :) -- igf (Ian Freislich) Senior Network Enginner UUNET Internet Africa http://copernicus.iafrica.com/