Understood, ita. I just wish I knew enough to be helpful instead of a parrot creature.

Not even restarting the daemon?

He's going to talk to his server admin about that. But it's not really a long term solution since we'll most likely start to creep up again on connections.

ETA:

We may need more than $20 of resources, but a bug in mysql making us need $200?

I've already had one person who was willing to move a site over contact me. Maybe a few other people who are interest could email me and we'd have a better idea on what the monthly cost would work out to be for you?

As soon as I get a new job, I'd be interested in picking up a domain name, and starting a site for myself. I'd do it with FG on the server we used. I don't know how soon that will be, though.

But we'd still be on the hook for the $200. If, for example an account that moved over left (for whatever reason) we would be financially responsible. I think we have to plan on that basis as a business issue (for lack of a better term). If the expense can be defrayed, great, but if we rely on that and it doesn't pan out, that's not good for long term fiscal health.

No, I understand that. I'm just saying that if we only have two people who are seriously interested, maybe it's not even worth further discussion. If we have 10 people, it might be worth a try.

Kristen (correct me where I'm wrong, please), I seem to remember that after a past crisis, and/or after ita shut off the RQG, and we pared down our threads, we were using well under 50 connections. If this problem is a MySQL bug (which I realize isn't Steven's fault), we're not actually problem children. We're victims of the bug. Given what's going on, shouldn't Steven resetting the daemon be part of the support he provides as ISP?

I'm in way over my head, so where I sound terse, please read it as me trying not to screw up. I just don't understand why we'd upgrade, if this is a MySQL problem, and not a Phoenix!Code problem, and I don't understand why you're saying our usage would creep up again, if we run under the 50, when we're not afflicted by the bug.

Cindy, if I'm following this correctly, we'd keep creeping up after each restart until the bug is fixed.

Just a thought -- could we negotiate a price for the occasional restarting (resetting? whatever the term is) of MySQL? That would come in between the $20 and the $200 support level, surely.

(Since I know very little about how much labor is involved or whether the labor/services can be priced accordingly, I just throw this out without knowing if it's a laughable idea or not.)

Cindy, if I'm following this correctly, we'd keep creeping up after each restart until the bug is fixed.

Okay, I wondered, but don't think of that as us creeping up, but rather an effect of the bug in the code. Thank you, aurelia.

I like Theodosia's idea.

As we get closer to Thursday, I still vote for Kristen's proprosal even if this code error gets fixed. Unless the host changes attitude, I'd like more responsive service, and I think that requires larger sums of money.