From owner-freebsd-current@FreeBSD.ORG Sun May 2 07:15:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B8F716A4CE for ; Sun, 2 May 2004 07:15:39 -0700 (PDT) Received: from endif.cjb.net (65-101-229-205.dnvr.qwest.net [65.101.229.205]) by mx1.FreeBSD.org (Postfix) with SMTP id B13B043D54 for ; Sun, 2 May 2004 07:15:38 -0700 (PDT) (envelope-from end@endif.cjb.net) Received: (qmail 20838 invoked from network); 2 May 2004 14:15:37 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 2 May 2004 14:15:37 -0000 Date: Sun, 2 May 2004 08:15:37 -0600 From: Robin Schoonover To: Panagiotis Astithas In-Reply-To: <4094F86E.2020908@noc.ntua.gr> References: <200404301403.50634.past@noc.ntua.gr> <20040430123040.GB30157@melusine.cuivre.fr.eu.org> <20040430211948.GC85783@dragon.nuxi.com> <4094F86E.2020908@noc.ntua.gr> X-Mailer: Sylpheed version 0.9.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040502141538.B13B043D54@mx1.FreeBSD.org> cc: freebsd-current@FreeBSD.ORG Subject: Re: Change default dumpdir to /usr/crash? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2004 14:15:39 -0000 On Sun, 02 May 2004 16:32:30 +0300, Panagiotis Astithas wrote: > > Hmmm, tricky. In my office alone I can count at least 5 systems with > different amounts of memory, from 128 MB to 1 GB. Now only the first one > can get crashdumps in a 256 MB /var. If we resize /var to 1 GB (as I > usually do) we get working crashdumps in 4 out of 5. Upping it to 2 GB > we get all 5 of my systems. The maximum configuration of 4 GB (for > 32-bit systems) needs a 4.5 GB /var, which is not too much for the 60 GB > hard disks we buy nowadays in laptops (servers come with larger disks > and need more space in /var for logs, anyway). If we cater for 64-bit > systems too, we need even more... > > I think I would be conservative and suggest a 1 GB /var for now. > Or suggest a value based on the amount of memory. Something like a base value (256 MB or 512 MB?) + the amount of memory. This would protect us in the instance that we have 1 GB or greater (which is becoming increasingly more common) because otherwise we'd -still- get bitten, and more and more systems these days start out with 1+ GB of memory. It probably could be implemented it similarly to how autosizing of swap is implemented. -- Robin Schoonover (aka End) # # I don't want to bore you, but there's nobody else around for me to bore. #