Date: Sat, 17 Nov 2001 21:36:38 +0800 (SGT) From: "Sudirman Hassan" <s9810048@mmu.edu.my> To: anthony@atkielski.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Mysterious boot during the night Message-ID: <1292.10.100.98.21.1006004198.squirrel@10.100.3.5> In-Reply-To: <02b101c16f65$ec12f550$0a00000a@atkielski.com> References: <02b101c16f65$ec12f550$0a00000a@atkielski.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1292.10.100.98.21.1006004198.squirrel>