I often have wine finish uncleanly or need to break in if it is misbehaving , this leaves some processes lying around and often means wine cannot be restarted correctly.
I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;
It works nicely but just wondered if anyone would say OMG dont do that !
TIA.
On Mon, 31 Oct 2005 20:10:12 +0100, [email protected] wrote:
I often have wine finish uncleanly or need to break in if it is misbehaving , this leaves some processes lying around and often means wine cannot be restarted correctly.
I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;
It works nicely but just wondered if anyone would say OMG dont do that !
TIA.
in fact it seems even kill -9 cant clean up some times.
bash-3.00#killwine kill -9 10666 kill -9 10690 bash-3.00#killwine kill -9 10666 kill -9 10690 bash-3.00#killwine kill -9 10666 kill -9 10690 bash-3.00#
bash-3.00#pgrep wine -l 10666 wineserver 10690 wine-preloader bash-3.00#
I took the system right down to the login console and still cant clean up.
Do I really have to reboot as the only way to clean up this mess?
This is taking windows emulation too far!! ;)
Does wineserver -k not work for you?
On Mon, 31 Oct 2005 [email protected] wrote:
I took the system right down to the login console and still cant clean up.
Do I really have to reboot as the only way to clean up this mess?
This is taking windows emulation too far!! ;)
[email protected] wrote:
bash-3.00#pgrep wine -l 10666 wineserver 10690 wine-preloader bash-3.00#
I took the system right down to the login console and still cant clean up.
Do I really have to reboot as the only way to clean up this mess?
This is taking windows emulation too far!! ;)
"killall -9 wine-preloader" works for me every time, however some older kernels have a bug which causes zombie processes (a placeholder for the process return code) to never be removed in the kernel. I think this was fixed around Linux 2.6.7 (ie. the unpatched Linux kernel).
Mike
On Mon, 31 Oct 2005, [email protected] wrote: [...]
I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;
You should try out pkill to simplify it even further.
[...]
in fact it seems even kill -9 cant clean up some times.
Besides the zombie processes mentionned before, some processes may be stopped (e.g. by the debugger) and won't die until you send them a CONT signal.
On Tue, 01 Nov 2005 11:50:17 +0100, Francois Gouget [email protected] wrote:
On Mon, 31 Oct 2005, [email protected] wrote: [...]
I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;
You should try out pkill to simplify it even further.
[...]
in fact it seems even cant clean up some times.
Besides the zombie processes mentionned before, some processes may be stopped (e.g. by the debugger) and won't die until you send them a CONT signal.
Thanks for all the replies, wineserver -k usually works but I still get some processes I cant kill:
15015 pts/5 Tl 0:01 /usr/bin/wine-preloader /usr/bin/wine-pthread natspeak
kill -9 15015 kill -9 15015 kill -9 15015
is not able to kill this.
closing the xterm did in this case lay it to rest.
Thanks again.
On Tue, 01 Nov 2005 11:50:17 +0100, Francois Gouget [email protected] wrote:
On Mon, 31 Oct 2005, [email protected] wrote: [...]
I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;
You should try out pkill to simplify it even further.
[...]
in fact it seems even kill -9 cant clean up some times.
Besides the zombie processes mentionned before, some processes may be stopped (e.g. by the debugger) and won't die until you send them a CONT signal.
After an untidy exit I get stuck with the following. I took it right down and even logout out of the initial login console using cntl-D
bash-3.00#killwine kill -9 16322 kill -9 16406 bash-3.00#wineserver -k Segmentation fault bash-3.00#pgrep -l wine 16322 wineserver 16406 wine-preloader
It really seems like all I can do here is init 0 !!
-
Dan Kegel -
Francois Gouget -
Mike McCormack -
Walt Ogburn -
wino＠piments.com