Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!vpk4!shagar
From: shagar@vpk4.UUCP (Steven Hagar)
Newsgroups: comp.sys.att,u3b.tech
Subject: Re: Is the sysdump partition *really* needed on a 3B2/600?
Message-ID: <4375@vpk4.UUCP>
Date: 14 Mar 89 14:32:19 GMT
References: <1068@vsi.COM> <1070@vsi.COM> <1518@ucsd.EDU>
Reply-To: shagar@attcan.UUCP (Steven Hagar)
Distribution: comp
Organization: AT&T Canada Inc., Toronto
Lines: 19

In article <1518@ucsd.EDU> brian@ucsd.edu (Brian Kantor) writes:
>On my 3B15, I have the crash dump area pointed at the swap area.  It's
>not going to be swapping at the same time as it's crashing, and since
>I have no intention of ever doing anything but rebooting if it DOES ever
>crash, that's good enough for me.  I just don't want it spewing on
>my filesystems on the way down.

One of our service technicians recommends getting a dump of memory after
a crash, before rebooting the system.  He has found that the memory dump
can provide useful troubleshooting information, which will be purged when
memory is reinitialized during the reboot.  His experience in a number
of instances has been that rebooting clears the symptoms, but doesn't
necessarily correct the problem, and without a memory dump, you might
not know until the problem occurs again what the real problem was. 


  Steven Hagar             .
  AT&T Canada Inc.         .  ATTMAIL: !shagar
  (416) 756-5061           .  UUCP: uunet!attcan!shagar