These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

How to kill process ExeFile.exe ?
Author
Previous Topic Next Topic
After Shok
Ruthenia Co
#1 - 2012-03-05 07:56:19 UTC
Sometimes the client hangs also it not to kill.
Process uses 100 % of 1 of 4 cpu and it's in running state.
wineserver -k or kill -9 - don't help

How to kill?

Правдой нельзя оскорбить, уважаемый адвокат!

Тот самый Мюнхгаузен

Золотая орка
Elegbara
White Wolf Enterprises
#2 - 2012-03-05 09:47:23 UTC
kill -9 will always help. Signal 9 can't be ignored or intercepted.

I am using killall -9 ExeFile.exe (but I haven't used that for quite a long time now).

Open your eyes. And awaken.
Karak Terrel
Foundation for CODE and THE NEW ORDER
#3 - 2012-03-05 18:33:57 UTC
Well there are occasions where you can't kill a process. But that only happens if it hangs in a kernel loop and a wine process should not do that except there is a problem with the gfx driver.
Elegbara
White Wolf Enterprises
#4 - 2012-03-05 20:41:49 UTC
SIGKILL will kill absolutely anything, even if it's locked in a kernel loop somewhere. At least that's how it should work on any sane platform.

Open your eyes. And awaken.
Katrina Bekers
A Blessed Bean
Pandemic Horde
#5 - 2012-03-05 21:14:29 UTC
The standard kill signal (TERM/15) means "please, dear stuck program, could you kindly run the callback for your gracious exit?". This can be of course ignored, or the process can be seriously unable to oblige - like being deeply frozen.

The KILL/9 signal is not managed by the process. The kernel removes the process from the process table forcefully, without asking permissions, waiting or even letting the process run anything.

There's only one chance for a -9'ed process to stay in the process table. When some sort of unsatisfiable I/O is expected, and the kernel buffer tables are still locked for that data. A process (which usually is in "D" state - waiting for I/O) then goes in "Z" state, for zombie. It may wait indefinitely for that I/O, but it's usually reaped as soon as the kernel needs the memory back.

Still, it's as good as dead, and you can start another instance easily.

<< THE RABBLE BRIGADE >>
Palovana
Inner Fire Inc.
#6 - 2012-03-06 12:32:43 UTC
Thread reminded me of this.

Please support: export of settings in editable format

Your stuff goes here.
After Shok
Ruthenia Co
#7 - 2012-03-09 16:21:52 UTC
Problem fixed - install Fedora 16 with 3.2.7-1 kernel - was Fedora 15

Правдой нельзя оскорбить, уважаемый адвокат!

Тот самый Мюнхгаузен

Золотая орка
Potiac
QUAFE Developers Inc.
#8 - 2012-03-10 11:22:35 UTC
hi,

that reminds me - i wrote a small shell script for that

Quote:
#!/bin/sh

# config
WINEPREFIX="/usr/local/games/wine"
EVE_PATH="/usr/local/games/eve"
EVE_SERVER=""
SISI_PATH="/usr/local/games/eve_sisi"

if [ "$1" = "kill" ]
then
killall -9 ExeFile.exe
wineserver -k
exit 0
fi

if [ "$1" = "sisi" ]
then
EVE_PATH=$SISI_PATH
EVE_SERVER="/server:87.237.38.50"
DESKTOP=$2
else
DESKTOP=$1
fi

cd $EVE_PATH
WINEPREFIX=$WINEPREFIX nice -n 3 wine explorer /desktop=EVE$DESKTOP,1680x1050 "eve.exe $EVE_SERVER"