Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!swrinde!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Spontaneous reboots Date: 30 Jun 1996 10:09:27 GMT Organization: Private BSD site, Dresden Lines: 20 Message-ID: <4r5jon$6g0@uriah.heep.sax.de> References: <Dts2HJ.3ps.E.fourthgen@fourthgen.fourthgen.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E tomg@fourthgen.fourthgen.com (Tom Greenwalt) wrote: > Is there a log or something that I can look at that would catch panics > or anything that I can watch to give me a clue about the reboots? You should enable kernel coredumps in /etc/sysconfig. Make sure you've got at least the amount of physical memory as free space under /var/crash, or wherever your dumps are supposed to go to. Btw., the kernel message buffer is not cleared on reboot, so after the system came up again, it should be fetched by syslogd (and it usually contains at least parts of the panic message there). Have a look into /var/log/messages. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)