Aaron,
        
>I received a lot of e-mail (thanks!) saying that the 
>temperature reading on
>the BP6 is artifically high and to measure the actual 
>temperatures with a seperate thermistor. Although it is a round-about way,
I might take the
>thermistor I have on my BE6 on the CPU heatsink and measure 
>the BP6 with it.
>Odd way of doing it but they are sitting next to each other anyway.
I bought a RadioShack indoor/outdoor thermometer for $14.95 and put the unit
on the front of my PC case
and put the "outside" probe against the top side of the BX chipset. That way
I get ambient temps in the room 
as well as "case-MB" temp. I mounted the unit on one of the "drive slot
covers" so it looks like it's part of the PC.
That allows me to move the temp probe around from time to time to see if
anything is running hot.


>True. The danger zone starts appearing around 60C or so.
I thought it was more around 50C, but i'm a computer scientist, not a EE
guy.
I set up a shell program to read the lm sensors data (grep for 45C) and if
the temp reached 45C it 
writes the temps to a ".tempread" file and runs shutdown -h now to protect
the computer. 
I found it shut down a few times and read the .tempread file to see if the
computer overheated.
I recently changed the temp to 50C and haven't had any instability.


>Offtopic but did you have much trouble setting up that with 
>the cable modem?
It was easy. Just read August's issue of LINUX Journal on IP masquerade.
There's also lots of good howtos on the subject.

I thought you might be interested in this SMP stuff: 
To get two seti@home programs running at once each in their own windows,
copy your setiathome directory to a setiathome2 directory then use the
script:

cd <directorytree>/setiathome/setiathome 
xterm -e setiathome &
cd <directorytree>/setiathome2/setiathome 
xterm -e setiathome &

The CD part is important so seti doesn't write the data and .lock file to
your current directory. This enables your second seti program to start. Just
name this "seti" and put this script in your /usr/sbin and chmod it to make
it executable and your in business. Just type
"seti" from a command prompt and you get two seti programs running in
seperate windows.
This will definitely punish your SMP system.

David Green
Research Engineer
SRI International - Ft Monmouth Office
(732) 427-6435

-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]

Reply via email to