Dayumm hurrrrzz gudd................
MUWAHAHAHAHHAHAHHAHAHHAHAHAHHAHAHAHHAHA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Printable View
Dayumm hurrrrzz gudd................
MUWAHAHAHAHHAHAHHAHAHHAHAHAHHAHAHAHHAHA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
lol'd
2nd times, by juji
Don't call me Shirley!
flaglerchat diddid itt
i guess flagerchat is making new evidences how he did it, but it's too late, juji did it (at least, maybe one of their admins accidentally upgrade vb forum and didn't have time to repair)
it's not a evidence
Moi diddit
U cun't ban Der flaglerchat.........................
MUWAHAHAHAHAHAHAHHAHAHAHHAHAHAHHAHAHAHHAHAHAHAHHAHAHA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!
ah, i see, i guess juji did it
hey op, stop idioting yourself if you dont have evidence
I did it
lizard drama
literally have no idea whats going on in this thjread
You wish faggot.
You're too stupid to cause this.Quote:
Hello,
This message is to advise you of a temporary block placed on your database. The database was found to be consuming an inordinate amount of processor time, to the point of degrading overall system performance. While we do limit each account to no more than 25% of a system's CPU in our terms of service, we do not actively disable accounts until they greatly exceed that number, which is what happened in this case. Requests to this database may become degraded by limiting the maximum number of queries or connections for a limited amount of time, or if there are sustained issues, ultimately we may be forced to block access to this database until the issue has been resolved.
Resolving this situation may be as simple as adding additional indexes to your database, optimizing the queries used, or something equally easy. If not, it may simply be a matter of moving this database to dedicated services, as it may have outgrown a shared environment.
If you believe you have a solution to this overuse, we are happy to discuss the situation with you and possibly reinstate the database on the server. Otherwise, we will be happy to assist you with the upgrade process if a dedicated server is the most appropriate solution. Thank you, and we look forward to hearing from you shortly.
~~~
Excessive MySQL activity is caused by (a) a long-running process that locks a table, causing other queries to back up, (b) a query that is not optimized ][example: select all from ... and involving a large or complex query], (c) huge table copies/maintenance during peak hours.
I don't think it's all been Cody but I believe some of it has been. I no longer get targeted, Cody has my cell phone number and as far as I know has yet to give it to anyone. Cody tends to air his bitterness towards me out in the open.
They seriously need to change the cookie settings so members don't get logged out so quick when idle.
Sure whatever you say.