From owner-freebsd-hackers Wed Oct 25 11:38:23 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA03945 for hackers-outgoing; Wed, 25 Oct 1995 11:38:23 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA03940 for ; Wed, 25 Oct 1995 11:38:21 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id LAA24356; Wed, 25 Oct 1995 11:37:49 -0700 From: Julian Elischer Message-Id: <199510251837.LAA24356@ref.tfs.com> Subject: Re: Correct kernel ops for Panic To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 25 Oct 1995 11:37:49 -0700 (PDT) Cc: hackers@freebsd.org In-Reply-To: <199510251803.OAA08396@crh.cl.msu.edu> from "Charles Henrich" at Oct 25, 95 02:03:57 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 510 Sender: owner-hackers@freebsd.org Precedence: bulk > On some versions of FreeBSD, you can see the last panic with dmesg.. no idea what decides if this will happen or not.. > What would the correct set of kernel options be to ensure that during a system > panic I get: > > 1) The panic and related messages in /var/log/messages > 2) The system immediatly reboots with no user intervention > > Thanks! > > -Crh > > Charles Henrich Michigan State University henrich@crh.cl.msu.edu > > http://rs560.msu.edu/~henrich/ >