From owner-freebsd-questions Sat Nov 17 13:49:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from atkielski.com (atkielski.com [161.58.232.69]) by hub.freebsd.org (Postfix) with ESMTP id D124537B405 for ; Sat, 17 Nov 2001 13:49:41 -0800 (PST) Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fAHLnIK51365; Sat, 17 Nov 2001 22:49:18 +0100 (CET) Message-ID: <02fd01c16fb1$b55a67e0$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "Sudirman Hassan" , "FreeBSD Questions" References: <02b101c16f65$ec12f550$0a00000a@atkielski.com> <1292.10.100.98.21.1006004198.squirrel@10.100.3.5> Subject: Re: Mysterious boot during the night Date: Sat, 17 Nov 2001 22:49:12 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 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 Always a possibility, but why would RAM produce an error only after many hours of monotonous system activity? The amount of memory in use isn't changing very much. One thing is for sure: No matter what SETI@home says, running their software _does_ put a significant load on your system. The temperature of my processor rises by 27 degrees Celsius when setiathome is running, compared to sitting idle at a login prompt in FreeBSD (when the system is probably stopped on a HLT instruction 99.9999% of the time). CMOS processors use more power and get hotter when executing instructions than when idle; processors that always use the same power and always generate the same heat haven't existed in PCs in many years. I'm debating whether it is really a good idea to run setiathome. I don't care as long as it's not putting a strain on anything, but if it's going to make things so warm that they become unreliable, I'll pass. Of course, at this point, I really don't know what caused the boot. ----- Original Message ----- From: "Sudirman Hassan" To: Cc: Sent: Saturday, November 17, 2001 14:36 Subject: Re: Mysterious boot during the night > 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