Date: Tue, 20 Jul 1999 15:54:41 -0500 (CDT) From: David Scheidt <dscheidt@tumbolia.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>, Poul-Henning Kamp <phk@critter.freebsd.dk>, freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? Message-ID: <Pine.NEB.3.96.990720154957.82272B-100000@shell-3.enteract.com> In-Reply-To: <199907202045.NAA06906@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.990720154957.82272B-100000>