Sorry I've been posting so many messages. We're working all the kinks out of the system; that's for sure.
I inadvertently pasted a command and started a Java program spawning too many threads. The program spat out a message about being unable to create enough threads, and I tried to kill it with CTRL-C. Then it said something to the effect of "kill signal received out of memory response; may have to forcefully terminate the VM". Unable to do anything, I logged out and tried to log back in.
I now receive the following message whenever I attempt to log in.
Connection to 126.96.36.199 closed by remote host.
Connection to 188.8.131.52 closed.
I'm assuming you only allow one login per user, and that's why I can't get back in. I tried logging in from another account (the account that this transpired on was a student account) to kill the runaway Java VM, but I can't kill it using the other (instructor) login. The runaway process' pid is 1561, and it is running on acano01.
EDIT: since then the process appears to have disappeared and I can log in again. I'll be more careful in future, but is there any mechanism whereby I can expedite the process?