Why is Red Eclipse sometimes unkillable? (i.e. Ctrl-C doesn't work, KILL doesn't work)
Sometimes, Ctrl-C works after about a second. Other times... it won't exit, and I can't kill it. Maybe it is a bug in ubuntu?
kill -15 redeclipse
Fallen {l Wrote}:killall -9 reclient
(it might be redeclipse if you use RE package for your os or smth..)
unixfreak {l Wrote}:I don't get the problem here on archlinux. Are you using the .deb package from playdeb? It might be worth downloading the source archive and see if that differs at all.
Have you tried closing it with, if that aint working you can always use -9 instead, but it will force the program to literally die and no settings will be saved if anything was changed while the game was running.
- {l Code}: {l Select All Code}
kill -15 redeclipse
unixfreak {l Wrote}:Are you using the .deb package
fawstoar {l Wrote}:Windows user here. This is absolutely useless to you, but I can always quit the program via Ctrl-Alt-Delete.
It's probably only crashed once in the last six months though.
ZeroKnight {l Wrote}:Yeah, I haven't learned too much about Linux yet, but I know that "kill -9" sends SIGKILL, which unlike in Windows, will force the program to die no matter what. That makes me very happy, because in Windows, sometimes processes will be stuck in certain kernel or driver jobs, and will literally be un-killable without restarting, as there is no similar process signals in Windows. I have had RE lock up on me like that a few times, but I have really bad Hardware, so that's probably why.
BTW, kill --help lists all of the process signals. What each does, I don't know ^^' It might be in a man page. Still too new to Linux.
man 7 signal
Users browsing this forum: Google [Bot] and 0 guests