From owner-freebsd-current Tue Jul 20 13:56:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id BC05A14C3D for ; Tue, 20 Jul 1999 13:56:01 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: (qmail 92665 invoked from network); 20 Jul 1999 20:54:41 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 20 Jul 1999 20:54:41 -0000 Date: Tue, 20 Jul 1999 15:54:41 -0500 (CDT) From: David Scheidt X-Sender: dscheidt@shell-3.enteract.com To: Matthew Dillon Cc: "Steven G. Kargl" , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? In-Reply-To: <199907202045.NAA06906@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 On Tue, 20 Jul 1999, Matthew Dillon wrote: > > 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. savecore saving compressed crash dumps is handy on production machines with lots of memory. I run a bunch of HP/UX boxes that don't have 4 gigs in /var/crash, because they never crash, except of course when they do. It is very useful to be able to save the dump, even if I have to analyze it somewhere else. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message