posted
Yes. That's actually what I'm talking about. There are ways for him to configure that computer which would make it much harder for one of you to crash the entire thing.
Posts: 37449 | Registered: May 1999
| IP: Logged |
quote:Originally posted by Blayne Bradley: That happens whenever someone's script runs an infinite loop (my teacher is working on a script to kill that process before it kills the server)
I am not talking about a slowdown, here. An infinite loop would not freeze all ssh instances to the point of being unable to accept Ctrl-C to kill the process. I've seen a heavy-duty fit slow things down to where it would take thirty seconds to get around to your input, but this takes it to the next level.
Posts: 10645 | Registered: Jul 2004
| IP: Logged |
Blayne Bradley
unregistered
posted
I am not talking about a slow down either, its the exact same, cant ctrl c, cant ctrl z, server essentially is crashed.
IP: Logged |
posted
Yeah, it is pretty easy to configure any modern operating system (usually in several different ways) to prevent one user from interfering with the operations of the other users to the point of exclusion.
KoM: I have a hypothesis. It managed to allocate with virtual memory, but there was such a huge amount of swap it thrashed the hard drive completely, and anything that wanted to page out was screwed, so everything froze once it attempted to allocate even a little memory. That would pretty thoroughly explain your symptoms.
Posts: 15770 | Registered: Dec 2001
| IP: Logged |
Printer-friendly view of this topic
