From owner-freebsd-questions@FreeBSD.ORG Mon Oct 10 19:22:58 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A08EF16A41F for ; Mon, 10 Oct 2005 19:22:58 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43C6443D45 for ; Mon, 10 Oct 2005 19:22:58 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 4639 invoked from network); 10 Oct 2005 19:22:57 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Oct 2005 19:22:57 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id A39E741; Mon, 10 Oct 2005 15:22:56 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Paul Schmehl To: freebsd-questions@freebsd.org References: <5FFB5A9BEDCEE5A292071AE7@utd59514.utdallas.edu> From: Lowell Gilbert Date: 10 Oct 2005 15:22:56 -0400 In-Reply-To: <5FFB5A9BEDCEE5A292071AE7@utd59514.utdallas.edu> Message-ID: <44achh6usv.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: What are the likely causes of reboots? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2005 19:22:58 -0000 Paul Schmehl writes: > I've got a bit of a problem. I didn't configure this box, and swap is > only 250MB. Physical memory is a gig. Is there a workaround that > would allow me to write a core file to somewhere else? Put a separate disk on and dump to that. Or constrain the kernel to less memory than you have in your swap area. See the FAQ entry on "How can I make the most of the data I see when my kernel panics?".