In <4dae819c.8020...@biotec.tu-dresden.de>, Alex Mestiashvili wrote: >just a simple forkbomb will make your OS unusable ...
It shouldn't. When I first got my current hardware up and running, I fork bombed myself and then recovered just to prove the OS and hardware could handle it. I was able to login from another terminal (/sbin/login uses exec() to start your shell so it doesn't need another pid) and use the /proc file system as well as various shell built-ins to terminate all the fork bomb processes. "Yanking the power" is rarely the correct thing to do. Even if normal keyboard and mouse input appear to be ignored, there should be some attempt to use the "Magic" SysRq to take the keyboard back from X, terminate / kill various processes, sync / remount read-only file systems, produce a crash dump, etc. including doing a warm reboot or a soft power off. If you were actively using lots of swap and have locked up X11, it can take quite a while to switch to a vt and kill eclipse. It will normally be possible though. In cases where that isn't possible, Alt+SysRq+K might help get rid of X and processes that are talking to it. If that fails to give you back the system, Alt+SysRq+E will, but it'll also shut down all the system services, so you'll need to restart them. In short, there's a ocean of possibilities between "wait for Linux/Eclipse to resolve things" and "yank the power" that you don't seem to be exploring. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
