From owner-freebsd-current Tue Jul 20 13:46:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id EABDD153DC for ; Tue, 20 Jul 1999 13:46:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA06906; Tue, 20 Jul 1999 13:45:53 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 13:45:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199907202045.NAA06906@apollo.backplane.com> To: David Scheidt Cc: "Steven G. Kargl" , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, 20 Jul 1999, Matthew Dillon wrote: : :> :> * 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. : :Is there any reason that savecore(8) can't write compressed crashdumps? :(Other than no one haveing ever written the the code, of course.) In :other words, if I wrote this would it get committed? : :David Scheidt A crash dump would have to uncopmressed to gdb it. If you have sufficient space to hold a crash dump, just point /var/crash at that space. If you compress it right off the bat then someone is going to have to uncompress it to look at it. I sometimes compress crash dumps if I want to save them after I'm through gdb'ing them. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message