?

Log in

No account? Create an account

Previous Entry | Next Entry

File Wars: The Sysadmin Strikes Back

Dammit.

In case nobody noticed, my Web host has killed off Filespace. Apparently, one of my beta scripts took nearly 50% of CPU. This might be excusable, except that Filespace has apparently been stressing the server for months.

Something I never knew about, although the admin seems to think he's talked to me about it before last week. Oh well, at least he let me grab all the files that were uploaded since I restarted the site--I still had everything from before then, so I don't think any files were lost.

In any case, I don't think just getting another host is an option--I'll probably just run into the same problems. Since I can't afford to pay $75/month for half of a dedicated server, I'm now looking at self-hosting. This has three components:

1. Getting a better DSL line--128kbps upstream won't cut it.
2. Getting a server.
3. Getting some knowledge of how to administer Linux.

Each of these has their own complications.

The complication in #1 is time. It normally takes twenty days to get a small business DSL account, the next step up from consumer DSL. I'm hoping that the fact it's an upgrade will help. My parents will pay the difference--I'll be canceling my Web hosting reseller account, so on balance they'll be saving $5/month. (Mom pays for the hosting account as remuneration for small, monthly updates to her Web site.)

The complication in #2 is money. I'm estimating it'll cost about $300; basically, I'll be buying new components and turning most of them into a new PC, leaving my current PC as the server. (Hard drives and cases will probably keep their current uses, though.) This means doing some sort of work. Mom has an idea to do authors' sites for cheap--they'll pay a few bucks a month for hosting on the server, as well as paying for the initial site and for updates. But it might not take off, in which case I'll have to get a real job, possibly doing grunt tech work at my father's office.

#3's complication is experience. Although I've used Linux on web servers for years, I've never administered it. I've never successfully set up a Linux distribution, let alone secured it and run Web sites off of it (although all my attempts were years ago, and usually stopped when I tried to interface with Windows machines or enable sound). It is, of course, quite a useful set of skills to learn, but I'd rather not learn things the hard way. Thus, any tips from those of you who have done such things before are much appreciated, especially titles of good books I can buy.

Some of you probably think I should just give up and not restart Filespace. And I probably should. Except...

I dunno. Maybe it's that my users put trust in me by uploading stuff to my server, and I want to honor that trust; maybe it's just because I'm stubborn. But whatever the reason, something in me refuses to give up. It's hard to explain, partly because I don't completely understand it.

In any case, if it is within my ability to see it happen, Filespace is down but not out.

Comments

codepoetica
Jan. 2nd, 2004 02:01 pm (UTC)
holy wars
I will put forward the suggestion of an X-less instance of Slackware (mirror). Despite various warnings, I find that running Slack-current is rel'tivly hassle-free.
nathanbp
Jan. 2nd, 2004 02:14 pm (UTC)
Re: holy wars
|\|0!!!!!!!1111111111111one!!!!!!1 Slackware 5|_|(|<20|25, Debian ownz j00.........errrrr....I mean, whatever works ^_^;; Just suggesting Debian cause it seems to work well for me