Mhm. Found that usefull tons of times myself (instead of crashing everything, even without stack trace or slightest smallest error text in logs, it tends to throw 200kb of error logs per minute, in your face
), but really. Take a closer look if your max statements isnt too low. It doesnt have to be, 150 is what i've used no prob (until server became, hmm... fat), now like I say - often 1k+ statements. If I had limited that to 150 then... Hate to hear that at some point you had to shutdown and work on inconsistent database, with missing pets, augments, rolled back levels xD Besides I don't think setting it even much higher would make this "prevention method" any less usefull. What matter most - is the max time you let idlying connection to live, until its closed. That's the problem maker in most cases (running out of available connections)
And in the next chronicle they went into space, fighting the evil empire... In a galaxy far, far away xD
