From owner-freebsd-questions Sat Nov 17 5:39:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mmu.edu.my (ext-dns.mmu.edu.my [203.106.62.11]) by hub.freebsd.org (Postfix) with ESMTP id 9E97437B416 for ; Sat, 17 Nov 2001 05:39:49 -0800 (PST) Received: from venus.cyber.mmu.edu.my (venus.cyber.mmu.edu.my [203.106.62.12]) by mmu.edu.my (8.9.1b+Sun/8.9.1) with ESMTP id VAA14674; Sat, 17 Nov 2001 21:34:46 +0800 (MYT) Received: from lunar.cyber.mmu.edu.my (lunar.cyber.mmu.edu.my [10.100.3.5]) by venus.cyber.mmu.edu.my (8.8.8+Sun/8.8.8) with ESMTP id VAA11915; Sat, 17 Nov 2001 21:38:15 +0800 (SGT) Received: from mmu.edu.my (localhost [127.0.0.1]) by lunar.cyber.mmu.edu.my (8.9.3+Sun/8.9.1) with SMTP id VAA10924; Sat, 17 Nov 2001 21:36:38 +0800 (SGT) Received: from 10.100.98.21 (SquirrelMail authenticated user s9810048) by 10.100.3.5 with HTTP; Sat, 17 Nov 2001 21:36:38 +0800 (SGT) Message-ID: <1292.10.100.98.21.1006004198.squirrel@10.100.3.5> Date: Sat, 17 Nov 2001 21:36:38 +0800 (SGT) Subject: Re: Mysterious boot during the night From: "Sudirman Hassan" To: anthony@atkielski.com In-Reply-To: <02b101c16f65$ec12f550$0a00000a@atkielski.com> References: <02b101c16f65$ec12f550$0a00000a@atkielski.com> Cc: freebsd-questions@FreeBSD.ORG X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG How about RAM? Sometimes faulty RAM can cause such problem. -dmn > Kent writes: > >> There are some exploits in 4.3. If you aren't >> running them, someone could have played tag >> with one of your daemons. That could prompt a >> mysterious reboot. > > There are only two systems on the LAN, both in my house, and neither is > accessible from the Net. > >> You must be running the x-version. I run the >> non-gui and get a wu in 9hrs. Top never shows >> more than that. > > I run setiathome under a special user account reserved for that purpose, > from the console (usually). According to SETI's web page, it churns out a > work unit every 5 hours and 40 minutes. I've never used the X version. It > had gone through about 10 work units non-stop at the time of the mysterious > reboot. > > If it were a temperature problem, I wouldn't expect it to take days to show > up. > >> I have a 900 t'bird and it doesn't run quite >> that hot. > > I don't know how hot this processor is supposed to run. I looked around on > the Web a bit, and all the maximum temperatures are considerably above my > measured temperature, usually closer to 70-80 degrees, sometimes 90. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message