You mention in another post that attempts to login to the server are "bounced" to one of the clients. Not sure how you accomplish this, but it would be interesting to force this guy to one single node no matter where he logs in. With ssh keys setup, you could automatically ssh him to the same server every other node :-) He would login, start his a.out, login to another machine, start his a.out, and would just be competing for cpu against himself.
in reply to Re^2: A (highly) "ethical" use for for Perl
in thread A (highly) "ethical" use for for Perl
I was going to suggest renaming your perl to a.out so that it appeared to be his code, but when I realized your program was named after his login I was ROFL.