From owner-freebsd-questions Mon Nov 11 21:52:31 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24067 for questions-outgoing; Mon, 11 Nov 1996 21:52:31 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24062 for ; Mon, 11 Nov 1996 21:52:27 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id VAA24425; Mon, 11 Nov 1996 21:52:15 -0800 (PST) Date: Mon, 11 Nov 1996 21:52:15 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Nick Esborn cc: questions@freebsd.org Subject: Re: Making kernel panics more noticable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 8 Nov 1996, Nick Esborn wrote: > I'm running a 2.1.5-RELEASE machine that crashed after running fine for a > long time. I didn't notice that it had crashed until someone tried to > check their mail, as it didn't make any real noise. Is there any way to > set FBSD up to start beeping like mad when it gets a kernel panic, so > that at least if someone is around, they are made aware of the machine's > distress and given a chance to write down the console messages? The system should auto-restart unless the system really died. In any case I believe the pertinent info is logged before the system is rebooted. I could be wrong. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major