Time to start mixing the Kool-Aid

[mdlbear]

Staggered over to my computer this morning and discovered that my mail/news server had hung inexplicably overnight -- for the third time, with an uptime of only 18 days. OK, it's ancient (built in 1997, according to my records), and I've been reluctant to upgrade (it's currently running RedHat 5.1) because, well, it wasn't broken. It's also a noisy power hog that takes up too much space in my closet.

Two things have been keeping me from fixing it: the fact that inn (the news server)'s configuration has changed considerably since '97, and the fact that switching to Debian, which I want to do for other reasons, will require changing my userIDs (which date back to Slackware 1.0 -- I'm still user 100).

But enough is enough. As soon as the taxes are done, central.thestarport.org is gone.

Comments

[eleccham.livejournal.com]

I understand not wanting to fix what ain't broken... but it sounds like it's broken, now. :-S

I've been going through similar, mostly 'cause I've been getting most of my hardware from the company junkpile for the past three years, and cobbling together the working bits. So, I've had my fair share of system-fall-down moments.

[mdlbear]

This is one I put together out of mostly-new parts; I suspect it's either RAM or the CPU fan. (The disk drives are also suspect, but I would have expected to find errors in the logs in that case.)

Getting rid of it should be pretty straightforward, though. I just hate having to relearn how to configure stuff that's been working almost forever -- the last time was back when my ISP dropped UUCP support.