From owner-freebsd-questions Fri May 1 18:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02968 for freebsd-questions-outgoing; Fri, 1 May 1998 18:18:25 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02959 for ; Fri, 1 May 1998 18:18:17 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA00409; Sat, 2 May 1998 10:48:11 +0930 (CST) (envelope-from grog) Message-ID: <19980502104811.C318@freebie.lemis.com> Date: Sat, 2 May 1998 10:48:11 +0930 From: Greg Lehey To: limanond@enws626.eas.asu.edu, freebsd-questions@FreeBSD.ORG Subject: Re: What cause automatic reboot? References: <3549F70B.184F@enws626.eas.asu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3549F70B.184F@enws626.eas.asu.edu>; from Suttipan Limanond on Fri, May 01, 1998 at 09:23:39AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 May 1998 at 9:23:39 -0700, Suttipan Limanond wrote: > Hi: > > Is there a way to check what is the cause of automatic rebooting? > This morning when I came to work on the computer, the screen was frozen > with reboot message. Part of the message said that / is not properly > dismounted. My guess is that somethings bad must have happened last > night. I just do not know what it is. The same thing happened the night > before (but the symptom was different: the blank screensaver was frozen > after leaving the PC on overnight). > I used to be able to leave the PC on without any problem at all. It could be a hardware problem, or it could be something started by cron. The first thing would be to look at /var/log/messages and see when the last message was written. If it's consistent, you could look for a cron job started some time after that. If you don't have many console messages, you could try the -m option to syslogd, which will issue "mark messages" at regular intervals. Apart from that, it's a difficult problem. It's a "can't happen" situation which we can't adequately analyse. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message