-----Original Message----- From: Chris Reeves [mailto:chris.reeves@iname.com]
Yatsen Ng wrote:
Sometimes I run into a process that just doesn't know when
the kill command all I want but it won't do any good. Take for example Netscape. Sometimes it freezes and I'll use xkill to take it out of its misery. When I restart it I'll get an error message stating
to quit. I can use that another user
is running Netscape using my files under process ID 437 (for example). When I issue the kill command nothing will happen. There's also a zombie process running that's equally stubborn. How do I deal with those?
I always used to use a 'kill -9 <pid>' until I discovered the CTRL-ALT-ESC-click-on-the-window-you-want-to-kill method.
Is this specific to a certain WM?
However, I discovered that that doesn't totally kill netscape off (it must be sending a different signal instead of a 9 (SIGKILL)). Because of this I've just moved bad to my old 'kill -9' routine.
Same here, love the flexibility of a console, xterm, wterm, eterm, or what have you. Greg Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/