TheRaven64's Journal: Blocked and Crashed

I went away for a week, and everything crashed. My Jabber server went down the day after I went away (and I didn't check it until I came back. Ho hum.) My BSD box also crashed.

That's right, after only a couple of weeks my FreeBSD box went down. This proves one of two things. Either:

1. Linux is more stable than FreeBSD, or
2. Disabling both case fans to reduce noise is not entirely sensible

Personally, I consider the second to be more likely.

On an unrelated note, my IP is still blocked by slashdot. Actually, it's not my IP, it's the transparent proxy run by my ISP. When I pointed this out, I recieved an email stating that someone had used that proxy to flood slashdot (which may be the case, or they may just have had a lot of requests from the proxy, since it does have several thousand cable modems behind it) and they are not going to unblock it until the person who attacked them owns up. Nice to see that slashdot isn't run by primary school children. Anyway, I am now stuck bouncing my connection through a proxy server outside my ISP's network.

Not so hot

[thinkninja]

How many case fans do you have? It's a P3-700, right? I didn't think that they ran that hot, in all honesty.

I found the best thing for to reduce noise on my box is to sleep drives, but that's because I have a Matrox that's loud as hell. The downside is you're wearing it out quicker by spinning it up and down. That's another advantage to having a fileserver, I suppose, you can put it somewhere that it doesn't bother you.

Slashdot blocked my ISPs webcache sometime last year, IIRC. sigh.

Re:Not so hot

[TheRaven64]

The problem is that it's two P3-700s, right next to each other. Intel's wonderful motherboard design has them facing the same way, so the fan on the top one is almost touching the back of the bottom one. If you don't have another fan blowing air across the two of them then it the top one doesn't really get any airflow.