From owner-freebsd-questions Sun Dec 6 09:42:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18610 for freebsd-questions-outgoing; Sun, 6 Dec 1998 09:42:48 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18604 for ; Sun, 6 Dec 1998 09:42:45 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id LAA20960 for questions@freebsd.org; Sun, 6 Dec 1998 11:42:40 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 06 Dec 1998 11:42:40 -0600 (CST) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: questions@FreeBSD.ORG Subject: Debugging after crash/reboot -- techniques wanted Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My -current box is rebooting itself at least once a day, and I'm wondering if anyone could provide some tips as to how to go about determining the cause(s). In other words, I'd like to know more about how others monitor/debug their systems, what methods/techniques are commonly used, how to get critical information logged properly, etc. Right now, I'm sort of flying blind, as after a reboot, I have nothing to go back and look at to try and determine what happened. Thanks for any suggestions. -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message