FreeGameDev

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?

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.

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

{l Code}: {l Select All Code}

kill -15 redeclipse

, 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.

I've never had a problem closing RE.. and I'm on linux 99.3% of the time..

killall -9 reclient
(it might be redeclipse if you use RE package for your os or smth..)

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

{l Code}: {l Select All Code}

kill -15 redeclipse

, 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.

Those both worked very well, thanks.
Also, I close it because sometimes some random person makes a terrifically gfx-intense weapon mod that slows RE to a refresh rate of about 30 seconds per frame, so I have to kill it, and sometimes CTRL-C won't work. I have no problems closing it normally.

unixfreak {l Wrote}:Are you using the .deb package

No, I had problems downloading 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.

That isn't useless, Ctrl-Alt-Delete turns out to open a shutdown dialog box in the DE i'm using.

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.

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.

Wait until you encounter zombies...

By the way:

{l Code}: {l Select All Code}

man 7 signal

Just googled them, and they don't sound very fun, however it's still better than windows...which never free the resources x_x

Oh and thanks for the man page :)