> >This will prevent it from exceeding the procs limits, but it will *not* >completely stop it.
What if the few procs that he may spawn also grab so much memory so your machine disappears in swap-t(h)rashing? >The only way to kill it off successfully is to killall >-9 the script name repeatedly. As said earlier, killall -STOP first => keeps the number of processes constant (so he can't spawn any new ones) >Of course, you should always use a bat on the user if nothing else works. ;) Use a keylogger if you distrust, and after a bombing, look who set us up the bomb. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
