From owner-freebsd-current Tue Jul 20 13: 6:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id DA65514E71 for ; Tue, 20 Jul 1999 13:06:38 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-170.skylink.it [194.185.55.170]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA17894; Tue, 20 Jul 1999 22:06:33 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id WAA01737; Tue, 20 Jul 1999 22:00:47 +0200 (CEST) Date: Tue, 20 Jul 1999 22:00:47 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Matthew Dillon Cc: "Steven G. Kargl" , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? In-Reply-To: <199907201849.LAA06381@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And how do you create dumps from a kernel that hasn't finished booting (not gotten to the stage of reading rc.conf)? 'dumps on' in kernel config does not seem to do the job. Nick > A checklist for people who want kernel cores: > > * make sure that dumpdev is set to point to your swap partition > in your /etc/rc.conf > > * make sure your swap partition is large enough to hold the crash > dump. If you have 256MB of ram, your swap partition must be > at least 256MB in size. > > * make sure /var/crash has sufficient space to hold the dump > (note: /var/crash *can* be a softlink to a directory in some > other partition if /var does not have sufficient space) > > /var/crash must nominally have sufficient space to hold the crash > dump (a file of the same size as the amount of memory you have), > *and* the kernel image. Normally you give it a lot more space so > you store several crash dumps in it at once. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message